From: ebiederm@xmission.com (Eric W. Biederman)
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH: NEW ARCHITECTURE FOR 2.5.8] support for NCR voyager (3/4/5xxx series)
Date: 17 Apr 2002 11:25:14 -0600 [thread overview]
Message-ID: <m1wuv6fdad.fsf@frodo.biederman.org> (raw)
In-Reply-To: <200204161601.g3GG1nP03345@localhost.localdomain>
James Bottomley <James.Bottomley@HansenPartnership.com> writes:
> This patch adds SMP (and UP) support for voyager which is an (up to 32 way)
> SMP microchannel non-PC architecture.
>
> The patch is in two parts: The i386 sub-architecture split is
> separated from the addition of the voyager components
>
> http://www.hansenpartnership.com/voyager/files/arch-split-2.5.8.diff (269k)
> http://www.hansenpartnership.com/voyager/files/voyager-2.5.8.diff (150k)
>
> (The split diff is pretty huge because it's actually moving files about). You
> must apply the split diff before applying the voyager one.
>
> These two patches are also available as separate bitkeeper trees:
>
> http://linux-voyager.bkbits.net/voyager-2.5
> http://linux-voyager.bkbits.net/arch-split-2.5
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. There is still plenty of room for the voyager table,
elsewhere so I don't think that is needed.
Please check out include/asm-i386/boot_param.h for an enumeration of where
we actually put the variables. Since it hasn't made it into the kernel
yet either get out of the linux-kernel mailing list or at:
ftp://download.lnxi.com/pub/src/linux-kernel-patches/boot/linux-2.5.8.boot.diff
Eric
next prev parent reply other threads:[~2002-04-17 17:32 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 [this message]
2002-04-17 18:23 ` Dave Jones
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=m1wuv6fdad.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=James.Bottomley@HansenPartnership.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