toolchain for building linux-2.6.27.8 or 2.6.28.1 ...

I wrote a couple days ago needing advice on USB wi fi. I made some progress but then I hit a snag loading the USB wi fi adapter firmware.

Jon schooled me on the firmware topic (thanks Jon), and advised me to select the following Kconfig options

Kconfig
Device drivers
generic driver options
user space firmware support
check - include in-kernel firmware blobs in kernel binary

My 2.6.24 kernel didn't offer these options, and I also suspected that since 2.6.24 some progress on the ralink drivers I need has been made I figured I'd just try a new kernel build and try to get my ralink-equipped Linksys WUSB54GC to work.

Trouble:
-I was using Ltib Toolchain (gcc-3.4.3-glibc-2.3.6 (for 603e)) to build my 2.6.24 kernel.
-It looks like somewhere after 2.6.24 this toolchain stopped successfully compiling the kernel.

So,
-I used crosstool and built 4.1.0 and 4.1.1 toolchains. Both produce the following error:

OBJCOPY arch/powerpc/kernel/vdso32/vdso32.so
objcopy: Unable to recognise the format of the input file `arch/powerpc/kernel/vdso32/vdso32.so.dbg' make[3]: *** [arch/powerpc/kernel/vdso32/vdso32.so] Error 1 make[2]: *** [arch/powerpc/kernel/vdso32] Error 2

Questions:
1) if I want to cross-compile a kernel later than 2.6.24 to hopefully get better WAN device support (and clearer options for fw loading), which kernel should I try, and which toolchain?

the ltib repository does not appear to have a toolchain newer than
gcc-3.4.3-glibc-2.3.6 (for 603e)

Admissions, disclaimers, etc
1) I'm using the same ltib script I have used for the 2.6.24 build with toolchain gcc-3.4.3-glibc-2.3.6 (for 603e).
I'm simply modifying the kernel spec file to use 2.6.28.1 (and specifyin a custom toolchain).
I've also tried to compile 2.6.27.8. I get the same error.

I think I'm slipping into version compatibility hell at this point. Please throw me a rope if you can by way of advice if you can.

Thanks!

-Mike

_______________________________________________
Linuxppc-dev mailing list
[email protected]
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Questions:
1) if I want to cross-compile a kernel later than 2.6.24 to hopefully get better WAN device support (and clearer options for fw loading), which kernel should I try, and which toolchain?

the ltib repository does not appear to have a toolchain newer than gcc-3.4.3-glibc-2.3.6 (for 603e)

Admissions, disclaimers, etc
1) I'm using the same ltib script I have used for the 2.6.24 build with toolchain gcc-3.4.3-glibc-2.3.6 (for 603e).
I'm simply modifying the kernel spec file to use 2.6.28.1 (and specifyin a custom toolchain).
I've also tried to compile 2.6.27.8. I get the same error.

Quoted 8 lines · Mike Timmons

Questions:
1) if I want to cross-compile a kernel later than 2.6.24 to hopefully get better WAN device support (and clearer options for fw loading), which kernel should I try, and which toolchain?

the ltib repository does not appear to have a toolchain newer than gcc-3.4.3-glibc-2.3.6 (for 603e)

Quoted 7 lines

Admissions, disclaimers, etc
1) I'm using the same ltib script I have used for the 2.6.24 build with toolchain gcc-3.4.3-glibc-2.3.6 (for 603e).
I'm simply modifying the kernel spec file to use 2.6.28.1 (and specifyin a custom toolchain).
I've also tried to compile 2.6.27.8. I get the same error.

Mike:

Denx's ELDK 4.1 or 4.2 make a great "It Just Works" solution. I've used 4.1 running from 2.6.23 up to 2.6.27.11 and 4.2 from 2.6.26 to 2.6.27.11 with zero problems or issues.

Regards,

Grant Erickson

Questions:
1) if I want to cross-compile a kernel later than 2.6.24 to hopefully get better WAN device support (and clearer options for fw loading), which kernel should I try, and which toolchain?