From: Dave Jones <davej@suse.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH: NEW ARCHITECTURE FOR 2.5.8] support for NCR voyager (3/4/5xxx series)
Date: Wed, 17 Apr 2002 20:23:36 +0200 [thread overview]
Message-ID: <20020417202336.I29982@suse.de> (raw)
In-Reply-To: <200204161601.g3GG1nP03345@localhost.localdomain> <m1wuv6fdad.fsf@frodo.biederman.org>
On Wed, Apr 17, 2002 at 11:25:14AM -0600, Eric W. Biederman wrote:
> Currently you place the voyager information in the APM table, which is problematic
> for the goal of being able to have a kernel that will support everything,
> and it is a little confusing.
Kernels for many of the x86 subarch's that are popping up won't "do the
right thing" on any 'normal' x86 if memory serves me correctly. For eg
a kernel for IBM summit machines won't work on a regular PC.
Getting them to do so would require things like apic.c to become an even
bigger mess than what it currently is
The idea behind the subarch patches is that you get a kernel
specifically for your weirdo machine, whilst keeping the common code
free of ifdefs and other uglies. So we'd end up with perhaps..
o regular i386 boot on any PC kernel
(also things like Athlon etc optimised ones fit here)
o IBM summit kernel
o NCR Voyager kernel
o SGI visws kernel
o Whatever other weirdo subarch pops up.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
prev parent reply other threads:[~2002-04-17 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 16:01 [PATCH: NEW ARCHITECTURE FOR 2.5.8] support for NCR voyager (3/4/5xxx series) James Bottomley
2002-04-17 17:25 ` Eric W. Biederman
2002-04-17 18:23 ` Dave Jones [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=20020417202336.I29982@suse.de \
--to=davej@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
/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