From: Ben Hutchings <ben@decadent.org.uk>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: netdev@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Michael Chan <mchan@broadcom.com>,
David Miller <davem@davemloft.net>
Subject: Re: In tree firmware not kept up to date
Date: Tue, 17 Apr 2012 20:03:22 +0100 [thread overview]
Message-ID: <20120417190322.GA3932@decadent.org.uk> (raw)
In-Reply-To: <1334675504.23948.99.camel@zakaz.uk.xensource.com>
On Tue, Apr 17, 2012 at 04:11:44PM +0100, Ian Campbell wrote:
> Hello,
>
> What is the current policy wrt keeping the in-tree firmware updated
> alongside the drivers?
Muddled.
> I use CONFIG_FIRMWARE_IN_KERNEL but a couple of times[0] recently this
> has failed me because the in-tree bnx2 driver requires
> bnx2/bnx2-mips-09-6.2.1b.fw but the tree contains
> firmware/bnx2/bnx2-mips-09-6.2.1a.fw.ihex and not 6.2.1b.
>
> Is it a bug that bnx2 was updated without adding the new firmware or is
> a bug that the obsolete firmware is still sitting in the tree?
It's a bug that any firmware is still in-tree, but
CONFIG_FIRMWARE_IN_KERNEL hasn't yet been made to work with a separate
linux-firmware directory.
Ben.
> Ian.
>
> [0] It's possible the same thing and I've just tripped over it more than
> once now.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
next prev parent reply other threads:[~2012-04-17 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 15:11 In tree firmware not kept up to date Ian Campbell
2012-04-17 17:01 ` Michael Chan
2012-04-17 19:03 ` Ben Hutchings [this message]
2012-04-18 9:13 ` Ian Campbell
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=20120417190322.GA3932@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@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).