netdev - RE: [PATCH net-next] qed*: Utilize Firmware 8.15.3.0

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <BL2PR07MB2306300BB972DC9466F08ABA8D200@BL2PR07MB2306.namprd07.prod.outlook.com>
Date:   Fri, 10 Mar 2017 05:49:57 +0000
From:   "Mintz, Yuval" <Yuval.Mintz@...ium.com>
To:     Christoph Hellwig <hch@...radead.org>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
        "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
        "Tayar, Tomer" <Tomer.Tayar@...ium.com>,
        "Amrani, Ram" <Ram.Amrani@...ium.com>,
        "Rangankar, Manish" <Manish.Rangankar@...ium.com>,
        "Dupuis, Chad" <Chad.Dupuis@...ium.com>
Subject: RE: [PATCH net-next] qed*: Utilize Firmware 8.15.3.0

> > We can't just require a new firmware version in the driver, as users
> > most likely won't have it by the time they install the new kernel.  So
> > you'll have to support the old firmware version as well.
> 
> Why not? That has been the paradigm forever.
> 
> The new firmware version is already available in linux-firmware.
> In any reasonable distro that would update the driver, you'd expect they'd
> also update the firmware version on their filesystem.

Just in case it wasn't clear from the original message - 
The firmware discussed here is the binary firmware, not the
management firmware.
For the management firmware [on persistent storage] there is
a backward/forward compatibility scheme in place.