On 12/14/2010 06:00 AM, Hemanth Kumar wrote: > Hi Mulyadi and Robert, > [...] >> it....or disable module versioning entirely............... > > Thanks for your time and suggestions,I solved this problem, > I added the two modules in kernel dir(driver/misc/),updated > Makefile,Kconfig file & compiled, loaded the m2 and m3 to my surprise it worked,Other things I observed is even when I compile two diff driver's with two diff version of GCC(4.2 & 4.3) I was able to insmod > and it was working fine(I thought kernel version (2.6.32.9) & gcc version(gcc-4.3.1) should be same,),I am really puzzled with android kernel????????,I realy dont know how it is working,Please correct if I am wrong My guess it has to do with the fact that you have versioning enabled and the method, because you can see during the loading and the modinfo that there is version information on your modules. Because dependencies exist from m3 to m2, you need to compile them in one run and allow the kernel build system to work out the references and make auto-versioning work. That is what is happening now that you have placed the modules in the Kbuild system. I think that if you disable the config option CONFIG_MODULE_SRCVERSION_ALL for your arm kernel and build your modules against that you can probably insert them exactly like on your x86 machine. As for the compiler version, as long as the compiled binaries are compatible it is possible to use a different GCC version. Disclaimer: all of the above is my best guess and I am by no means an expert. Best regards, Wouter -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
