[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1329184754.3048.33.camel@deadeye>
Date: Tue, 14 Feb 2012 01:59:14 +0000
From: Ben Hutchings <ben@...adent.org.uk>
To: Divy Le Ray <divy@...lsio.com>
Cc: David Woodhouse <dwmw2@...radead.org>, davem@...emloft.net,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Steve Wise <swise@...ngridcomputing.com>, nhorman@...driver.com
Subject: Re: [patch net-next] cxgb3: update firmware version
On Mon, 2012-02-13 at 13:39 -0800, Divy Le Ray wrote:
> On Monday, February 13, 2012 12:43:37 PM, David Woodhouse wrote:
> >
> > On Mon, 2012-02-13 at 12:28 -0800, Divy Le Ray wrote:
> >>
> >> This patch updates the firmware version cxgb3 is requesting to 7.12.0.
> >
> >
> > I'm confused. Your patch doesn't change anything in the driver, except
> > the firmware version. So why is it a "major" change?
>
> Hi David,
>
> cxgb3 embeds the firmware file name it will request at load time.
> It uses the FW_VERSION_* defs to construct the firmware name FW_FNAME
> before calling request_firmware().
> Hence the need to update the firmware minor version.
>
> On the other hand, the driver version update is not a strict requirement
> here.
> I would prefer keeping it though.
The problems with this are:
1. Older kernel versions don't benefit from the firmware update.
2. The old firmware has to be kept in linux-firmware to support those
old kernel versions, and distributions may have to package more
versions.
To avoid this, the firmware filename should only be changed if you make
incompatible changes in the driver/firmware interface.
Ben.
--
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein
Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)
Powered by blists - more mailing lists