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.7] support for NCR voyager (3/4/5xxx series)
Date: Sun, 24 Mar 2002 11:34:31 -0600 [thread overview]
Message-ID: <200203241734.g2OHYV810736@localhost.localdomain> (raw)
This really only tidies up the split out of arch/i386 in the previous release.
It also backs out a fix for the migration_mask physical/logical CPU problems
in 2.5.6 in favour of the official fix.
In response to will it work questions, this is the list of supported types
3430/3360 (Level 4): Works (tested up to 2 way), need sim710 driver for
internal SCSI chip.
345x (Level 5): Works (tested up to 10 way), need NCR_D700 or BusLogic SCSI
card.
35xx (Level 5): Should work up to 16 way (not tested), need NCR_D700 or
BusLogic SCSI card.
4100 (Level 5): Should work (not tested), need NCR_D700 SCSI card. Q720
driver is broken currently, so must use D700 or BusLogic SCSI card.
51xx (Level 5): Should work up to 32 way (not tested). No Q720 driver is a
bit of a problem here since I don't think they support anything else.
The patch is in two parts this time: The i386 sub-architecture split is
separated from the addition of the voyager components
http://www.hansenpartnership.com/voyager/files/split-2.5.7.diff (259k)
http://www.hansenpartnership.com/voyager/files/split-2.5.7.BK (107k)
http://www.hansenpartnership.com/voyager/files/voyager-2.5.7.diff (149k)
http://www.hansenpartnership.com/voyager/files/voyager-2.5.7.BK (288k)
(The split diff is pretty huge because it's actually moving files about). You
must apply the split diff before applying the voyager one.
James Bottomley
reply other threads:[~2002-03-24 17:35 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=200203241734.g2OHYV810736@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®