From: David Woodhouse <dwmw2@infradead.org>
To: Bastian Blank <bastian@waldi.eu.org>
Cc: Michael Chan <mchan@broadcom.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bnx2 - use request_firmware()
Date: Sat, 05 Jul 2008 10:44:01 +0100 [thread overview]
Message-ID: <1215251041.3189.69.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20080704225415.GA557@wavehammer.waldi.eu.org>
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@debian.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
next parent reply other threads:[~2008-07-05 9:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080704225415.GA557@wavehammer.waldi.eu.org>
2008-07-05 9:44 ` David Woodhouse [this message]
2008-07-07 4:21 ` Michael Chan
2008-07-07 7:53 ` Bastian Blank
2008-07-07 9:03 ` David Woodhouse
2008-07-07 18:56 ` Michael Chan
2008-07-07 21:38 ` David Miller
2008-07-07 21:19 ` Alan Cox
2008-07-07 22:05 ` David Miller
2008-07-08 6:39 ` Alan Cox
2008-07-08 8:58 ` David Miller
2008-07-09 20:25 ` request_firmware vs. resume (was Re: [PATCH] bnx2 - use request_firmware()) Pavel Machek
2008-07-09 21:13 ` Rafael J. Wysocki
2008-07-09 21:20 ` Theodore Tso
2008-07-09 21:58 ` Rafael J. Wysocki
2008-07-09 22:23 ` Theodore Tso
2008-07-09 22:33 ` Rafael J. Wysocki
2008-07-07 22:08 ` [PATCH] bnx2 - use request_firmware() Jeff Garzik
2008-07-07 23:01 ` David Miller
2008-07-08 6:41 ` Alan Cox
2008-07-08 9:00 ` David Miller
2008-07-08 3:30 ` david
2008-07-08 6:49 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1215251041.3189.69.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=bastian@waldi.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®