From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-kernel@vger.kernel.org
Cc: James.Bottomley@HansenPartnership.com
Subject: [PATCH: NEW ARCHITECTURE FOR 2.5.18] support for NCR voyager (3/4/5xxx series)
Date: Sun, 26 May 2002 20:36:51 -0400 [thread overview]
Message-ID: <200205270036.g4R0aps02234@localhost.localdomain> (raw)
This patch adds SMP (and UP) support for voyager which is an (up to 32 way)
SMP microchannel non-PC architecture.
There's basically nothing different from the 2.5.15 one except for merge fixes
and changes to the tlb and process init code.
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.15.diff (144k)
http://www.hansenpartnership.com/voyager/files/voyager-2.5.15.diff (148k)
(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 (the voyager
tree contains the arch-split tree):
http://linux-voyager.bkbits.net/voyager-2.5
http://linux-voyager.bkbits.net/arch-split-2.5
James Bottomley
reply other threads:[~2002-05-27 0:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200205270036.g4R0aps02234@localhost.localdomain \
--to=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
all inboxes | Powered by JetHome®