Messages in this thread |  | | From | Russell King <> | Subject | Re: USB init order dependencies. | Date | Tue, 7 Nov 2000 07:26:41 +0000 (GMT) |
| |
Dunlap, Randy writes: > I'm not following your argument very well. I've read it > and reread it several times. > Does adding a call to usb_init() in init/main.c cause > USB to be init 2 times?
No. As I said elsewhere in this thread, the USB OHCI chip is not accessible until other board-specific initialisation has happened. This is done via an initcall. Unfortunately, moving usb_init() back into init/main.c will mean that USB is again initialised before any initcalls, which means for these boards USB will be non-functional without additional changes over and above just moving usb_init().
I hope this helps you understand the problem. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King rmk@arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/personal/aboutme.html / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |