Messages in this thread | | | Date | Fri, 17 Feb 2012 14:26:46 -0500 | From | Neil Horman <> | Subject | Re: pull request: linux-firmware: update cxgb* firmwares |
| |
On Fri, Feb 17, 2012 at 03:41:34AM +0000, Ben Hutchings wrote: > On Wed, 2012-02-15 at 23:18 -0800, Divy Le Ray wrote: > [...] > > The following changes since commit 38118a598df73d5a9fd72bf04910e8298db82a46: > > > > linux-firmware: brcm: add firmware for bcm43236 usb device > > (2012-02-11 19:20:10 +0000) > > > > are available in the git repository at: > > git://git.chelsio.net/pub/git/linux-firmware for-upstream > > > > 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 > > Are there any versions of the cxgb4 driver that will specifically > request cxgb4/t4fw-1.3.10.0.bin? If not, what's the point of keeping it > around after changing the cxgb4/t4fw.bin symlink? > > Ben. > I think the right thing to do is update the chelsio driver to do exactly that, request a specific version of firmware (or range of versions), like most other drivers do. That way a single system can boot kernels with varying driver versions, each of which may require a different firmware api level. Regards Neil
> > Cheers, > > Divy > > > > > > -- > Ben Hutchings > Beware of programmers who carry screwdrivers. - Leonard Brandwein
| |