linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Ivo Van Doorn <ivdoorn@gmail.com>
Cc: Gertjan van Wingerde <gwingerde@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: Firmware files for Ralink RT28x0
Date: Sun, 10 Apr 2011 20:04:01 +0100	[thread overview]
Message-ID: <1302462241.5282.232.camel@localhost> (raw)
In-Reply-To: <BANLkTi=o3P7PbcjW1n_dnhtwX08UE4t2+Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2745 bytes --]

On Sun, 2011-04-10 at 20:06 +0200, Ivo Van Doorn wrote:
> Hi,
> 
> >> On Sun, Apr 10, 2011 at 5:56 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> >> > 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.
> >>
> >> Well the rt2800pci/usb firmware behavior is consistent with the original
> >> Ralink drivers (Not sure about the staging drivers, I only look to the drivers
> >> on the Ralink website).
> >
> > Are you referring to the #ifdef BIN_IN_FILE code?  This code is not
> > enabled, so you should assume it is broken.  I suspect that it was
> > intended to ease firmware development.
> 
> Not only BIN_IN_FILE, but the .bin files provided in the Ralink package
> itself. At some point I grabbed all .bin files from all Ralink packages,
> and compared them.

But this proves nothing, because the Ralink drivers don't use those
files!

[...]
> > 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*.
> 
> How do you determine this version? I usually check the last couple
> of bytes of the firmware file. (The last 2 bytes of the firmware is the CRC,
> but the 2 bytes before that is the version).

That's exactly what I'm looking at, in the file include/firmware.h.
There are 256 lines * 16 bytes for each image, so the images end with:

RT2870 image 1: 0x00, 0x11, 0xc2, 0x7a 
RT2870 image 2: 0x00, 0x11, 0x77, 0x81
RT3070 image 1: 0x00, 0x11, 0x7b, 0xc4
RT3070 image 2: 0x00, 0x11, 0x65, 0xd3

By the way, there is a comment in common/rtmp_mcu.c which says the
version number for these chips is only 1 byte.

[...]
> > linux-firmware is supposed to have all firmware files referenced by any
                                       ---                              ---
> > version of Linux; therefore these files must not be removed.
> 
> I agree that the firmware should be in linux-firmware, but only if they
> are the latest version (and it is possible to keep them up-to-date). Having
> outdated firmware in the linux-firmware tree only causes more problems.
> 
> > If just two files are sufficient then the other files could be replaced
> > by symlinks to them.
> 
> Why? The patch to remove the staging drivers has been sent out a few
> days ago. After that we only have rt2800pci and rt2800usb drivers,
> so we can get rid of the rt30xx files completely. ;)

No.  Read what I said again.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-10 15:56 Firmware files for Ralink RT28x0 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-10 17:02 Xose Vazquez Perez
2011-04-10 17:29 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 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

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=1302462241.5282.232.camel@localhost \
    --to=ben@decadent.org.uk \
    --cc=gwingerde@gmail.com \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.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 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).