From: Alan Nishioka <alan@nishioka•com>
To: mike_timmons@trimble•com
Cc: linuxppc-dev@ozlabs•org
Subject: Re: kernel 2.6.24 USB wi fi device firmware loading issue(s): rt73.bin...
Date: Wed, 04 Feb 2009 11:14:04 -0800 [thread overview]
Message-ID: <4989E8FC.9090002@nishioka.com> (raw)
In-Reply-To: <4989C635.1050605@trimble.com>
request_firmware uses the hotplug code so the kernel doesn't have any
sourceless binaries compiled into it. on init, the driver requests the
firmware, user mode hotplug daemon loads the firmware from disk and
gives the driver a pointer to it.
since this is a short term problem, i would suggest converting rt73.bin
to a header file and compiling it into the kernel. you have to make a
few minor changes to where request_firmware is called, but in the end
firmware is just an array of bytes with a pointer to it. this is what i
did when i was testing usb wifi a little while ago.
i am probably going to open source hell for suggesting this, but i'm a
hardware engineer, so i am in hell already.
alan nishioka
Mike Timmons wrote:
> I received great help last week in getting a USB wi fi device working.
> Thanks again, but can someone read below and advise me on kernel
> 2.6.24? The best out-of-the box solution for me was 2.6.27.8, for
> which I needed a Denx eldx toolchain in place of the toolchain I was
> using to compile 2.6.24. The significance of all this is that I did
> get USB wi fi working, but...
>
> I'm not in a position to upgrade from 2.6.24 at this time. I need to
> get the USB wi wi (Linksys WUSB54GC) working under 2.6.24.
next prev parent reply other threads:[~2009-02-04 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 16:45 kernel 2.6.24 USB wi fi device firmware loading issue(s): rt73.bin Mike Timmons
2009-02-04 19:14 ` Alan Nishioka [this message]
2009-02-04 20:18 ` Matt Gessner
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=4989E8FC.9090002@nishioka.com \
--to=alan@nishioka$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mike_timmons@trimble$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox