[uClinux-dev] do_initcalls() where is vmlinuz set up to populate between __initcall_start to end

John.Jeffers at bjservices.com John.Jeffers at bjservices.com
Tue Oct 16 15:11:49 EDT 2007


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 the "module_init" macro.
Cheers John

> 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 by setting the variable ( just as a test)
> 
> initcall_debug to 1 in
> 
> init/main.c
> 
> Regards
>    Phil Wilshire
> 



More information about the uClinux-dev mailing list