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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1334740425.23948.157.camel@zakaz.uk.xensource.com>
Date:	Wed, 18 Apr 2012 10:13:45 +0100
From:	Ian Campbell <Ian.Campbell@...rix.com>
To:	Ben Hutchings <ben@...adent.org.uk>
CC:	"netdev@...r.kernel.org" <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, 2012-04-17 at 20:03 +0100, Ben Hutchings wrote:
> 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.

Thanks, so the future-proof solution is to clone and install
firmware-linux.gitwhich is currently a rather manual process but will
improve at some point.

Cheers,
Ian.

> 
> Ben.
> 
> > Ian.
> > 
> > [0] It's possible the same thing and I've just tripped over it more than
> > once now.
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ