> I only got the OHCI controller yesterday and don't have much experience with
> OHCI. Where might I start to look to fix this problem?
I'm tracking down some Cardbus/OHCI related problems ...
the short version of the story is that both the OHCI and
UHCI drivers need to convert to "new style" PCI drivers
(providing a 'struct pci_driver') before they can handle
the hotplug/unplug/... features of Cardbus correctly, but
there are some smaller issues too.
That patch will be visible at some point (soon I hope)
but until then I suspect you can get work done so long as
the card is always plugged in when you modprobe usb-ohci.
I'll also be posting an "ohci micro patch" which includes
fixes for an OOps you might happen on, as well as some
cleanup and groundwork for a later cardbus patch. Apply
that, just in case!
> I didn't get very
> many debug messages when I #define DEBUG in usb-ohci.c .
> Is there something else I need to do?
Did you get _any_ debug messages? Did you configure
all your kern.debug syslog messages to get saved?
That problem would likely be a generic OHCI problem,
nothing cardbus-specific. I'd expect some messages
in the vicinity of that failure.
- Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
