From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH: NEW ARCHITECTURE FOR 2.5] support for NCR voyager 343x/345x/4100/51xx architecture
Date: Sun, 23 Dec 2001 13:13:42 -0600 [thread overview]
Message-ID: <200112231913.fBNJDgt01933@localhost.localdomain> (raw)
The NCR voyager architecture is essentially a precursor of the intel APIC one.
The Voyager systems support from one to eight "processor" slots which take
big cards with 1-4 486-686 processors. The difficulties for linux are mainly
that the Interrupts are delivered through the VIC architecture of 8 8259 PIC
dyads (so some processors accept interrupts and some don't); the 8259 dyads
are accessible only locally to the interrupt handling processor, so global
interrupt enable and disable becomes a difficult concept.
Since the architecture support depends fairly intimitely on the existing i386
code, I've slotted it into the i386 architecture directory rather than trying
to create a separate one.
The architecture was released publicly in March 2001 for both the 2.2 and 2.4
kernel series. It has a fairly small user base.
The diffs are ~151k, so I refer to them by URL rather than bunging up the
mailing list. The URL is
http://www.hansenpartnership.com/voyager/files/voyager-2.5.1.diff
All comments welcome.
James Bottomley
next reply other threads:[~2001-12-23 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-23 19:13 James Bottomley [this message]
2001-12-24 0:10 ` [PATCH: NEW ARCHITECTURE FOR 2.5] support for NCR voyager 343x/345x/4100/51xx architecture Dave Jones
2001-12-27 14:09 ` James Bottomley
2001-12-27 15:33 ` Dave Jones
2001-12-24 0:58 ` Rik van Riel
2001-12-27 14:08 ` James Bottomley
2001-12-27 15:34 ` 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=200112231913.fBNJDgt01933@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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