public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Divy Le Ray <divy@chelsio.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: pull request: linux-firmware: update cxgb* firmwares
Date: Sun, 12 Feb 2012 21:52:38 -0800	[thread overview]
Message-ID: <4F38A526.70900@chelsio.com> (raw)
In-Reply-To: <20120211140701.GA5194@neilslaptop.think-freely.org>

On 2/11/2012 6:07 AM, Neil Horman wrote:
> On Fri, Feb 10, 2012 at 07:07:37PM -0800, Divy Le Ray wrote:
>> Hi David,
>>
>> Can you please pull from the following URL?
>>       git://git.chelsio.net/pub/git/linux-firmware.git for-david
>>
>> It contains the following commits:
>> 03cadf2 linux-firmware: update cxgb3 driver firmware to revision 7.12.0
>> 235dfaf linux-firmware: add t4fw-1.4.16.0.bin firmware for cxgb4 driver.
>> e2ea873 linux-firmware: remove current t4fw.bin
>>
>> The following changes since commit 15888a2eab052ac3d3f49334e4f6f05f347a516e:
>>
>>    bnx2x: Adding FW 7.0.29.0 (2011-10-24 16:31:44 +0200)
>>
>> are available in the git repository at:
>>    git://git.chelsio.net/pub/git/linux-firmware.git for-david
>>
>> Divy Le Ray (3):
>>        linux-firmware: remove current t4fw.bin
>>        linux-firmware: add t4fw-1.4.16.0.bin firmware for cxgb4 driver.
>>        linux-firmware: update cxgb3 driver firmware to revision 7.12.0
>>
>>   WHENCE                  |    3 ++-
>>   cxgb3/t3fw-7.12.0.bin   |  Bin 0 ->   31812 bytes
>>   cxgb4/t4fw-1.4.16.0.bin |  Bin 0 ->   298496 bytes
>>   cxgb4/t4fw.bin          |  Bin 241664 ->   0 bytes
>>   4 files changed, 2 insertions(+), 1 deletions(-)
>>   create mode 100755 cxgb3/t3fw-7.12.0.bin
>>   create mode 100644 cxgb4/t4fw-1.4.16.0.bin
>>   delete mode 100644 cxgb4/t4fw.bin
>>
> Deleting the old firmware is a bad idea.  You've haven't modified the driver in
> net or net-next to use the new firmware, and until you do, kernels won't be able
> to find the firmware the driver is requesting.  You should make firmware changes
> addative.  Add new versions of firmware, but keep the old ones (at least for a
> while).  Thank you for moving cxgb4 to a versioned firmware file though.  I
> presume there is a pending update to change the FW_FNAME definition to pending?

Hi Neil,

Thank you for the review. I have updated the patch series with the 
following changes:
- Rename the existing t4fw.bin file as t4fw-1.3.10.0.bin
- Add t4fw.bin as a symlink to the latest t4fw revision.

The driver looks up "t4fw.bin", the symlink allows updates of the FW 
without actually modifying the driver source.
Also, if the firmware revision under /lib/firmware/cxgb4/t4fw.bin is 
more recent than the adapter's embedded FW,
the driver will update it. The FW revisions are forward compatible.

The following changes since commit 15888a2eab052ac3d3f49334e4f6f05f347a516e:

   bnx2x: Adding FW 7.0.29.0 (2011-10-24 16:31:44 +0200)

are available in the git repository at:
   git://git.chelsio.net/pub/git/linux-firmware.git for-david

Divy Le Ray (3):
       linux-firmware: rename t4fw.bin
       linux-firmware: add t4fw-1.4.16.0.bin firmware for cxgb4 driver.
       linux-firmware: update cxgb3 driver firmware to revision 7.12.0

  WHENCE                  |    4 +++-
  cxgb3/t3fw-7.12.0.bin   |  Bin 0 -> 31812 bytes
  cxgb4/t4fw-1.3.10.0.bin |  Bin 0 -> 241664 bytes
  cxgb4/t4fw-1.4.16.0.bin |  Bin 0 -> 298496 bytes
  cxgb4/t4fw.bin          |  Bin 241664 -> 17 bytes
  5 files changed, 3 insertions(+), 1 deletions(-)
  create mode 100755 cxgb3/t3fw-7.12.0.bin
  create mode 100644 cxgb4/t4fw-1.3.10.0.bin
  create mode 100644 cxgb4/t4fw-1.4.16.0.bin
  mode change 100644 => 120000 cxgb4/t4fw.bin

Cheers,
Divy


  reply	other threads:[~2012-02-13  5:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-11  3:07 pull request: linux-firmware: update cxgb* firmwares Divy Le Ray
2012-02-11 14:07 ` Neil Horman
2012-02-13  5:52   ` Divy Le Ray [this message]
2012-02-13 11:37     ` Neil Horman
2012-02-16  7:18     ` Divy Le Ray
2012-02-17  3:41       ` Ben Hutchings
2012-02-17 19:26         ` Neil Horman
2012-02-17 19:30         ` Divy Le Ray
2012-02-19  0:58           ` Ben Hutchings
2012-02-19  1:04             ` Ben Hutchings
2012-02-19  1:35               ` Divy Le Ray

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=4F38A526.70900@chelsio.com \
    --to=divy@chelsio.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nhorman@tuxdriver.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