Hey all,
I've decided for fun, and learning, to get into doing some cross compilation with the caanoo. I really wanted to learn how to several things, but one of them is kernel modules. So, brief overview. I installed x64 debian inside Virtual box, and moved all the Caanoo toolchain stuff into it.
Cross compiling seemed to be no problem. Now, I went ahead and tried a kernel module. Specifically, I have an old USB wireless thing. I wanted to see if I can make it work. So, I downloaded the Caanoo kernel (from 1.06) source, and linux-wlan-ng debian package.
I was able to get the kernel modules to compile (once I got the environment right), but I cannot load them.
I get "Unknown symbol malloc_sizes". Now, I searched through the source, and there aren't any references to this in the source. So, it implies, to me, that is expected in something local. Perhaps libraries?
Anyway. I am running the firmware for 1.5, which is still kernel 2.6.24.
Are there any suggestions? I feel like I could possibly get this to work, because I am so close.
Since kernel module development seems to be tightly integrated with the kernel itself, I almost feel like I could tweak some kernel config settings to get this to go.
Still, this is new territory for me, so I'm not sure.
Thanks!
I've decided for fun, and learning, to get into doing some cross compilation with the caanoo. I really wanted to learn how to several things, but one of them is kernel modules. So, brief overview. I installed x64 debian inside Virtual box, and moved all the Caanoo toolchain stuff into it.
Cross compiling seemed to be no problem. Now, I went ahead and tried a kernel module. Specifically, I have an old USB wireless thing. I wanted to see if I can make it work. So, I downloaded the Caanoo kernel (from 1.06) source, and linux-wlan-ng debian package.
I was able to get the kernel modules to compile (once I got the environment right), but I cannot load them.
I get "Unknown symbol malloc_sizes". Now, I searched through the source, and there aren't any references to this in the source. So, it implies, to me, that is expected in something local. Perhaps libraries?
Anyway. I am running the firmware for 1.5, which is still kernel 2.6.24.
Are there any suggestions? I feel like I could possibly get this to work, because I am so close.
Since kernel module development seems to be tightly integrated with the kernel itself, I almost feel like I could tweak some kernel config settings to get this to go.
Still, this is new territory for me, so I'm not sure.
Thanks!