Compiling wl driver on upup 476?

piratesmack · 09-11-2009, 09:49 AM

I'm trying to compile this driver on upup 476.

I tried following the readme, but I get a "No targets" error when I run:
make -C /lib/modules/2.6.29.4/build M=`pwd`

I have the kernel source and devx
sfs modules.

Any ideas?

Thanks

8-bit · 09-15-2009, 01:02 AM

Does the source have a configure file?
I usually just do a ./configure followed on completion of that by make.

piratesmack · 09-15-2009, 02:15 AM

Quote:

Originally Posted by 8-bit

Does the source have a configure file?
I usually just do a ./configure followed on completion of that by make.

Nah, no configure script.
I tried compiling it on puppy again and this time it actually started to compile, but failed. (sorry, didn't bother to write down the error)

Then I applied the 2.6.29 patch from broadcoms site and tried compiling again, but it still failed.

I know you can't help much without the errors, so I'll post them later. But if anybody has been able to compile this on on upup, please let me know how you did it.

piratesmack · 09-16-2009, 08:52 AM

OK, the error was caused by a missing /usr/src/linux-2.6.29.4/include/linux/bounds.h

I noticed that there was a bounds.h in /usr/src/linux-2.6.29.1/include/linux, so I copied it over to 2.6.29.4.

After that, the driver successfully compiles.
The only problem now is I get a kernel panic every time I "modprobe wl"

Any ideas?

8-bit · 09-16-2009, 11:28 AM

Quote:

Originally Posted by piratesmack

OK, the error was caused by a missing /usr/src/linux-2.6.29.4/include/linux/bounds.h

I noticed that there was a bounds.h in /usr/src/linux-2.6.29.1/include/linux, so I copied it over to 2.6.29.4.

After that, the driver successfully compiles.
The only problem now is I get a kernel panic every time I "modprobe wl"

Any ideas?

It just might be a compiling kernel mismatch.
I clicked on my upup-476.iso, to mount it and then clicked on upup-476.sfs to mount it.
then I navigated to lib/modules.
It showed a folder for the kernel that was 2.6.29.3.
So that would mean the wrong kernel source was used to compile the driver.

You can verify the kernel version used in upup 476 by navigating to /lib/modules and see what kernel version was used by the name of the folder.
If it does not match your kernel source sfs file you have a kernel incompatibility.

piratesmack · 09-16-2009, 01:39 PM

Quote:

Originally Posted by 8-bit

It just might be a compiling kernel mismatch.
I clicked on my upup-476.iso, to mount it and then clicked on upup-476.sfs to mount it.
then I navigated to lib/modules.
It showed a folder for the kernel that was 2.6.29.3.
So that would mean the wrong kernel source was used to compile the driver.

You can verify the kernel version used in upup 476 by navigating to /lib/modules and see what kernel version was used by the name of the folder.
If it does not match your kernel source sfs file you have a kernel incompatibility.

2.6.29.3?
Thanks, I'll check that out.

Could've sworn it used 2.6.29.4, but maybe I made a mistake.

EDIT:

Quote:

'upup-476.iso' is the standard Jaunty Puppy build, kernel 2.6.29.4.

http://puppylinux.com/blog/?viewDetailed=00768