From: Mike Timmons <mike_timmons@trimble.com>
To: Grant Erickson <gerickson@nuovations.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: toolchain for building linux-2.6.27.8 or 2.6.28.1 AND USB wi fi SUCCESS...
Date: Fri, 30 Jan 2009 15:39:57 -0600 [thread overview]
Message-ID: <498373AD.5040107@trimble.com> (raw)
In-Reply-To: <C5A7544F.14345%gerickson@nuovations.com>
Thank You! I obtained ELDK 4.1 from Denx and built 2.6.27.8 with it. A
couple host tool links were required but the build was pretty painless.
Ultimate goal I startedon early in the week was USB wi fi using the
Linksys WUSB54GC, which requires the ralink rt73 driver.
The 2.6.27.8 menuconfig offered the "firmware" loading options I was
looking for.
I now have a working USB wi fi device.
THANK YOU!
-Mike Timmons
Grant Erickson wrote:
> On 1/29/09 11:52 AM, Mike Timmons wrote:
>
>> 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.
>>
>
> 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
>
>
>
next prev parent reply other threads:[~2009-01-30 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 19:52 toolchain for building linux-2.6.27.8 or 2.6.28.1 Mike Timmons
2009-01-29 20:16 ` Bruno Monteiro
2009-01-29 20:40 ` Grant Erickson
2009-01-30 21:39 ` Mike Timmons [this message]
2009-01-30 23:08 ` Robert Schwebel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=498373AD.5040107@trimble.com \
--to=mike_timmons@trimble.com \
--cc=gerickson@nuovations.com \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.