linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
	Ivo Van Doorn <ivdoorn@gmail.com>,
	Xose Vazquez Perez <xose.vazquez@gmail.com>,
	dwmw2@infradead.org, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [rt2x00-users] [PATCH] rt2800pci: rt2800usb: Firmware update
Date: Mon, 11 Apr 2011 13:46:01 -0500	[thread overview]
Message-ID: <4DA34C69.1050508@lwfinger.net> (raw)
In-Reply-To: <4DA3477F.8080709@gmail.com>

On 04/11/2011 01:25 PM, Gertjan van Wingerde wrote:
> On 04/11/11 20:13, Ben Hutchings wrote:
>> On Mon, Apr 11, 2011 at 07:57:15PM +0200, Ivo Van Doorn wrote:
>>>>> From: Shiang Tu<shiang_tu@ralinktech.com>
>>>>>
>>>>> Update firmware for rt2800pci to Version 34 and firmware for rt2800usb to
>>>>> Version 29.
>>>>>
>>>>> Signed-off-by: Shiang Tu<shiang_tu@ralinktech.com>
>>>>> Signed-off-by: Larry Finger<Larry.Finger@lwfinger.net>
>>>>> ---
>>>>>   WHENCE     |    8 ++++----
>>>>>   rt2860.bin |  Bin 8192 ->   8192 bytes
>>>>>   rt2870.bin |  Bin 4096 ->   8192 bytes
>>>>>   3 files changed, 4 insertions(+), 4 deletions(-)
>>>>
>>>> links to rt3070.bin rt3071.bin rt3090.bin ???
>>>
>>> What do you mean? Those files should be deleted from the linux-firmware
>>> package. There is no need to keep them around, as with the removal of
>>> the staging drivers, the last users of those files are gone.
>>
>> Stop repeating this nonsense, Ivo.  If the firmware has been bundled in
>> the Linux tree, that would be correct.  For linux-firmware the policy is
>> different.
>
> It's unbelievable how much fuzz a set of binary firmware files can create.
>
> To be honest, I do not care whether they stay or go, as long as it is very
> clear that rt2x00 does not need, and will never need those files. If they
> stay, I would recommend simply not touching them at all, and leave them as
> they are, so that nothing changes for the people running the staging driver
> (at least with respect to these 3 firmware files).
>
> Larry, it might be best to update your changes to the WHENCE file to clearly
> state that these 3 files are only needed for the staging rt2860sta driver,
> up to kernel 2.6.39 (assuming that that staging driver will be removed in 2.6.40).

Agreed. I'll add that as soon as I get the requested info about what changed 
from Ralink.

I can test if linking rt3090.bin to rt2860.bin works for the PCI device, but I 
have no USB stick for testing. As a result, I'm inclined to leave those files 
intact for the foreseeable future.

Off-Topic: What are some makes/models of USB sticks? If there are some 
inexpensive models on E-bay, I could add to my collection.

Larry

  reply	other threads:[~2011-04-11 18:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 14:27 [PATCH] rt2800pci: rt2800usb: Firmware update Larry Finger
2011-04-11 14:32 ` [rt2x00-users] " Ivo Van Doorn
2011-04-11 14:35 ` Gertjan van Wingerde
2011-04-11 15:18 ` Walter Goldens
2011-04-11 15:33   ` Larry Finger
2011-04-11 17:53   ` Xose Vazquez Perez
2011-04-11 20:09     ` Walter Goldens
2011-04-12  3:14       ` Valdis.Kletnieks
2011-04-12  5:23       ` RA-Shiang Tu
2011-04-12  5:34         ` Larry Finger
2011-04-11 17:49 ` Xose Vazquez Perez
2011-04-11 17:55   ` Luis Correia
2011-04-11 17:59     ` [rt2x00-users] " Ivo Van Doorn
2011-04-11 18:02       ` Luis Correia
2011-04-11 18:18     ` Xose Vazquez Perez
2011-04-11 17:57   ` [rt2x00-users] " Ivo Van Doorn
2011-04-11 18:13     ` Ben Hutchings
2011-04-11 18:25       ` Gertjan van Wingerde
2011-04-11 18:46         ` Larry Finger [this message]
2011-04-11 18:58           ` Richard Farina
2011-04-11 19:58           ` Xose Vazquez Perez
2011-04-11 18:30     ` Xose Vazquez Perez

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=4DA34C69.1050508@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=ben@decadent.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=gwingerde@gmail.com \
    --cc=ivdoorn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).