linux-kernel - Re: [PATCH] rt2800pci: rt2800usb: Firmware update

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 12 Apr 2011 00:34:22 -0500
From:	Larry Finger <Larry.Finger@...inger.net>
To:	RA-Shiang Tu <Shiang_Tu@...inktech.com>
CC:	Walter Goldens <goldenstranger@...oo.com>,
	Xose Vazquez Perez <xose.vazquez@...il.com>,
	"dwmw2@...radead.org" <dwmw2@...radead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"gwingerde@...il.com" <gwingerde@...il.com>,
	"ben@...adent.org.uk" <ben@...adent.org.uk>,
	"users@...x00.serialmonkey.com" <users@...x00.serialmonkey.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: Re: [PATCH] rt2800pci: rt2800usb: Firmware update

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/