Hi,
This message is in repsonse to my troubles writing the SKPCR register on
the SA-1111 development board to enable the USB clock.
It seems John was right after all, only I wasn't paying attention and
missed the real cause of the problem. The USB initialisation is performed
before the code in sa1111_init() is executed. Hence, my code added to the
USB driver cannot work because the RAB hasn't been initialised properly
at this point in the bootsequence. Only after puting some more printks in
different parts of the kernel did I notice this... :(
This leads me to my next question. What controls in what sequence the
different parts of the kernel are executed during system boot and why is
the code in sa1111_init() executed at such a late stage in the sequence?
It seems to me that it would be beneficial to have the SA-1111
initalisation code executed earlier, so other kernel parts, like the
USB driver or the Ethernet driver, can also initialise while compiled
into the kernel. Compiling the drivers as modules would solve the problem,
but would be the wrong solution to the problem in my opinion.
I have been staring at the kernel code to try to understand what
determines the boot sequence, but haven't found it yet, not helped in the
least by the fact that I was dozing off on my keyboard.... :-)
Could someone shed some light on this matter?
Thanks in advance,
Arjan
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
