From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: davej@suse.de (Dave Jones), gone@us.ibm.com (Patricia Gaughen),
linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: [RFC] modularization of i386 setup_arch and mem_init in 2.4.18
Date: 10 Mar 2002 20:17:19 -0700 [thread overview]
Message-ID: <m1u1rnztc0.fsf@frodo.biederman.org> (raw)
In-Reply-To: <E16k33p-0006Ra-00@the-village.bc.nu>
In-Reply-To: <E16k33p-0006Ra-00@the-village.bc.nu>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > I will tenatively vote in favor of this kind of action. There
> > are a couple of directions to consider. This is a two dimensional
> > problem.
>
> That should not be suprising
>
> > Dimension 1. Different basic hardware architectures.
> > (pc,numaq,visws,voyager)
> (and others upcoming)
>
> > Dimension 2. Different firmware implementations.
> > (pcbios,linuxbios,openfirmware,acpi?)
>
> i386-pc-pcbios
>
> Maybe autoconf got the concept right. You don't neccessarily want to think
> of it as a grid though. A lot of the stuff is i386-*-pcbios and i386-pc-*
Agreed, there is a lot of potential for sharing.
Eric
next prev parent reply other threads:[~2002-03-11 3:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 21:08 [RFC] modularization of i386 setup_arch and mem_init in 2.4.18 Patricia Gaughen
2002-03-08 21:33 ` Dave Jones
2002-03-08 21:34 ` Greg KH
2002-03-08 21:59 ` [Lse-tech] " Martin J. Bligh
2002-03-08 22:16 ` Dave Jones
2002-03-09 0:00 ` H. Peter Anvin
2002-03-08 23:48 ` Christer Weinigel
2002-03-09 1:15 ` Josh Fryman
2002-03-09 1:21 ` Dave Jones
2002-03-09 1:22 ` Christer Weinigel
2002-03-10 7:27 ` Eric W. Biederman
2002-03-09 7:22 ` [Lse-tech] " Christoph Hellwig
2002-03-10 7:42 ` Eric W. Biederman
2002-03-10 13:08 ` Alan Cox
2002-03-11 3:17 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-08 22:54 James Bottomley
2002-03-11 16:51 James Bottomley
2002-03-12 3:43 ` James Bottomley
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=m1u1rnztc0.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=gone@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@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