linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: mike_timmons@trimble.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: any luck with wireless USB adaptors?
Date: Tue, 27 Jan 2009 09:10:00 -0500	[thread overview]
Message-ID: <9e4733910901270610qd40bbacm8f1f1bf0bcc63ae9@mail.gmail.com> (raw)
In-Reply-To: <497EAEAF.3010108@trimble.com>

On Tue, Jan 27, 2009 at 1:50 AM, Mike Timmons <mike_timmons@trimble.com> wrote:
> Thanks. Yes, USB  wi fi is what I'm after.  I did find the driver I needed
> after enabling the WLAN80211 and EXPERIMENTAL options. The device discovery
> appears to work, and with wireless tools I can iwconfig and see my
> interface.
>
> QUESTION: when I "ifoncfig wlan0 up" it results in an attempt to load a
> firmwmare file as follows. as you can see, it fails. What are these firmware
> files? I can't find it in my build output. How do I build it or where do I
> get it? Where would I put it on my target?

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

>
> I did search for answers to these questions and tried to stick an rt73.bin
> of unknown origin (to me anyway) in /lib/firmware but I got the same error.
>
> -sh-2.05b# ifconfig wlan0 up
> [ 2212.027071] phy1 -> rt2x00lib_request_firmware: Info - Loading firmware
> file 'rt73.bin'.
> [ 2272.058793] phy1 -> rt2x00lib_request_firmware: Error - Failed to request
> Firmware.
> SIOCSIFFLAGS: No such file or directory
>
> Thanks again,
> Mike
>
>
>
> \
> Grant Likely wrote:
>>
>> On Mon, Jan 26, 2009 at 8:39 PM, Mike Timmons <mike_timmons@trimble.com>
>> wrote:
>>
>>>
>>> I'm running 2.6.24 with Freescale's lite5200 as my base. I'm interested
>>> in
>>> this USB adaptor for wireless USB, but my web search does not make me
>>> confident that my effort will yield fruit.
>>>
>>> Can anyone direct me to a good source outlining success stories with
>>> wireless USB adaptors? At present I'm mesing with Linksys WUSB54GC and
>>> some
>>> driver source from Ralink, but my cross-compile is not working.
>>>
>>
>> Umm, the WUSB54GC is not a "wireless USB" adapter.  It is a USB WiFi
>> adapter.  If you're looking for wireless USB then it is the wrong
>> device.
>>
>> If you are looking for a suitable wifi adapter, then that device
>> should work, but if you can go with a PCI or a miniPCI WiFi adapter
>> instead then you should get better performance.  The 5200 only has USB
>> 1.1.
>>
>> I'm having good success with an Atheros miniPCI adapter at the moment
>> using a 2.6.28 kernel.
>>
>> g.
>>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>



-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2009-01-27 14:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27  3:39 any luck with wireless USB adaptors? Mike Timmons
2009-01-27  4:26 ` Jon Smirl
2009-01-27  5:01 ` Grant Likely
2009-01-27  6:50   ` Mike Timmons
2009-01-27 14:10     ` Jon Smirl [this message]
2009-01-27 17:28       ` Mike Timmons
2009-01-27 17:55         ` John W. Linville
2009-02-03  5:23         ` kernel 2.6.24 USB wlan firmware loading issue(s): rt73.bin Mike Timmons

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=9e4733910901270610qd40bbacm8f1f1bf0bcc63ae9@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mike_timmons@trimble.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).