linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: RA-Shiang Tu <Shiang_Tu@ralinktech.com>
Cc: Walter Goldens <goldenstranger@yahoo.com>,
	Xose Vazquez Perez <xose.vazquez@gmail.com>,
	"dwmw2@infradead.org" <dwmw2@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"gwingerde@gmail.com" <gwingerde@gmail.com>,
	"ben@decadent.org.uk" <ben@decadent.org.uk>,
	"users@rt2x00.serialmonkey.com" <users@rt2x00.serialmonkey.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] rt2800pci: rt2800usb: Firmware update
Date: Tue, 12 Apr 2011 00:34:22 -0500	[thread overview]
Message-ID: <4DA3E45E.3040005@lwfinger.net> (raw)
In-Reply-To: <3CD5C4D3B07007449D2E692F161FEE710933423B@TWHCMBS02.tw.ralinktech.ad>

On 04/12/2011 12:23 AM, RA-Shiang Tu wrote:
> Hi,
>>>> Are there any changelogs for these firmware files? Do
>>> they
>>>> only offer support for newer chips, or are there any
>>> actual
>>>> improvements and bug fixes implemented? Users should
>>> know
>>>> whether updating the firmware will be of any use to
>>> them.
>>>
>>> Shiang Tu from ralink says [1] :
>>> "We always suggest to use latest firmware, because it's backward
>>> compatible and also has some enhancement, bug fix, or
>> support of new
>>> chip.
>>
>> Sorry, but how very ... Microsoft-y of Ralink.
>> Something has changed, a bug, an improvement, but we are to
>> guess what it is?
>> Maybe if people knew how these firmware files affect
>> different generations of chips, they'd knew how to maintain
>> them better. I think this contributes to the mess here.
>>
>
> First of all, thanks for all for the great help to make Ralink chipset can
> work well in Linux.
>
> In deed, restricted by the limited resources, Ralink didn't involve in the
> rt2x00 project development closely for long time and the rt2x00 project
> developers and free contributors only can get limited information from
> Ralink's open source code. I think that' why make the situation becomes
> a little bit complicate. Sorry for that.
>
> Now we try to work closely with rt2x00 project, we also will sumbit latest
> frimware to linux-firmware once have any updates. We are newbie to work
> with open source community, if we have any problem, your kindly help will
> be highly appreciated.

Shiang,

We greatly appreciate the help you have given. We certainly understand the 
problems of limited resources.

Does Ralink have any documentation that you can share regarding the changes in 
rt2860.bin from revision 11, which is now in linux-firmware, to the current 
revision 34. The same information on the changes from revision 12 to revision 29 
of rt2870.bin would also be useful. As you have seen in the E-mails, the details 
are requested for the acceptance of the new versions in linux-firmware.

Thanks,

Larry


  reply	other threads:[~2011-04-12  5:34 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 [this message]
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
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=4DA3E45E.3040005@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=Shiang_Tu@ralinktech.com \
    --cc=ben@decadent.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=goldenstranger@yahoo.com \
    --cc=gwingerde@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).