Dunlap, Randy writes:
> While Jeff and I basically agree on the short-term
> solution (if one is still needed, altho I'm not aware of
> any init order problems in USB in 2.4.0-test10), my
> recollection of Linus's preference (without
> looking it up) is to remove the calls from init/main.c
> and to use __initcalls.
The problem for ARM is that Linux does a lot of the initialisation for
some machines, which basically means the hardware isn't setup for access
to the USB device if the USB initialisation was placed in init/main.c
(this initialisation is done by the very first initcall on ARM). However,
that said, we may be able to get away with only adding hw_sa1100_init()
before the USB call, but this is only one family of the ARM machine types.
BTW, I've long lost track of what the original problem that sparked off
this thread was, does someone have a quick reference to it? (please
reply in private mail). Thanks.
_____
|_____| ------------------------------------------------- ---+---+-
| | 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/
This archive was generated by hypermail 2b29 : Tue Nov 07 2000 - 21:00:17 EST