On Tue, Sep 1, 2009 at 5:37 AM, Microbit_Ubuntu<microbit@xxxxxxxxxxxxxxxxxxxxxx> wrote: > Hi Mulyadi, > > Oh, perhaps I should have noted that the consecutive module placements are 0x3000 > when my test module doesn't use __init... > Else - of course - the consecutive placements are 0x6000, but I guess that was implied :-) > > It's still a strange ranger scenario, the init code being placed where - normally - the next insmod > would go. Perhaps the init code is padded as well for some sort of protection... dunno. > > I'll keep the padding issue in the back of my head as I learn further with Linux. I haven't enabled > debug VM in kernel config yet - that's for later.. :-) > > But thanks for the advice and review ! Well, sorry if at this point I am unable to give further ideas. Hopefully it gives you enough fundamentals to go further by your own. Please keep us informed on what you've found.... -- regards, Mulyadi Santosa Freelance Linux trainer blog: the-hydra.blogspot.com -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
