linux-kernel - Re: [PATCH] bnx2 - use request

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-next>] [day] [month] [year] [list]

Date:	Sat, 05 Jul 2008 10:44:01 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Bastian Blank <bastian@...di.eu.org>
Cc:	Michael Chan <mchan@...adcom.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] bnx2 - use request_firmware()

On Sat, 2008-07-05 at 00:54 +0200, Bastian Blank wrote:
> Hi David
> 
> This patch is used by Debian since 2.6.25 to use request_firmware in the
> bnx2 driver. It lacks a small piece of inline patching for now.
> 
> The firmware files includes 7 firmwares with up to 3 sections plus some
> additional initialisation data. The corresponding firmware file
> generator is located at
> svn://svn.debian.org/kernel/dists/trunk/firmware-nonfree/bnx2/fwcutter.
> 
> Signed-off-by: Bastian Blank <waldi@...ian.org>

Thanks for that. I had said I was going to stop working on drivers/net
for now though, so I'm not sure whether to apply it right now. Do you
have any more of these patches, for _non_ network drivers?

The firmware tree is intended to be obviously correct and uncontentious,
just updating drivers to what is common practice these days _anyway_,
with a few other things to make that easier for users.

Given that the majority of normal people are happy with it, we can cope
with a small amount of mostly-unfounded whinging, which we've got from
_both_ of the extreme ends of the spectrum as we try to find a sensible
path somewhere in the middle. But I don't want to provoke it further
right now, so I'm quite tempted to leave this patch until later, to
ensure that the tantrums from the network maintainers don't get in the
way of the rest of the real work and cleanups we're doing.

But if _Michael_ signs off on it, and if you can provide it in the form
used in the firmware-2.6.git tree, with the firmware files added into
the firmware/ subdirectory so they're still being shipped with the
kernel and the user doesn't have to go find them elsewhere, then I
suppose I'll probably take it.

I believe you no longer need to 'select FW_LOADER', btw.

-- 
dwmw2

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