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 17:01:17 +0000
From:	"Michael Chan" <mchan@...adcom.com>
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>,
	"David Miller" <davem@...emloft.net>,
	"Ben Hutchings" <bhutchings@...arflare.com>
Subject: Re: In tree firmware not kept up to date

On Tue, 2012-04-17 at 16:11 +0100, Ian Campbell wrote: 
> Hello,
> 
> What is the current policy wrt keeping the in-tree firmware updated
> alongside the drivers?
> 
> 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?

We probably should remove the obsolete firmware in the kernel tree.  All
the firmware files to support old and new kernels are here:

git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git



--
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