David Brownell wrote:
>
>
>
> >>But all of your diagnostics seem more related to descriptor access,
> >>which is a different layer than the ohci code. Both sound drivers
> >>give you funkiness, and sound has unique descriptor handling, which
> >>did change (more textually than behaviorally) in
But all of your diagnostics seem more related to descriptor access,
which is a different layer than the ohci code. Both sound drivers
give you funkiness, and sound has unique descriptor handling, which
did change (more textually than behaviorally) in 2.5.45...
Thanks David,
Is anyone workin
David Brownell wrote:
>
>
>
> > Aaah, this looks like an ohci problem, rather than audio ( or there is
> > more than one problem :))
>
> Well, there's certainly more than one problem! And I'd be surprised
> if none were in the ohci code, I'll be looking for one in particular.
>
> But all of y
Thomas Sailer wrote:
>
>
> On Fri, 2002-11-08 at 06:11, Kevin Brosius wrote:
> > I've tried the latest usb changes from the bk tree, and continue to see
> > the attached null pointer problem when trying to install the 'audio'
> > module.
>
> Can you mail me a lsusb descriptor dump and cc
> [EMAI
Aaah, this looks like an ohci problem, rather than audio ( or there is
more than one problem :))
Well, there's certainly more than one problem! And I'd be surprised
if none were in the ohci code, I'll be looking for one in particular.
But all of your diagnostics seem more related to descripto
Kevin Brosius wrote:
>
> With 2.5.46, recent bk tree usb patches to 2.5.46, 2.5.45 and maybe
> 2.5.44 (I forget if this broke in 2.5.44 or .45, it worked a couple
> versions ago) I see the following oops'es.
>
> System is Athlon MP mobo, ohci hub.
>
> On trying to install ohci and audio with mod
