linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Ivo Van Doorn <ivdoorn@gmail.com>
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>,
	linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: Firmware files for Ralink RT28x0
Date: Sun, 10 Apr 2011 13:26:29 -0500	[thread overview]
Message-ID: <4DA1F655.1070909@lwfinger.net> (raw)
In-Reply-To: <BANLkTimp6h9x0JC0HzSpKzdbKLOw=ioUvw@mail.gmail.com>

On 04/10/2011 12:35 PM, Ivo Van Doorn wrote:
> Hi.
>
>>> I notice that rt2800{pci,usb} each specify only one firmware image,
>>> regardless of the controller version.
>>>
>>> This is inconsistent with rt28{6,7}0sta and with the firmware images in
>>> linux-firmware.
>>>
>>> If you think that a single image per bus type can cover all controllers,
>>> please identify those firmware images, test them on each hardware
>>> generation, and get them into linux-firmware.
>>
>> querida:/datos/kernel/linux-2.6/drivers/net/wireless/rt2x00 $ grep "\.bin" *
>> rt2800pci.h:#define FIRMWARE_RT2860                     "rt2860.bin"
>> rt2800usb.h:#define FIRMWARE_RT2870                     "rt2870.bin"
>> rt61pci.h:#define FIRMWARE_RT2561                       "rt2561.bin"
>> rt61pci.h:#define FIRMWARE_RT2561s                      "rt2561s.bin"
>> rt61pci.h:#define FIRMWARE_RT2661                       "rt2661.bin"
>> rt73usb.h:#define FIRMWARE_RT2571                       "rt73.bin"
>>
>> rt3070.bin rt3071.bin rt3090.bin should be deleted from linux-firmware.
>> They were only need by staging drivers.
>
> True, but the rt2860 and rt2870 firmware file are outdated in the
> linux-firmware,
> and probably don't support the rt3090 or other more recent chipsets. So before
> they can be removed, those files must be updated.

As I wrote earlier, my RT3090 is supported by rt2860.bin. I haven't tested 
everything, but is functioned in STA and ad-hoc modes.

Larry

  parent reply	other threads:[~2011-04-10 18:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-10 17:29 Firmware files for Ralink RT28x0 Xose Vazquez Perez
2011-04-10 17:35 ` Ivo Van Doorn
2011-04-10 18:12   ` Xose Vazquez Perez
2011-04-10 18:26   ` Larry Finger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-10 19:25 Xose Vazquez Perez
2011-04-10 21:03 ` Ben Hutchings
2011-04-10 21:30   ` Larry Finger
2011-04-10 21:46   ` Xose Vazquez Perez
2011-04-10 22:37     ` Larry Finger
2011-04-10 22:56       ` Xose Vazquez Perez
2011-04-11  3:01         ` Larry Finger
2011-04-10 17:02 Xose Vazquez Perez
2011-04-10 15:56 Ben Hutchings
2011-04-10 16:18 ` Larry Finger
2011-04-10 16:35 ` Ivo Van Doorn
2011-04-10 17:49   ` Ben Hutchings
2011-04-10 18:06     ` Ivo Van Doorn
2011-04-10 19:04       ` Ben Hutchings

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=4DA1F655.1070909@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=users@rt2x00.serialmonkey.com \
    --cc=xose.vazquez@gmail.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).