From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.178]) by ozlabs.org (Postfix) with ESMTP id 3CDD8DE0B0 for ; Fri, 30 Jan 2009 07:16:50 +1100 (EST) Received: by el-out-1112.google.com with SMTP id s27so64685ele.3 for ; Thu, 29 Jan 2009 12:16:48 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <498208E0.7000707@trimble.com> References: <498208E0.7000707@trimble.com> Date: Thu, 29 Jan 2009 20:16:47 +0000 Message-ID: Subject: Re: toolchain for building linux-2.6.27.8 or 2.6.28.1 ... From: Bruno Monteiro To: mike_timmons@trimble.com Content-Type: multipart/alternative; boundary=000e0cd1a1fc985c420461a4c4b2 Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --000e0cd1a1fc985c420461a4c4b2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Mike, For cross compile issue you should try crosstool-ng. It works fine with ppc 405. Regards, Bruno On Thu, Jan 29, 2009 at 7:52 PM, Mike Timmons wrote: > 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 > Linuxppc-dev@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-dev > --000e0cd1a1fc985c420461a4c4b2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Mike,

For cross compile issue you should try crosstool-ng. It works = fine with ppc 405.

Regards,
Bruno

On Thu, Jan 29, 2009 at 7:52 PM, Mike Timmons <mike_timmons@trimble.com> wrote:

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 selec= t the following Kconfig options

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

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 fig= ured 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 bui= ld my 2.6.24 kernel.
-It looks like somewhere after 2.6.24 this toolchain stopped successfully c= ompiling the kernel.

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

OBJCOPY arch/powerpc/kernel/vdso32/vdso32.so
objcopy: Unable to recognise the format of the input file `arch/powerpc/ker= nel/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 b= etter 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 gc= c-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 specifyi= n 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. Ple= ase throw me a rope if you can by way of advice if you can.

Thanks!

-Mike

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@o= zlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

--000e0cd1a1fc985c420461a4c4b2--