From: Andreas Jochens <aj@andaco.de>
To: Wichert Akkerman <wichert@wiggy.net>
Cc: "David S. Miller" <davem@redhat.com>,
jgarzik@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tg3 driver - make use of binary-only firmware optional
Date: Mon, 19 Apr 2004 17:41:37 +0200 [thread overview]
Message-ID: <20040419154137.GA4885@andaco.de> (raw)
In-Reply-To: <20040419085809.GA585@wiggy.net>
On 04-Apr-19 10:58, Wichert Akkerman wrote:
> Is there any reason for not using the hotplug firmware infrastructure?
I had the hotplug mechanism in mind when I moved the three firmware
images from tg3.c to three separate firmware files in my first patch.
I thought of this as a first step which could be followed by
converting the driver to use the hotplug firmware
infrastructure and moving the firmware images to user space.
However, since a patch putting the firmware in separate files doesn't
seem to be welcome, I doubt that a conversion to use the hotplug
mechanism will be accepted because this would separate the firmware
and the driver even more.
In any case, making the use of the firmware optional by introducing
CONFIG_TIGON3_FIRMWARE seems to make sense. A later conversion to the
hotplug firmware mechanism will always be possible.
Regards
Andreas Jochens
next prev parent reply other threads:[~2004-04-19 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-18 13:55 [PATCH] tg3 driver - make use of binary-only firmware optional Andreas Jochens
2004-04-18 21:02 ` walt
2004-04-19 1:08 ` David S. Miller
2004-04-19 8:04 ` Andreas Jochens
2004-04-19 8:58 ` Wichert Akkerman
2004-04-19 15:41 ` Andreas Jochens [this message]
2004-04-19 15:49 ` Jeff Garzik
2004-04-19 15:52 ` Jeff Garzik
2004-04-19 18:12 ` [PATCH] tg3 driver - address error in TSO firmware code Andreas Jochens
2004-04-19 18:25 ` David S. Miller
2004-04-19 18:32 ` Jeff Garzik
2004-04-19 18:33 ` David S. Miller
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=20040419154137.GA4885@andaco.de \
--to=aj@andaco.de \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wichert@wiggy.net \
/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