Re: I am interested in helping port to Indigo

Re: I am interested in helping port to Indigo

[Alex deVries]

Fernando D. Mato Mira wrote:

> Hello,
>
> What would one need to do to port what is running of SGI/Linux to
> Indigo R4400 150MHz Elan?

One would need to write device drivers for:
- SCSI
- ethernet
- display or serial

I thought the indigo used either gio64 or gio32.  I might be wrong.

Have I missed anything?

- Alex

I am interested in helping port to Indigo

[Fernando D. Mato Mira]

Hello,

What would one need to do to port what is running of SGI/Linux to 
Indigo R4400 150MHz Elan?

Regards,

Re: I am interested in helping port to Indigo

[William J. Earl]

Fernando D. Mato Mira writes:
 > Hello,
 > 
 > What would one need to do to port what is running of SGI/Linux to 
 > Indigo R4400 150MHz Elan?

     By "Indigo R4400", I assume you mean "Indigo2 R4400".  As far as
I know, we only supported the R4000 in the "Indigo R4000".  The 
kernel should be mostly compatible, aside from some details about
clocks, the addition of the EISA bus, and the absence of the video
port.  The big issue is the graphics.  Elan has downloaded microcode,
although you might make do with what is downloaded by the PROM.
Unfortunately, I cannot at present supply documentation for the
interface exported by that microcode (partly because I don't have
any ready to hand).  

Re: I am interested in helping port to Indigo

[William J. Earl]

Alex deVries writes:
 > Fernando D. Mato Mira wrote:
 > 
 > > Hello,
 > >
 > > What would one need to do to port what is running of SGI/Linux to
 > > Indigo R4400 150MHz Elan?
 > 
 > One would need to write device drivers for:
 > - SCSI
 > - ethernet
 > - display or serial
 > 
 > I thought the indigo used either gio64 or gio32.  I might be wrong.

     The original Indigo (R3000-based) used a different chip set from
the Indigo R4000, Indy, and Indigo2, which shared a common memory controller.
The latter machines use vary a bit in the details of their peripheral
chips, the parts are mostly either the same or different mainly in being
later revisions in some of the systems.  The Indigo2 added EISA bus support
(along with GIO). 

Re: I am interested in helping port to Indigo

[Fernando D. Mato Mira]

At 11:28 AM 10/12/98 -0700, you wrote:

> > What would one need to do to port what is running of SGI/Linux to 
> > Indigo R4400 150MHz Elan?
>
>     By "Indigo R4400", I assume you mean "Indigo2 R4400".  As far as

Nope. Indigo "1" R4400 indeed. 

And yes, it's GIO32.

Re: I am interested in helping port to Indigo

[Rob Lembree]

> Perhaps you can supply us with a hinv output and picture of it, as I
>have never heard of an Indigo with a R4400...

SGI did indeed build these with both 100 and 150 MHz processors.
It was called the IP20.

-- 

Rob Lembree                Strategic Software Organization

Silicon Graphics, Inc.                  http://www.sgi.com
One Cabot Road                             rob@lembree.com
Hudson, MA 01749                           lembree@sgi.com
Phone: 978-567-2141                      FAX: 978-567-2341

PGP: 1F EE F8 58 30 F1 B1 20  C5 4F 12 21 AD 0D 6B 29

Re: I am interested in helping port to Indigo

[William J. Earl]

Rob Lembree writes:
 > > Perhaps you can supply us with a hinv output and picture of it, as I
 > >have never heard of an Indigo with a R4400...
 > 
 > SGI did indeed build these with both 100 and 150 MHz processors.
 > It was called the IP20.
...
      I was familiar with the IP20.  I didn't realize that we had shipped
any 150 MHZ R4400 processors for the IP20.

Re: I am interested in helping port to Indigo

[darkaeon]

Fernando D. Mato Mira wrote:

> At 11:28 AM 10/12/98 -0700, you wrote:
>
> > > What would one need to do to port what is running of SGI/Linux to
> > > Indigo R4400 150MHz Elan?
> >
> >     By "Indigo R4400", I assume you mean "Indigo2 R4400".  As far as
>
> Nope. Indigo "1" R4400 indeed.
>
> And yes, it's GIO32.

  Perhaps you can supply us with a hinv output and picture of it, as I
have never heard of an Indigo with a R4400...

-Steve

Re: I am interested in helping port to Indigo

[Rob Lembree]

Here's a hinv from an R4400 Indigo:

CPU: MIPS R4400 Processor Chip Revision: 4.0
FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
1 100 MHZ IP20 Processor
Main memory size: 48 Mbytes
Secondary unified instruction/data cache size: 1 Mbyte on Processor 0
Instruction cache size: 16 Kbytes
Data cache size: 16 Kbytes
Integral SCSI controller 0: Version WD33C93B, revision C
  Disk drive: unit 1 on SCSI controller 0
  Disk drive: unit 2 on SCSI controller 0
On-board serial ports: 2
On-board bi-directional parallel port
Graphics board: GR2-Elan
Integral Ethernet: ec0, version 1
Iris Audio Processor: revision 10
Galileo video  (ev1): unit 0, revision 2.  601 option connected.  

-- 

Rob Lembree                Strategic Software Organization

Silicon Graphics, Inc.                  http://www.sgi.com
One Cabot Road                             rob@lembree.com
Hudson, MA 01749                           lembree@sgi.com
Phone: 978-567-2141                      FAX: 978-567-2341

PGP: 1F EE F8 58 30 F1 B1 20  C5 4F 12 21 AD 0D 6B 29

Re: I am interested in helping port to Indigo

[Christian Reisch]

> 
> > Perhaps you can supply us with a hinv output and picture of it, as I
> >have never heard of an Indigo with a R4400...
> 

[dreamtime:~] hinv
CPU: MIPS R4400 Processor Chip Revision: 5.0
FPU: MIPS R4000 Floating Point Coprocessor Revision: 0.0
1 150 MHZ IP20 Processor
Main memory size: 48 Mbytes
Secondary unified instruction/data cache size: 1 Mbyte on Processor 0
Instruction cache size: 16 Kbytes
Data cache size: 16 Kbytes
Integral SCSI controller 0: Version WD33C93B, revision C
  Disk drive: unit 1 on SCSI controller 0
  Disk drive: unit 2 on SCSI controller 0
  Disk drive: unit 3 on SCSI controller 0
On-board serial ports: 2
On-board bi-directional parallel port
Graphics board: GR2-XS24
Integral Ethernet: ec0, version 1
Iris Audio Processor: revision 10

Re: I am interested in helping port to Indigo

[Fernando D. Mato Mira]

[-- Attachment #1: Type: text/html, Size: 2354 bytes --]