<div>Hi,</div> <div> </div> <div>My doubt is more related to Linux kernel rather than PPC, but I feel that many will be interested to know this. Please help me to understand a silly doubt.</div> <div> </div> <div>When we have drivers as kernel modules, it can be loaded using insmod or modprobe.</div> <div>We use the depmod utility to generate the module dependancy and so concerned module gets loaded first.</div> <div>This is fine.</div> <div> </div> <div>Now when in comes to in-build module (part of kernel image), we obviously don't run the modprobe and/or depmod because they are no more modules.</div> <div> </div> <div>So how does - during compilation time, tool chain can identify which module to load first so that do_initcalls() function can take care if it.</div> <div> </div> <div>e.g. Module A and Module B.</div> <div>Both are inbuild, and A uses the functionality of B. So module_init() of B should get called first.</div>
<div>How this is achieved for in-build modules?</div> <div>__init macro takes care of it for freeing that memory after those calls, but how the sequencing is done?</div> <div> </div> <div>Regards,</div> <div>Parav Pandit</div> <div> </div><p> 
<hr size=1>Stay in the know. Pulse on the new Yahoo.com. <a href="http://us.rd.yahoo.com/evt=42974/*http://www.yahoo.com/preview"> Check it out.</a>