Return-path: Received: from nm17-vm0.bullet.mail.bf1.yahoo.com ([98.139.213.157]:28124 "HELO nm17-vm0.bullet.mail.bf1.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1755785Ab1DKUJQ (ORCPT ); Mon, 11 Apr 2011 16:09:16 -0400 Message-ID: <312743.30438.qm@web161611.mail.bf1.yahoo.com> Date: Mon, 11 Apr 2011 13:09:15 -0700 (PDT) From: Walter Goldens Subject: Re: [PATCH] rt2800pci: rt2800usb: Firmware update To: Xose Vazquez Perez Cc: dwmw2@infradead.org, Larry Finger , linux-kernel@vger.kernel.org, gwingerde@gmail.com, ben@decadent.org.uk, users@rt2x00.serialmonkey.com, linux-wireless@vger.kernel.org, Shiang Tu In-Reply-To: <4DA33FFD.5070004@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: > > 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.