HI John,
A simple way to do this is to use the module_init macro
static int __init my_init_stuff(void)
{
return 0;
}
module_init(my_init_stuff);
You can see all the init calls as they happen
using the initcall_debug command line option
root=/dev/mtdblock0 rw initcall_debug=1 ...
Or
Thanks I am getting closer.
The debug does not work for 2.4.32-uc0 I did stick a printk in
do_initcalls() to show the called addresses of the modules which works.
Is there a best place in the file structure (on the host) 2.4.32-uc0 to
put the static int __init my_init_stuff()
so link picks up
Hi
Yes I have puzzled through this and read a lot of material and code but
have not quite found this answer.
With 20070130-dist 2.4.32 and uClib on a Coldfire m5235 board with some
special kernel/driver modules for LEDs etc.
For the ram between __initcall_start and end to populate with the
On Monday 15 October 2007, [EMAIL PROTECTED] wrote:
Yes I have puzzled through this and read a lot of material and code but
have not quite found this answer.
you're wondering how the initcall mechanism works and how to use it yourself ?
-mike
signature.asc
Description: This is a digitally
