From: David Woodhouse <dwmw2@infradead.org>
To: Hans de Goede <hdegoede@redhat.com>,
chi-hsien.lin@cypress.com,
Christopher Rumpf <Christopher.Rumpf@cypress.com>,
Chung-Hsien Hsu <cnhu@cypress.com>
Cc: linux-firmware@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Updating cypress/brcm firmware in linux-firmware for CVE-2019-15126
Date: Thu, 05 Mar 2020 11:16:46 +0200 [thread overview]
Message-ID: <40403657934d090d4668916a02878f476b34c9fd.camel@infradead.org> (raw)
Message-ID: <20200305091646.KCGxcFrAsePH97biIJZaUnQSxTByzo6lIzemwYxMjIg@z> (raw)
In-Reply-To: <17ec344e-80c5-02a9-59a3-35789a2eaaf9@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
On Thu, 2020-03-05 at 07:24 +0100, Hans de Goede wrote:
> > also clm_blob download is not supported in kernels prior to 4.15 so
> > those files won't work with older kernels.
>
> That is a valid concern, I'm not sure what the rules for linux-firmware
> are with regards to this.
Not quite sure I understand the problem.
The rules for Linux firmware are just the same as basic engineering
practice for loadable libraries.
If you change the ABI, you change the "soname" of a library, which
equates to changing the filename of a linux-firmware object.
So if you make a new file format for the firmware which requires new
driver support, then you give it a new name. The updated driver can
attempt to load the old firmware filename as a fallback, if it still
supports that, or you just have a clean separation between the two.
The linux-firmware repository then carries *both* files, supporting
both old and new kernels in parallel.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2020-03-05 9:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 22:16 Updating cypress/brcm firmware in linux-firmware for CVE-2019-15126 Hans de Goede
2020-02-26 22:16 ` Hans de Goede
2020-03-04 11:45 ` Hans de Goede
2020-03-04 11:45 ` Hans de Goede
2020-03-05 3:50 ` Chi-Hsien Lin
2020-03-05 3:50 ` Chi-Hsien Lin
2020-03-05 6:24 ` Hans de Goede
2020-03-05 6:24 ` Hans de Goede
2020-03-05 9:16 ` David Woodhouse [this message]
2020-03-05 9:16 ` David Woodhouse
2020-03-05 14:00 ` Hans de Goede
2020-03-05 14:00 ` Hans de Goede
2020-03-06 9:58 ` Chi-Hsien Lin
2020-03-06 9:58 ` Chi-Hsien Lin
2020-03-18 22:06 ` Hans de Goede
2020-03-18 22:06 ` Hans de Goede
2020-03-19 12:41 ` Hans de Goede
2020-03-19 12:41 ` Hans de Goede
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=40403657934d090d4668916a02878f476b34c9fd.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=Christopher.Rumpf@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=cnhu@cypress.com \
--cc=hdegoede@redhat.com \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).