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.21] support for NCR voyager (3/4/5xxx series)
Date: Sun, 09 Jun 2002 13:54:00 -0400 [thread overview]
Message-ID: <200206091754.g59Hs0d08560@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 updates and
changes to the arch-split and a few #include file additions.
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.21.diff (165k)
http://www.hansenpartnership.com/voyager/files/voyager-2.5.21.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 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
next reply other threads:[~2002-06-09 17:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 17:54 James Bottomley [this message]
2002-06-13 8:20 ` Andrey Panin
2002-06-13 15:48 ` James Bottomley
2002-06-13 23:17 ` Dave Jones
2002-06-14 0:13 ` James Bottomley
2002-06-14 0:45 ` Dave Jones
2002-06-14 2:19 ` Matthew D. Pitts
2002-06-14 2:52 ` SCSI host/channel/lun/part to /dev/sd* or maj/minor mapping Mark Atwood
2002-06-14 13:41 ` [PATCH: NEW SUBARCHITECTURE FOR 2.5.21] support for NCR voyager (3/4/5xxx series) Andrey Panin
2002-06-14 13:49 ` Dave Jones
2002-06-14 13:52 ` Andrey Panin
2002-06-14 14:14 ` James Bottomley
2002-06-14 14:16 ` Dave Jones
2002-06-17 13:36 ` Andrey Panin
2002-06-17 14:03 ` Dave Jones
2002-06-16 0:00 ` 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=200206091754.g59Hs0d08560@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®