From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Pavel Machek <pavel@suse.cz>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH: NEW ARCHITECTURE FOR 2.5.3] support for NCR voyager
Date: Sat, 09 Feb 2002 13:47:18 -0500 [thread overview]
Message-ID: <200202091847.g19IlIq02443@localhost.localdomain> (raw)
In-Reply-To: Message from Pavel Machek <pavel@suse.cz> of "Sat, 09 Feb 2002 19:00:58 +0100." <20020209180057.GB113@elf.ucw.cz>
pavel@suse.cz said:
> Maybe you should stop calling it new architecture? Its mostly
> i386-compatible, right?
It's x86 based, and like all good x86 machines, it has a mode where it will
boot on a single CPU and look like a microchannel PC. However, the voyagers
were designed to be large multi-CPU SMP machines. For SMP, it is completely
incompatible with the APIC/IO-APIC architecture which linux supports, so the
voyager patches provide a completely different SMP HAL, which had to be
written from scratch; it's not merely a modification of the existing one.
> BTW are those "current" machines, or is their production already
> stopped?
I believe the last data centre machines (the 32 CPU 51xx series) rolled off
NCR's production lines in 2001, so it is pretty much an obsolete machine now.
James
next prev parent reply other threads:[~2002-02-09 18:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 18:25 James Bottomley
2002-02-09 18:00 ` Pavel Machek
2002-02-09 18:47 ` James Bottomley [this message]
2002-02-11 9:00 ` Andrey Panin
2002-02-11 12:05 ` Dave Jones
2002-02-11 13:41 ` Alan Cox
2002-02-11 15:08 ` 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=200202091847.g19IlIq02443@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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®