linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: users@rt2x00.serialmonkey.com, linux-wireless@vger.kernel.org,
	ben@decadent.org.uk
Subject: Re: Firmware files for Ralink RT28x0
Date: Sun, 10 Apr 2011 21:25:30 +0200	[thread overview]
Message-ID: <4DA2042A.3010301@gmail.com> (raw)

Ben Hutchings wrote:

> Ralink provides multiple drivers per bus type for RT28xx and later
> chips.  For PCI devices they split between RT2860 and RT309x; for USB
> devices they split between RT2870 and RT307x (I think - the chip model
> numbers don't seem to be stated consistently).
> 
> In addition, the USB drivers have two separate images packed together
> and they can select different images based on the controller version:
> 
> #ifdef RTMP_MAC_USB
> 		if ((Version != 0x2860) && (Version != 0x2872) && (Version != 0x3070)) 
> 		{	// Use Firmware V2.
> 			//printk("KH:Use New Version,part2\n");
> 			pFirmwareImage = (PUCHAR)&FirmwareImage[FIRMWAREIMAGEV1_LENGTH];
> 			FileLength = FIRMWAREIMAGEV2_LENGTH;
> 		}
> 		else
> 		{
> 			//printk("KH:Use New Version,part1\n");
> 			pFirmwareImage = FirmwareImage;
> 			FileLength = FIRMWAREIMAGEV1_LENGTH;
> 		}
> #endif // RTMP_MAC_USB //
> 
> The firmware blobs in RT2870 version 2009-08-20 and RT3070 version
> 2009-05-25 are all marked as version 17 (or 0.17), but *they all have
> different contents*.
> 
> I attempted to maintain the same version selection logic when converting
> the staging drivers to use the firmware loader, since I assumed there
> was a good reason for it.
> 

As you can see in the ralink web[1] RT28XX/RT30XX USB devices (RT2870/RT2770/RT3572/RT3070)
need _only_ the rt2870.bin fw-file.

And RT28XX/RT30XX PCI/mPCI/PCIe/CardBus devices
(RT2760/RT2790/RT2860/RT2890/RT3060/RT3062/RT3562/RT2860/RT2760/RT2890/RT2790/RT3090)
need _only_ the rt2860.bin fw-file.

> linux-firmware is supposed to have all firmware files referenced by any
> version of Linux

That's a good joke!
linux-firmware is *unmaintained* , a lot of firmwares are missing.
Even the intel ones(microcode.dat, ipw2{1,2}*), zd1211, etc...
Others are very old, really it's a mess.
Fedora puts _forty_ patches on top of linux-firmware.

[1] http://www.ralinktech.com/support.php?s=2

             reply	other threads:[~2011-04-10 19:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-10 19:25 Xose Vazquez Perez [this message]
2011-04-10 21:03 ` Firmware files for Ralink RT28x0 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-11  3:06         ` Firmware for rt2800pci and rt2800usb Larry Finger
2011-04-11  5:48           ` Steev Klimaszewski
2011-04-11  9:12           ` Gertjan van Wingerde
2011-04-11 13:01             ` Larry Finger
2011-04-11 13:32               ` Gertjan van Wingerde
2011-04-11 15:05               ` Johannes Stezenbach
2011-04-11 11:14           ` Juan Carlos Garza
2011-04-11 11:23             ` Ben Hutchings
2011-04-11 12:21               ` Juan Carlos Garza
2011-04-11 13:19               ` Larry Finger
2011-04-11 14:56           ` Chí-Thanh Christopher Nguyễn
  -- strict thread matches above, loose matches on Subject: below --
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
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=4DA2042A.3010301@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=linux-wireless@vger.kernel.org \
    --cc=users@rt2x00.serialmonkey.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).