From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-kernel@vger.kernel.org
Cc: James.Bottomley@HansenPartnership.com
Subject: [PATCH: NEW SUBARCHITECTURE FOR 2.5.31] support for NCR voyager (3/4/5xxx series)
Date: Sun, 18 Aug 2002 10:59:14 -0500 [thread overview]
Message-ID: <200208181559.g7IFxE604241@localhost.localdomain> (raw)
This patch adds SMP (and UP) support for voyager which is an (up to 32 way)
SMP microchannel non-PC architecture.
The only change since 2.5.31 is that the code will now boot with a non-zero
boot cpu id (previously current->cpu was being initialised too late).
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.31.diff (108k)
http://www.hansenpartnership.com/voyager/files/voyager-2.5.31.diff (146k)
You must apply the split diff before applying the voyager one.
These two patches are also available as separate bitkeeper trees (the voyager
tree is a superset of the arch-split one):
http://linux-voyager.bkbits.net/voyager-2.5
http://linux-voyager.bkbits.net/arch-split-2.5
James Bottomley
reply other threads:[~2002-08-18 15:55 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=200208181559.g7IFxE604241@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®