From: Geert Uytterhoeven <geert@linux-m68k.org>
To: blaisorblade_spam@yahoo.it
Cc: Andrew Morton <akpm@osdl.org>, Jeff Dike <jdike@addtoit.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
User-mode Linux Kernel Development
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [patch 1/1] Refer to CONFIG_USERMODE, not to CONFIG_UM
Date: Fri, 10 Sep 2004 21:11:37 +0200 (MEST) [thread overview]
Message-ID: <Pine.GSO.4.58.0409102109330.9294@waterleaf.sonytel.be> (raw)
In-Reply-To: <20040910170859.24ABDC74B@zion.localdomain>
On Fri, 10 Sep 2004 blaisorblade_spam@yahoo.it wrote:
> We should also figure out how to make the config process work better for UML.
> We would like to make UML able to "source drivers/Kconfig" and have the right
> drivers selectable (i.e. LVM, ramdisk, and so on) and the ones for actual
> hardware excluded. I've been reading such a request even from Jeff Dike at the
> last Kernel Summit, (in the lwn.net coverage) but without any followup.
Yes, I agree 100%!
Drivers for `modern' hardware (e.g. PCI, USB), shouldn't be a problem, since
they have good dependencies.
`legacy' hardware is more of a problem. Since the consensus was that CONFIG_ISA
is meant to indicate ISA slots, perhaps we need something like CONFIG_XBUS to
mark all these legacy drivers?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2004-09-10 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 17:08 blaisorblade_spam
2004-09-10 19:11 ` Geert Uytterhoeven [this message]
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=Pine.GSO.4.58.0409102109330.9294@waterleaf.sonytel.be \
--to=geert@linux-m68k.org \
--cc=akpm@osdl.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.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
all inboxes | Powered by JetHome®