netdev - Re: In tree firmware not kept up to date

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]

Date:	Tue, 17 Apr 2012 20:03:22 +0100
From:	Ben Hutchings <ben@...adent.org.uk>
To:	Ian Campbell <Ian.Campbell@...rix.com>
Cc:	netdev@...r.kernel.org,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Ian Jackson <Ian.Jackson@...citrix.com>,
	Michael Chan <mchan@...adcom.com>,
	David Miller <davem@...emloft.net>
Subject: Re: In tree firmware not kept up to date

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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html