From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Denys Vlasenko <vda.linux@googlemail.com>,
Valdis.Kletnieks@vt.edu, David Miller <davem@davemloft.net>,
mchan@broadcom.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] bnx2: factor out gzip unpacker
Date: Fri, 21 Sep 2007 18:33:39 -0400 [thread overview]
Message-ID: <46F446C3.9050600@garzik.org> (raw)
In-Reply-To: <20070921220333.3b31afb5@the-village.bc.nu>
Alan Cox wrote:
>> For example, bnx2 maintainer says that driver and
>> firmware are closely tied for his driver. IOW: you upgrade kernel
>> and your NIC is not working anymore.
>>
>> Another argument is to make kernel be able to bring up NICs
>> without needing firmware images in initramfs/initrd/hard drive.
>
> dgrs should be using the request_firmware interface. Actually dgrs is
> probably a good candidate for /dev/null
According to an earlier thread, dgrs was never really maintained,
written for hardware that was never really distributed widely, and very
likely hasn't had users in years... if ever.
If that picture is accurate (it's a story I was told), then I am
definitely queueing up a deletion patch.
Jeff
next prev parent reply other threads:[~2007-09-21 22:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 11:01 [PATCH 1/2] bnx2: factor out gzip unpacker Denys Vlasenko
2007-09-21 11:03 ` [PATCH 2/2] bnx2: move gzip unpacker to zlib Denys Vlasenko
2007-09-21 16:14 ` [PATCH 1/2] bnx2: factor out gzip unpacker David Miller
2007-09-21 17:03 ` Denys Vlasenko
2007-09-21 17:49 ` David Miller
2007-09-21 18:05 ` Denys Vlasenko
2007-09-21 18:36 ` Valdis.Kletnieks
2007-09-21 19:18 ` Denys Vlasenko
2007-09-21 19:32 ` Valdis.Kletnieks
2007-09-21 19:33 ` Krzysztof Oledzki
2007-09-21 22:43 ` Denys Vlasenko
2007-09-21 22:57 ` Jeff Garzik
2007-09-21 21:03 ` Alan Cox
2007-09-21 22:33 ` Jeff Garzik [this message]
2007-09-21 22:48 ` Alan Cox
2007-09-22 0:02 ` maximilian attems
2007-09-21 20:13 ` Andi Kleen
2007-09-21 20:31 ` Roland Dreier
2007-09-21 22:37 ` Denys Vlasenko
2007-09-24 17:32 ` Lennart Sorensen
2007-09-25 4:20 ` Kyle Moffett
2007-09-22 2:47 ` Michael Chan
2007-10-01 0:57 ` David 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=46F446C3.9050600@garzik.org \
--to=jeff@garzik.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=vda.linux@googlemail.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