From: David Woodhouse <dwmw2@infradead.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Michael D. Setzer II" <msetzerii@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel Firmware Support
Date: Fri, 10 May 2013 07:17:08 +0100 [thread overview]
Message-ID: <1368166628.3378.46.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20130507172010.GA30610@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
On Tue, 2013-05-07 at 10:20 -0700, Greg KH wrote:
> > But yesterday, I got a message from a different user with screen
> > captures that showed failure of loading the firmware below.
> > Actually, one screen shot with the 7.0.23.0 and another with the
> > 7.0.29.0. Wasn't sure, so I had added all three of th 7.0.x group to
> > a test build of my kernels. Is only the latest needed?
> >
> > ./bnx2x/bnx2x-e1h-7.0.23.0.fw
> > ./bnx2x/bnx2x-e1h-7.0.29.0.fw
> > ./bnx2x/bnx2x-e1h-7.0.20.0.fw
>
> If you are supporting multiple versions of the kernel, that need
> different versions of the firmware package, then you need to include
> all of these to handle that properly.
The linux-firmware tree should include them all, hopefully. We don't
intentionally *remove* old stuff, since that would break old kernels.
Eventually we'll want a way for people to filter out firmware which is
only used by old kernels, when they install or package linux-firmware.
But for now you just get everything.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5745 bytes --]
prev parent reply other threads:[~2013-05-10 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 1:44 Michael D. Setzer II
2013-05-07 2:47 ` Greg KH
2013-05-07 4:56 ` Michael D. Setzer II
2013-05-07 17:20 ` Greg KH
2013-05-10 4:30 ` Michael D. Setzer II
2013-05-10 6:17 ` David Woodhouse [this message]
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=1368166628.3378.46.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msetzerii@gmail.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
all inboxes | Powered by JetHome®