From: Keith Owens <kaos@ocs.com.au>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Alexander Viro <viro@math.psu.edu>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [CFT] initramfs patch
Date: Tue, 31 Jul 2001 11:21:38 +1000 [thread overview]
Message-ID: <31687.996542498@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 30 Jul 2001 17:56:25 EST." <Pine.LNX.3.96.1010730175545.27870C-100000@mandrakesoft.mandrakesoft.com>
On Mon, 30 Jul 2001 17:56:25 -0500 (CDT),
Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
>Eventually I would like to see firmware uploading in initramfs,
>instead of compiling firmware images into the kernel...
<AOL>Me too</AOL>. Building the firmware images as part of kbuild is
wrong, they should be in separate user space packages. One of my
biggest problems with kbuild 2.5 was supporting the firmware build for
sound and SCSI cards in the kernel, it is all ugly special case code.
next prev parent reply other threads:[~2001-07-31 1:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 6:05 [CFT] initramfs patch Alexander Viro
2001-07-30 16:25 ` Alon Ziv
2001-07-30 15:33 ` Keith Owens
2001-07-30 19:56 ` Anthony de Boer
2001-07-30 20:05 ` Alexander Viro
2001-07-30 20:29 ` Mike Touloumtzis
2001-07-30 20:49 ` Alexander Viro
2001-07-30 21:14 ` Mike Touloumtzis
2001-07-30 22:16 ` Bill Pringlemeir
2001-07-30 22:37 ` Mike Touloumtzis
2001-07-30 20:50 ` Jeff Garzik
2001-07-30 21:09 ` Mike Touloumtzis
2001-07-31 6:46 ` Eric W. Biederman
2001-08-11 0:27 ` David Woodhouse
2001-07-30 22:56 ` Jeff Garzik
2001-07-31 1:21 ` Keith Owens [this message]
2001-07-31 3:09 ` Alexander Viro
2001-08-02 22:46 ` [CFT] initramfs patch (2.4.8-pre3) Alexander Viro
2001-08-04 20:49 ` Ken Moffat
2001-08-05 7:07 ` Alexander Viro
2001-08-05 7:12 ` Alexander Viro
2001-08-05 20:39 ` Ken Moffat
2001-08-05 20:47 ` Alexander Viro
2001-08-06 20:16 ` Ken Moffat
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=31687.996542498@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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