[PATCH: NEW ARCHITECTURE FOR 2.5.8] support for NCR voyager (3/4/5xxx series)

[PATCH: NEW ARCHITECTURE FOR 2.5.8] support for NCR voyager (3/4/5xxx series)

[James Bottomley]

This patch adds SMP (and UP) support for voyager which is an (up to 32 way) 
SMP microchannel non-PC architecture.

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.8.diff (269k)
http://www.hansenpartnership.com/voyager/files/voyager-2.5.8.diff (150k)

(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:

http://linux-voyager.bkbits.net/voyager-2.5
http://linux-voyager.bkbits.net/arch-split-2.5

James Bottomley

Re: [PATCH: NEW ARCHITECTURE FOR 2.5.8] support for NCR voyager (3/4/5xxx series)

[Eric W. Biederman]

James Bottomley <James.Bottomley@HansenPartnership.com> writes:

> This patch adds SMP (and UP) support for voyager which is an (up to 32 way) 
> SMP microchannel non-PC architecture.
> 
> 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.8.diff (269k)
> http://www.hansenpartnership.com/voyager/files/voyager-2.5.8.diff (150k)
> 
> (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:
> 
> http://linux-voyager.bkbits.net/voyager-2.5
> http://linux-voyager.bkbits.net/arch-split-2.5

Currently you place the voyager information in the APM table,  which is problematic
for the goal of being able to have a kernel that will support everything,
and it is a little confusing.  There is still plenty of room for the voyager table,
elsewhere so I don't think that is needed.

Please check out include/asm-i386/boot_param.h for an enumeration of where
we actually put the variables.  Since it hasn't made it into the kernel
yet either get out of the linux-kernel mailing list or at:
ftp://download.lnxi.com/pub/src/linux-kernel-patches/boot/linux-2.5.8.boot.diff

Eric

Re: [PATCH: NEW ARCHITECTURE FOR 2.5.8] support for NCR voyager (3/4/5xxx series)

[Dave Jones]

On Wed, Apr 17, 2002 at 11:25:14AM -0600, Eric W. Biederman wrote:

 > Currently you place the voyager information in the APM table,  which is problematic
 > for the goal of being able to have a kernel that will support everything,
 > and it is a little confusing.

Kernels for many of the x86 subarch's that are popping up won't "do the
right thing" on any 'normal' x86 if memory serves me correctly. For eg
a kernel for IBM summit machines won't work on a regular PC.
Getting them to do so would require things like apic.c to become an even
bigger mess than what it currently is

The idea behind the subarch patches is that you get a kernel
specifically for your weirdo machine, whilst keeping the common code
free of ifdefs and other uglies. So we'd end up with perhaps..

 o  regular i386 boot on any PC kernel
    (also things like Athlon etc optimised ones fit here)
 o  IBM summit kernel
 o  NCR Voyager kernel
 o  SGI visws kernel
 o  Whatever other weirdo subarch pops up.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs