Re: Module init for compiled in vs loaded modules

On Tue, 19 Aug 2008, Fundu wrote: > > linux/init.h: > > > > #ifndef MODULE > > ... > > #define module_init(x) __initcall(x); > > #define __initcall(fn) device_initcall(fn) > > #define device_initcall(fn) > > __define_initcall("6",fn) > > #define __define_initcall(level,fn) \ > > static in

Re: Module init for compiled in vs loaded modules

> linux/init.h: > > #ifndef MODULE > ... > #define module_init(x) __initcall(x); > #define __initcall(fn) device_initcall(fn) > #define device_initcall(fn) > __define_initcall("6",fn) > #define __define_initcall(level,fn) \ > static initcall_t __initcall_##fn __attribute_used__ > \ >

Re: Module init for compiled in vs loaded modules

Please, do not start a new thread by replying to a message in an existing thread. Compose a new message from scratch to the mailing list. Otherwise your thread shows up in the middle of another, *unrelated* thread when anybody looks at a threaded view of the archives. Just look at

Re: Module init for compiled in vs loaded modules

Code base of 2.6.18 > > 1) But where do i look to find how the kernel loads(ie. calls the fn exported > by module_init()) for modules compiled into the kernel. linux/init.h: #ifndef MODULE ... #define module_init(x) __initcall(x); #define __initcall(fn) device_initcall(fn) #define device_i

Module init for compiled in vs loaded modules

Hi, For kernel modules can be loaded by explicitly do insmod etc for ones that are not compiled into the kernel. 1) But where do i look to find how the kernel loads(ie. calls the fn exported by module_init()) for modules compiled into the kernel. 2) Does the kernel call some kind of probe