linux-kernel - Re: [PATCH] bnx2: update bnx2-mips-09 firmware to bnx2-mips-09-6.2.1b

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:	Fri, 13 Jul 2012 15:09:08 +0100
From:	Chris Webb <chris@...chsys.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	Michael Chan <mchan@...adcom.com>, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org, "David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH] bnx2: update bnx2-mips-09 firmware to bnx2-mips-09-6.2.1b

Eric Dumazet <eric.dumazet@...il.com> writes:

> Have you read firmware/README.AddingFirmware ?

I hadn't, but now I have, and if firmware upgrades are considered 'adding
new firmware', I agree this patch is wrong, and should have just removed the
obsolete bnx2-mips-09-6.2.1a file that is no longer used by the bnx2 driver.

However, not having dealt with cards that need these kinds of horrible
binary blobs before, I'm a little uncertain how I should be building
upstream kernels with CONFIG_FIRMWARE_IN_KERNEL and pulling in the correct
blobs from a linux-firmware checkout.

Is there a more automatic method than going through the source for each
configured driver and setting CONFIG_EXTRA_FIRMWARE manually to list the
relevant firmwares? Is there any way to give the kernel the location of
linux-firmware and have it compile in everything needed for the selected
drivers, as used to happen with the firmware/ subdirectory?
CONFIG_EXTRA_FIRMWARE_DIR doesn't seem to do anything with
CONFIG_EXTRA_FIRMWARE empty, so I don't think it does what I'm hoping?

Cheers,

Chris.
--
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/