> > >> 2. If you got the SDK from TI, TI should be able to supply the source >> code. >> >> > Thanks Steve. I got the SDK from TI so I've initiated contact with their > support. I could not find the same version of module-init-tools on > kernel.org otherwise I could have just taken it from there. The one on > DM355 target file system is version 3.1-pre5. > > This was completely my bad. I have this big build script that first builds the kernel, the modules and some more things follow. I looked at the build log closely and saw that the kernel 2.6.10 was never getting built properly with the MVL5.0 toolchain. And the board was booting of the old uImage.
So, lesson learnt: have the build script delete all old files before they are re-built. Anyway, so finally I did manage to get the 2.6.10 kernel to build with MVL5.0 toolchain. It needed some minor changes to the code, but they were straight forward on comparing with the 2.6.18 kernel of MVL5.0. Now I have another problem, it looks like the DVSDK 1.30.01.41 also has to be re-built with MVL5.0 toolchain. I did this, which ensures that the cmem.ko module, among others, is re-built with the new toolchain. When I try to load this module, I get the following errors: #insmod cmemk.ko phys_start=0x87400000 phys_end=0x88000000 pools=1x2097152,2x1529856,7x829440,1x524288,1x108680,2x81920,1x9600,2x8192,6x4096 cmemk: disagrees about version of symbol strcpy cmemk: Unknown symbol strcpy cmemk: disagrees about version of symbol __arch_copy_to_user cmemk: Unknown symbol __arch_copy_to_user cmemk: disagrees about version of symbol __put_user_4 cmemk: Unknown symbol __put_user_4 cmemk: disagrees about version of symbol __memzero cmemk: Unknown symbol __memzero cmemk: disagrees about version of symbol __get_user_4 cmemk: Unknown symbol __get_user_4 cmemk: disagrees about version of symbol __arch_copy_from_user cmemk: Unknown symbol __arch_copy_from_user insmod: error inserting 'cmemk.ko': -1 Unknown symbol in module [email protected]:/opt/dvsdk/dm355# Can anyone please point out what else do I need to re-build with MVL5.0 toolchain? Why the complaint about "strcpy"?? Best regards, Kapil -- "The Power to Imagine, is The Power to Create!" -TTux
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
