From eak@cygnus.detroit.sgi.com  Wed Oct  1 13:01:38 1997
Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id NAA06492; Wed, 1 Oct 1997 13:01:29 +0200 (MET DST)
Received-Date: Wed, 1 Oct 1997 13:01:29 +0200 (MET DST)
Received: from dataserv.detroit.sgi.com (relay.detroit.sgi.com [169.238.128.2]) by sgi.sgi.com (950413.SGI.8.6.12/970507) via ESMTP id EAA09080; Wed, 1 Oct 1997 04:01:02 -0700
	env-from (eak@cygnus.detroit.sgi.com)
Received: from cygnus.detroit.sgi.com by dataserv.detroit.sgi.com via ESMTP (940816.SGI.8.6.9/930416.SGI)
	 id GAA02065; Wed, 1 Oct 1997 06:59:43 -0400
Sender: eak@cygnus.detroit.sgi.com
Message-ID: <34322D1F.8AEDE04@cygnus.detroit.sgi.com>
Date: Wed, 01 Oct 1997 06:59:43 -0400
From: Eric Kimminau <eak@cygnus.detroit.sgi.com>
Reply-To: eak@detroit.sgi.com
Organization: Silicon Graphics, Inc
X-Mailer: Mozilla 4.03C-SGI [en] (X11; I; IRIX 6.3 IP32)
MIME-Version: 1.0
To: Ralf Baechle <ralf@cobaltmicro.com>
CC: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: For stability freaks ...
References: <199710010102.SAA22736@dns.cobaltmicro.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 1247
Lines: 34

Ralf Baechle wrote:
> 
> Ok, I said I'd touch 2.0.x for MIPS again when hell freezes.  It was
> damn cold weather the last days and hell has froozen ...
> 
> [root@(none) /]# uname -a
> Linux (none) 2.0.30 #389 Tue Sep 30 17:47:39 PDT 1997 mips unknown
> [root@(none) /]# cat /proc/cpuinfo
> cpu                     : MIPS
> cpu model               : Nevada V1.0
> system type             : Cray YMP  [just kidding ...]
> BogoMIPS                : 131.89
> byteorder               : little endian
> unaligned accesses      : 0
> wait instruction        : yes
> microsecond timers      : yes
> extra interrupt vector  : yes
> 
>   Ralf

Thats quite an impressive BogoMips number for a machine that old...

-- 
Eric Kimminau                           System Engineer/RSA
eak@detroit.sgi.com                     Silicon Graphics, Inc
Voice: (248) 848-4455                   39001 West 12 Mile Rd.
Fax:   (248) 848-5600                   Farmington, MI 48331-2903

                 VNet Extension - 6-327-4455
              "I speak my mind and no one else's."
       http://www.dcs.ex.ac.uk/~aba/rsa/perl-rsa-sig.html

    When confronted by a difficult problem, solve it by reducing 
    it to the question, "How would the Lone Ranger handle this?"

From harald.koerfgen@netcologne.de  Wed Oct  1 20:09:04 1997
Received: from ns1.netcologne.de (ns1.netcologne.de [194.8.194.70]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id UAA09313; Wed, 1 Oct 1997 20:08:59 +0200 (MET DST)
Received-Date: Wed, 1 Oct 1997 20:08:59 +0200 (MET DST)
Received: from franz.netcologne.de by ns1.netcologne.de (8.6.12/NetCologne/marvin/netsafe-a0020)
	id <UAA10622>; Wed, 1 Oct 1997 20:44:02 +0200 with SMTP
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.971001200907.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.0 [p0] on Linux
Sender: harry@franz.netcologne.de
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199709302112.OAA04252@dull.cobaltmicro.com>
Date: Wed, 01 Oct 1997 19:53:34 +0200 (MEST)
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: Re: Linux/MIPS for DECstations...
Content-Length: 2108
Lines: 56

Hi,

On 30-Sep-97 Ralf Baechle wrote:

>Your handler seems to die in the second level exception handler.
>However in buffer_init(), where the vmalloc'ed memory is being cleared,
>the pages are always readable/writeable and therefore that handler should
>never be reached.  Note that the way that handler in head.S is implemented
>the load in the handler should never cause a second fault.
>
>Nevertheless, for your case the superfluous srl instruction shouldn't make
>a difference.  Note that the R3000 exception mechanism is a bit different
>from the R4000, which means I'll have to read a bit ...

Me too...

Ok, all documentation about MIPS Processors are the "IDT R30xx Family Software
Reference Manual" from IDT and the "MIPS R4000 Microprocessor User's Manual" 
from SGI.

[hours later]

After carefully re-resing the IDT Manual ant glance at the SGI Manual, it is my 
understanding, that indeed there is a difference in the exception mechanism
between the R3000 and the R4000.

R4000:
*All* TLB misses cause a TLB refill exception. If a TLB miss happens in the
exception routine itself, a TLBL or TLBS exception is caused. This is handled
bye the general exception handler.

R3000:
*Only* references to KSEG0 (0x00000000- 0x7fffffff) may cause a TLB exception.
TLB misses with references to KSEG2 (0xc0000000 - 0xffffffff !!!) cause a TLBL 
or TLBS exception, which is handled by the general exception handler.

Just to make shure, that I understand this right: can anybody on the list
confirm this?
  
This could explain, why the kernel seems to die in the second level eception
handler. It's simply a reference to the freshly vmalloced hash table.

Paul wrote:

>...I should probably say that I think this code is of dubious
>parentage!  It would probably be best for you to look closely at the
>MMU code.  I was only just getting my head around the R3K MMU when I
>ran out of time to keep working on it, so I'd suggest you might even
>want to throw it away and write it again!

That would be the best. Ok, if nobody else wants to do it, I'll start rewriting
the R3000 TLB stuff.

-- 
cheers
Harald

From harald.koerfgen@netcologne.de  Wed Oct  1 20:19:28 1997
Received: from ns1.netcologne.de (ns1.netcologne.de [194.8.194.70]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id UAA09404; Wed, 1 Oct 1997 20:19:26 +0200 (MET DST)
Received-Date: Wed, 1 Oct 1997 20:19:26 +0200 (MET DST)
Received: from franz.netcologne.de by ns1.netcologne.de (8.6.12/NetCologne/marvin/netsafe-a0020)
	id <UAA11335>; Wed, 1 Oct 1997 20:54:34 +0200 with SMTP
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.971001201939.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.0 [p0] on Linux
Sender: harry@franz.netcologne.de
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <XFMail.971001200907.harald.koerfgen@netcologne.de>
Date: Wed, 01 Oct 1997 20:17:07 +0200 (MEST)
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: Re: Re: Linux/MIPS for DECstations...
Content-Length: 207
Lines: 12

I'm sorry.

On 01-Oct-97 Harald Koerfgen wrote:

>R3000:
>*Only* references to KSEG0 (0x00000000- 0x7fffffff) may cause a TLB exception.
                      ^^^^^

This should have been KUSEG.

cu
Harald 

From dom@algor.co.uk  Wed Oct  1 23:31:58 1997
Received: from embankment.algor.co.uk (root@embankment.algor.co.uk [193.117.190.2]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id XAA10537; Wed, 1 Oct 1997 23:31:55 +0200 (MET DST)
Received-Date: Wed, 1 Oct 1997 23:31:55 +0200 (MET DST)
Received: from gladsmuir.algor.co.uk (dom@gladsmuir.algor.co.uk [193.117.190.129])
	by embankment.algor.co.uk (8.8.7/8.8.5) with ESMTP id WAA17596;
	Wed, 1 Oct 1997 22:31:44 +0100 (BST)
Received: (from dom@localhost) by gladsmuir.algor.co.uk (8.7.3/8.7.3) id WAA00679; Wed, 1 Oct 1997 22:33:26 +0100 (BST)
Date: Wed, 1 Oct 1997 22:33:26 +0100 (BST)
From: Dom Sweetman <dom@algor.co.uk>
Message-Id: <199710012133.WAA00679@gladsmuir.algor.co.uk>
To: linux-mips@fnet.fr
Subject: Re: Linux/MIPS for DECstations...
In-Reply-To: <XFMail.971001200907.harald.koerfgen@netcologne.de>
References: <199709302112.OAA04252@dull.cobaltmicro.com>
        <XFMail.971001200907.harald.koerfgen@netcologne.de>
Content-Length: 1705
Lines: 44


Harald Koerfgen (harald.koerfgen@netcologne.de) writes:

> After carefully re-resing the IDT Manual ant glance at the SGI
> Manual, it is my understanding, that indeed there is a difference in
> the exception mechanism between the R3000 and the R4000.

Yes, there are some very big differences concealed behind what look
like almost the same registers...

> R4000: *All* TLB misses cause a TLB refill exception. If a TLB miss
> happens in the exception routine itself...

Strictly speaking, that's "if a TLB miss happens with the status
register exception level bit set" - SR(EXL) for short.  But you're
right, the only time that will actually happen will be the TLB miss
incurred by the table look-up of the fast TLB miss.

> ..., a TLBL or TLBS exception is caused. This is handled
> bye the general exception handler.

> R3000: *Only* references to KSEG0 (0x00000000- 0x7fffffff) may cause
> a TLB exception.  TLB misses with references to KSEG2 (0xc0000000 -
> 0xffffffff !!!) cause a TLBL or TLBS exception, which is handled by
> the general exception handler.

That's right; so unix application TLB misses are handled fast, but any
kernel-translation misses get a bigger penalty.  It's up to the OS
writer to minimise the latter.

Both mechanisms support the mechanism built around the "Context"
register which helps out a translation scheme using a main page table
which is apparently "flat" but is actually located in kernel virtual
memory.

But yes, Harald, that sounds right.

PS: I wrote most of the IDT manual, so I hope it helped...  My
    forthcoming book has the R4x00 stuff in too, and should be out
    next year, pub Morgan Kaufmann.

Dominic Sweetman
Algorithmics Ltd
dom@algor.co.uk

From dom@algor.co.uk  Wed Oct  1 23:39:54 1997
Received: from embankment.algor.co.uk (root@embankment.algor.co.uk [193.117.190.2]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id XAA10586; Wed, 1 Oct 1997 23:39:52 +0200 (MET DST)
Received-Date: Wed, 1 Oct 1997 23:39:52 +0200 (MET DST)
Received: from gladsmuir.algor.co.uk (dom@gladsmuir.algor.co.uk [193.117.190.129])
	by embankment.algor.co.uk (8.8.7/8.8.5) with ESMTP id WAA17616
	for <linux-mips@fnet.fr>; Wed, 1 Oct 1997 22:39:47 +0100 (BST)
Received: (from dom@localhost) by gladsmuir.algor.co.uk (8.7.3/8.7.3) id WAA00685; Wed, 1 Oct 1997 22:41:29 +0100 (BST)
Date: Wed, 1 Oct 1997 22:41:29 +0100 (BST)
From: Dom Sweetman <dom@algor.co.uk>
Message-Id: <199710012141.WAA00685@gladsmuir.algor.co.uk>
To: linux-mips@fnet.fr
Subject: Re: Linux/MIPS for DECstations...
In-Reply-To: <XFMail.971001200907.harald.koerfgen@netcologne.de>
References: <199709302112.OAA04252@dull.cobaltmicro.com>
        <XFMail.971001200907.harald.koerfgen@netcologne.de>
Content-Length: 742
Lines: 20


Perhaps I should have added: when rewriting R3K exception handlers,
you need to be aware that the way you get into the general exception
entry point is very different.

When the R4K CPUs get a TLB miss during the fast TLB miss exception
routine, they leave the original user exception restart location in
EPC.  When you get to the general exception handler, it's as if
the fast TLB exception never happened.

The R3K doesn't do that; it nests the second-level miss exception and
returns back through the fast handler.  The MIPS OS' handlers use one
of the reserved-for-exception registers (k0, k1) to save the original
EPC value.  

That's why MIPS reserved two registers for exceptions...

Dominic Sweetman
Algorithmics Ltd
dom@algor.co.uk

From imp@village.org  Wed Oct  1 23:42:28 1997
Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id XAA10637; Wed, 1 Oct 1997 23:42:26 +0200 (MET DST)
Received-Date: Wed, 1 Oct 1997 23:42:26 +0200 (MET DST)
Received: from harmony [10.0.0.6] 
	by rover.village.org with esmtp (Exim 1.71 #1)
	id 0xGWXF-0007R3-00; Wed, 1 Oct 1997 15:42:21 -0600
Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id PAA26574 for <linux-mips@fnet.fr>; Wed, 1 Oct 1997 15:43:12 -0600 (MDT)
Message-Id: <199710012143.PAA26574@harmony.village.org>
To: linux-mips@fnet.fr
Subject: Re: Linux/MIPS for DECstations... 
In-reply-to: Your message of "Wed, 01 Oct 1997 22:33:26 BST."
		<199710012133.WAA00679@gladsmuir.algor.co.uk> 
References: <199710012133.WAA00679@gladsmuir.algor.co.uk>  <199709302112.OAA04252@dull.cobaltmicro.com> <XFMail.971001200907.harald.koerfgen@netcologne.de> 
Date: Wed, 01 Oct 1997 15:43:11 -0600
From: Warner Losh <imp@village.org>
Content-Length: 371
Lines: 9

In message <199710012133.WAA00679@gladsmuir.algor.co.uk> Dom Sweetman writes:
: PS: I wrote most of the IDT manual, so I hope it helped...  My
:     forthcoming book has the R4x00 stuff in too, and should be out
:     next year, pub Morgan Kaufmann.

Can you post something when this is available?  I know that it sounds
like something that I'd be interested in.

Warner

From ralf@mail2.cobaltmicro.com  Thu Oct  2 00:37:21 1997
Received: from dns.cobaltmicro.com ([209.19.61.1]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id AAA12456; Thu, 2 Oct 1997 00:37:20 +0200 (MET DST)
Received-Date: Thu, 2 Oct 1997 00:37:20 +0200 (MET DST)
Received: from dull.cobaltmicro.com (dull.cobaltmicro.com [209.19.61.35])
	by dns.cobaltmicro.com (8.8.5/8.8.5) with ESMTP id PAA27332
	for <linux-mips@fnet.fr>; Wed, 1 Oct 1997 15:37:21 -0700
From: Ralf Baechle <ralf@cobaltmicro.com>
Received: (from ralf@localhost)
	by dull.cobaltmicro.com (8.8.5/8.8.5) id PAA16831
	for linux-mips@fnet.fr; Wed, 1 Oct 1997 15:35:09 -0700
Message-Id: <199710012235.PAA16831@dull.cobaltmicro.com>
Subject: Re: Linux/MIPS for DECstations...
To: linux-mips@fnet.fr
Date: Wed, 1 Oct 1997 15:35:08 -0700 (PDT)
In-Reply-To: <XFMail.971001200907.harald.koerfgen@netcologne.de> from "Harald Koerfgen" at Oct 1, 97 07:53:34 pm
Content-Type: text
Content-Length: 2855
Lines: 73

> >Nevertheless, for your case the superfluous srl instruction shouldn't make
> >a difference.  Note that the R3000 exception mechanism is a bit different
> >from the R4000, which means I'll have to read a bit ...
> 
> Me too...
> 
> Ok, all documentation about MIPS Processors are the "IDT R30xx Family Software
> Reference Manual" from IDT and the "MIPS R4000 Microprocessor User's Manual" 
> from SGI.
> 
> [hours later]
> 
> After carefully re-resing the IDT Manual ant glance at the SGI Manual, it is my 
> understanding, that indeed there is a difference in the exception mechanism
> between the R3000 and the R4000.
> 
> R4000:
> *All* TLB misses cause a TLB refill exception. If a TLB miss happens in the
> exception routine itself, a TLBL or TLBS exception is caused. This is handled
> bye the general exception handler.
> 
> R3000:
> *Only* references to KSEG0 (0x00000000- 0x7fffffff) may cause a TLB exception.
> TLB misses with references to KSEG2 (0xc0000000 - 0xffffffff !!!) cause a TLBL 
> or TLBS exception, which is handled by the general exception handler.

So what you have to do in software is pretty easy.  To make things even
easier take a look at what the code in r4k_misc.S does when
NOTLB_OPTIMIZE is optimized.  That's the minimum it has to do; the rest
of the assembler code tries to handle some simple cases like dirtying
pages without calling the generic memory managment but that is just for
performance reasons.  Plus, on the R3000 you additionally have to examine
c0_badvaddr if it contains a KSEG2 address:

NESTED(r2k_handle_tlbl, PT_SIZE, sp)
		mfc0	k0,CP0_BADVADDR
		 nop
		bltz	k0, go_utlb_tlbl
		 nop

utlb_tlbl:	/* Do what the your old tlbl handler does */
		...
		END(r2k_handle_tlbl, PT_SIZE, sp)
go_utlb_tlbl:	j	utlb_handler	/* The thing at KSEG0 or so */

If yes, just jump to the TLB exception handler.  Same thing for the tlbs
exception.

> Just to make shure, that I understand this right: can anybody on the list
> confirm this?

Yes, that's about right.  At least it's what I remember ...

> This could explain, why the kernel seems to die in the second level eception
> handler. It's simply a reference to the freshly vmalloced hash table.

You may want to modify the debugging helpers in arch/mips/lib/tlbdump.c
for the R3000, they'll probably really solve you alot of headaches.

> Paul wrote:
> 
> >...I should probably say that I think this code is of dubious
> >parentage!  It would probably be best for you to look closely at the
> >MMU code.  I was only just getting my head around the R3K MMU when I
> >ran out of time to keep working on it, so I'd suggest you might even
> >want to throw it away and write it again!
> 
> That would be the best. Ok, if nobody else wants to do it, I'll start rewriting
> the R3000 TLB stuff.

When you're done with that you can call yourself MIPS-Man :-)

  Ralf

From ralf@dns.cobaltmicro.com  Wed Oct  1 03:02:48 1997
Received: from dns.cobaltmicro.com ([209.19.61.1]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id DAA03875; Wed, 1 Oct 1997 03:02:47 +0200 (MET DST)
Received-Date: Wed, 1 Oct 1997 03:02:47 +0200 (MET DST)
Received: (from ralf@localhost)
	by dns.cobaltmicro.com (8.8.5/8.8.5) id SAA22736;
	Tue, 30 Sep 1997 18:02:51 -0700
From: Ralf Baechle <ralf@cobaltmicro.com>
Message-Id: <199710010102.SAA22736@dns.cobaltmicro.com>
Subject: For stability freaks ...
To: linux-mips@fnet.fr, linux@engr.sgi.com
Date: Tue, 30 Sep 1997 18:02:51 -3100 (PDT)
Content-Type: text
Content-Length: 578
Lines: 17

Ok, I said I'd touch 2.0.x for MIPS again when hell freezes.  It was
damn cold weather the last days and hell has froozen ...

[root@(none) /]# uname -a
Linux (none) 2.0.30 #389 Tue Sep 30 17:47:39 PDT 1997 mips unknown
[root@(none) /]# cat /proc/cpuinfo
cpu                     : MIPS
cpu model               : Nevada V1.0
system type             : Cray YMP  [just kidding ...]
BogoMIPS                : 131.89
byteorder               : little endian
unaligned accesses      : 0
wait instruction        : yes
microsecond timers      : yes
extra interrupt vector  : yes

  Ralf

From paul@suede.sw.oz.au  Thu Oct  2 03:52:48 1997
Received: from staff.cs.su.OZ.AU (staff.cs.su.OZ.AU [129.78.8.1]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id DAA17707; Thu, 2 Oct 1997 03:52:39 +0200 (MET DST)
Received-Date: Thu, 2 Oct 1997 03:52:39 +0200 (MET DST)
Received: from suede.sw.oz.au by swallow.sw.oz.au with ESMTP
	id BAA02408; Thu, 2 Oct 1997 01:51:52 GMT (8.6.10/Unixware)
	(from paul@suede.sw.oz.au for <linux-mips@fnet.fr>)
Received: by suede.sw.oz.au
	id BAA25845; Thu, 2 Oct 1997 01:51:51 GMT (SMI-8.6/1.34)
	(from paul for linux-mips@fnet.fr)
From: paul@softway.com.au (Paul Antoine)
Message-Id: <199710020151.BAA25845@suede.sw.oz.au>
Subject: Ralf - email problems!
To: linux-mips@fnet.fr (Linux MIPS mailing list)
Date: Thu, 2 Oct 1997 11:51:50 +1000 (EST)
Organization: Softway Pty Ltd
X-Face: 
	U)Kb/c%d9`JI>Y>s'evmMaR`z*WE$<,["^2)I8o?jkx/d^=dMa$GD(s6[p|npE}r0?)qQ7H
	*3S2vbK66POj?=%pCn?Bp}D/3A{`-.v0=%L9emS+|Pc91$EP0-;i\ON*p;Mwp$tt3wO~g1Z
	W.mIz'n~$U&uIM9ix=\1=~""=W?t$3b)>`foC8+3g$m2l;^D$?i}WI(Uxc@THJ9OBbk3g6
X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*]
Content-Type: text
Content-Length: 894
Lines: 24

Ralf,

Just tried to send you email at cobaltmicro, and had the following
error message in the returned transcript:

	<my email snipped>
	> .
	< 500 Syntax error, <cr><lf> not used as end of line
	The remote host returned the following fatal error:
	  >>> 500 Syntax error, <cr><lf> not used as end of line

...so whilst I could connect to your site to deliver my email reply,
it complained of the way the smtpd closed the session!

Regards,
Paul
_______________________________________________________________________________
Paul M. Antoine, 				        Net: paul@sw.oz.au
Softway Pty Ltd						WWW: www.softway.com.au
PO Box 305, Strawberry Hills, NSW 2012, Australia       Tel: +61 2 9698 2322
Level 2, 79 Myrtle St, Chippendale, NSW 2008, Australia Fax: +61 2 9699 9174

"It is the lack of acceptance of diversity which threatens to 
 destroy society, NOT the free expression of it." - Me.

From ralf@mail2.cobaltmicro.com  Thu Oct  2 04:18:56 1997
Received: from dns.cobaltmicro.com ([209.19.61.1]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id EAA18235; Thu, 2 Oct 1997 04:18:55 +0200 (MET DST)
Received-Date: Thu, 2 Oct 1997 04:18:55 +0200 (MET DST)
Received: from dull.cobaltmicro.com (dull.cobaltmicro.com [209.19.61.35])
	by dns.cobaltmicro.com (8.8.5/8.8.5) with ESMTP id TAA28169
	for <linux-mips@fnet.fr>; Wed, 1 Oct 1997 19:18:57 -0700
From: Ralf Baechle <ralf@cobaltmicro.com>
Received: (from ralf@localhost)
	by dull.cobaltmicro.com (8.8.5/8.8.5) id TAA17960
	for linux-mips@fnet.fr; Wed, 1 Oct 1997 19:16:44 -0700
Message-Id: <199710020216.TAA17960@dull.cobaltmicro.com>
Subject: Re: Ralf - email problems!
To: linux-mips@fnet.fr
Date: Wed, 1 Oct 1997 19:16:43 -0700 (PDT)
In-Reply-To: <199710020151.BAA25845@suede.sw.oz.au> from "Paul Antoine" at Oct 2, 97 11:51:50 am
Content-Type: text
Content-Length: 736
Lines: 22

Paul,

> Just tried to send you email at cobaltmicro, and had the following
> error message in the returned transcript:
> 
> 	<my email snipped>
> 	> .
> 	< 500 Syntax error, <cr><lf> not used as end of line
> 	The remote host returned the following fatal error:
> 	  >>> 500 Syntax error, <cr><lf> not used as end of line
> 
> ...so whilst I could connect to your site to deliver my email reply,
> it complained of the way the smtpd closed the session!

Welcome to the pleasures of Eudora running on a Mac.  Use ralf@uni-koblenz.de
or ralf@gnu.ai.mit.edu.  Or ralf@mail2.cobaltmicro.com which is on a
Linux / sendmail system and therefore works.

Oh, and I did receive a mail '<199710020144.BAA25681@suede.sw.oz.au>'
from you.

  Ralf

From hkoerfg1@ford.com  Thu Oct  2 12:23:48 1997
Received: from mailfw1.ford.com (mailfw1.ford.com [136.1.1.26]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id MAA22190; Thu, 2 Oct 1997 12:22:58 +0200 (MET DST)
Received-Date: Thu, 2 Oct 1997 12:22:58 +0200 (MET DST)
Received: by mailfw1.ford.com id AA15811
  (InterLock SMTP Gateway 3.0 for linux-mips@fnet.fr);
  Thu, 2 Oct 1997 06:22:34 -0400
Message-Id: <199710021022.AA15811@mailfw1.ford.com>
Received: by mailfw1.ford.com (Internal Mail Agent-1);
  Thu, 2 Oct 1997 06:22:34 -0400
Comments: Authenticated sender is <hkoerfg1@dttws020.merkenich.ford.com>
From: "Harald Koerfgen" <hkoerfg1@ford.com>
Organization: Ford Motor Company
To: linux-mips@fnet.fr
Date: Thu, 2 Oct 1997 12:20:26 +0100
Subject: Re: Linux/MIPS for DECstations...
Reply-To: hkoerfg1@ford.com
Priority: normal
In-Reply-To: <199710012235.PAA16831@dull.cobaltmicro.com>
References: <XFMail.971001200907.harald.koerfgen@netcologne.de> from "Harald Koerfgen" at Oct 1, 97 07:53:34 pm
X-Mailer: Pegasus Mail for Windows (v2.53/R1)
Content-Length: 228
Lines: 11

Ralf wrote:

> > Ok, if nobody else wants to do it, I'll start rewriting
> > the R3000 TLB stuff.
> 
> When you're done with that you can call yourself MIPS-Man :-)

Well, if that isn't a reward ... :-)

I'll be back ...
Harald

From hkoerfg1@ford.com  Thu Oct  2 13:07:42 1997
Received: from mailfw1.ford.com (mailfw1.ford.com [136.1.1.26]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id NAA22540; Thu, 2 Oct 1997 13:07:39 +0200 (MET DST)
Received-Date: Thu, 2 Oct 1997 13:07:39 +0200 (MET DST)
Received: by mailfw1.ford.com id AA17996
  (InterLock SMTP Gateway 3.0 for linux-mips@fnet.fr);
  Thu, 2 Oct 1997 07:07:27 -0400
Message-Id: <199710021107.AA17996@mailfw1.ford.com>
Received: by mailfw1.ford.com (Internal Mail Agent-1);
  Thu, 2 Oct 1997 07:07:27 -0400
Comments: Authenticated sender is <hkoerfg1@dttws020.merkenich.ford.com>
From: "Harald Koerfgen" <hkoerfg1@ford.com>
Organization: Ford Motor Company
To: linux-mips@fnet.fr
Date: Thu, 2 Oct 1997 13:05:19 +0100
Subject: Re: Linux/MIPS for DECstations...
Reply-To: hkoerfg1@ford.com
Priority: normal
In-Reply-To: <199710012133.WAA00679@gladsmuir.algor.co.uk>
References: <XFMail.971001200907.harald.koerfgen@netcologne.de>
X-Mailer: Pegasus Mail for Windows (v2.53/R1)
Content-Length: 317
Lines: 11

Dominic wrote:

> PS: I wrote most of the IDT manual, so I hope it helped...  My
>     forthcoming book has the R4x00 stuff in too, and should be out
>     next year, pub Morgan Kaufmann.

Yes, Dominic, it helped a lot. I find this manual very readable, even for a 
MIPS novice. Thank you very much.

regards,
Harald

From Henrik.Scheel@geoteknisk.dk  Thu Oct  2 15:12:37 1997
Received: from dgil.com (gateway.geoteknisk.dk [130.226.6.2]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id PAA24443; Thu, 2 Oct 1997 15:11:54 +0200 (MET DST)
Received-Date: Thu, 2 Oct 1997 15:11:54 +0200 (MET DST)
Received: from HNSPC (hnspc.dgil.com [192.192.12.187])
	by dgil.com (8.8.5/8.8.5) with SMTP id PAA26976;
	Thu, 2 Oct 1997 15:08:40 +0200
Message-ID: <34339DFC.15EF@geoteknisk.dk>
Date: Thu, 02 Oct 1997 15:13:32 +0200
From: "Henrik R. Scheel" <scheelh@kfumscout.dk>
Reply-To: scheelh@kfumscout.dk
Organization: KFUM spejderne
X-Mailer: Mozilla 3.01 (WinNT; I)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: old SGI workstations
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 1265
Lines: 35

Hello,
  I would like to start by telling you how much I admire your ongoing
efforts to port Linux software. 

I have a few old Personal Iris workstations that I would like to use for
running Linux. I think they have a MIPS R3000 processor, 8 or 16 MB ram
and 250 MB harddisk. So I suppose they will perform much like a Intel
486 or a slow pentium, only with better graphics, if Linux will run on
them. 

They will make great X-terminals, though, with those big screens.

I would like to tell you that I have the time and ability do a lot of
kernel-hacking on this port, but I can't. I simply cannot promise to put
any time in it. (I might not have the ability (yet), either   :-)

On the other hand, if your best judgement says that only minor changes
to an existing port will probably work, I will give it a try.

I found out as much as:
Linux is running on R300 now (?)
but not on SGI Personal Iris (?)
on SGI Indy (!)
which has a similar hardware design (memory, bus, video, network) (?)

Well I haven't found out a lot, yet.
Any pointers will be appreciated.

Best Regards,
Henrik
-- 
Henrik R. Scheel, Danish Geotechnical institute,
Maglebjergvej 1, BOX 119, 2800 Lyngby, Danmark
tel: +45 45884444, fax: +45 45881240,
reply email: Henrik.Scheel@geoteknisk.dk

From ralf@informatik.uni-koblenz.de  Fri Oct  3 01:14:22 1997
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id BAA03756; Fri, 3 Oct 1997 01:14:20 +0200 (MET DST)
Received-Date: Fri, 3 Oct 1997 01:14:20 +0200 (MET DST)
Received: from erbse (ralf@erbse.uni-koblenz.de [141.26.5.44]) by informatik.uni-koblenz.de (8.8.7/8.6.9) with SMTP id BAA04831; Fri, 3 Oct 1997 01:01:08 +0200 (MEST)
From: Ralf Baechle <ralf@informatik.uni-koblenz.de>
Message-Id: <199710022301.BAA04831@informatik.uni-koblenz.de>
Received: by erbse (SMI-8.6/KO-2.0)
	id BAA05365; Fri, 3 Oct 1997 01:01:06 +0200
Subject: Guess it's getting stable ...
To: linux@engr.sgi.com, linux-mips@fnet.fr
Date: Fri, 3 Oct 1997 01:01:05 +0200 (MET DST)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Length: 524
Lines: 12

That's the best scene from the movie I'm just enjoying:

  3:44pm  up  1:02,  2 users,  load average: 137.09, 95.96, 57.83
276 processes: 188 sleeping, 86 running, 2 zombie, 0 stopped
CPU states: 52.9% user, 35.3% system, 66.5% nice, 18.2% idle
Mem:   63636K av,  62388K used,   1248K free,  72900K shrd,    440K buff
Swap: 130748K av,  95288K used,  35460K free                  4412K cached

That's compiling two kernels, glibc, gcc, binutils and CVS with make -j.
I think I forgot to run a couple of crashmes ...

  Ralf

From ryan@ravage.labs.gmu.edu  Fri Oct  3 14:42:32 1997
Received: from ravage.labs.gmu.edu ([129.174.166.55]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id OAA09183; Fri, 3 Oct 1997 14:42:30 +0200 (MET DST)
Received-Date: Fri, 3 Oct 1997 14:42:30 +0200 (MET DST)
Received: from localhost (ryan@localhost)
	by ravage.labs.gmu.edu (8.8.5/8.8.5) with SMTP id IAA26666
	for <linux-mips@fnet.fr>; Fri, 3 Oct 1997 08:41:22 -0400
Date: Fri, 3 Oct 1997 08:41:22 -0400 (EDT)
From: Ryan <ryan@ravage.labs.gmu.edu>
To: linux-mips@fnet.fr
Subject: video cards
In-Reply-To: <199709210755.JAA10216@informatik.uni-koblenz.de>
Message-ID: <Pine.LNX.3.95.971003083531.26597A-100000@ravage.labs.gmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 876
Lines: 20


I don't know if anyone on this list knows anything about the GGI project,
but there are several areas where that project could be of interest to our
port.

For one thing, machines that require nonstandard video cards (like the
Magnums) and other machines that don't have x86 BIOS emulation (like the
PCI boards) should be able to use EISA or PCI graphics boards that
wouldn't otherwise work, due to the ability of GGI drivers to wake up
boards that haven't been awakened by a machine's firmware.  This also
allows multiheaded machines, since most modern video cards have the
ability to allow MMIO modes.  Right now, for example, it is possible on
the 386 platform to have as many S3 Trio64V+ and/or 968's, 964's, or 928's
in operation as you have availible slots.

Just thought I'd try to spark some interest in the project within this
group.

Is mise le meas,
Ryan Rafferty

From r.martins@distrim.pt  Fri Oct  3 18:30:19 1997
Received: from netland.netlandia.pt (root@netland.netlandia.pt [194.79.73.66]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id SAA10654; Fri, 3 Oct 1997 18:30:09 +0200 (MET DST)
Received-Date: Fri, 3 Oct 1997 18:30:09 +0200 (MET DST)
Received: from distrim (root@[194.79.73.126] (may be forged)) by netland.netlandia.pt (8.8.6/8.7.5) with SMTP id RAA23045 for <@netland.netlandia.pt:linux-mips@fnet.fr>; Fri, 3 Oct 1997 17:23:16 GMT
Received: from distrim (distrim [194.79.81.193]) by distrim (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id RAA07112 for <linux-mips@fnet.fr>; Fri, 3 Oct 1997 17:30:36 +0100
Sender: ricardo@distrim
Message-ID: <34351DAB.794B@distrim.pt>
Date: Fri, 03 Oct 1997 17:30:35 +0100
From: Ricardo Martins <r.martins@distrim.pt>
Organization: Distrim, Lda.
X-Mailer: Mozilla 3.01SC-SGI (X11; I; IRIX 6.2 IP22)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: mips Box
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 827
Lines: 16

Hello,
I saw wour page about Linux for mips processors:
http://www.fnet.fr/linux-mips/s: 
And i would like to now i there is a port to SGI Indigo or indy R3000 to
R5000 whith graphics XGE or XZ.
I work with both machines and have chances to test software.
I would like to now also if there is any IRIX emulator do Linux runing
on Intel x86.
-- 
 __________________________________________________________________
|\o------------- Powered by IRIX on SGI Indy at work --------------\
| | Ricardo Martins - r.martins@distrim.pt - webmaster@distrim.pt  |
| | Distrim, Lda    - Cad/Cam/Cae  -  http://www.distrim.pt        |
| | Marinha Grande  - tel: +351.44.5704000                         |
| | Portugal        - Fax: +351.44.5703000                         |
 \o------------ Powered by Linux on Pc 486Dx4 at home -------------o

From miguel@athena.nuclecu.unam.mx  Fri Oct  3 19:06:42 1997
Received: from athena.nuclecu.unam.mx (athena.nuclecu.unam.mx [132.248.29.9]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id TAA11286; Fri, 3 Oct 1997 19:06:37 +0200 (MET DST)
Received-Date: Fri, 3 Oct 1997 19:06:37 +0200 (MET DST)
Received: (from miguel@localhost)
	by athena.nuclecu.unam.mx (8.8.5/8.8.5) id MAA15049;
	Fri, 3 Oct 1997 12:01:54 -0500
Date: Fri, 3 Oct 1997 12:01:54 -0500
Message-Id: <199710031701.MAA15049@athena.nuclecu.unam.mx>
From: Miguel de Icaza <miguel@nuclecu.unam.mx>
To: linux-mips@fnet.fr
In-reply-to: <34351DAB.794B@distrim.pt> (message from Ricardo Martins on Fri,
	03 Oct 1997 17:30:35 +0100)
Subject: Re: mips Box
X-Windows: Complex nonsolutions to simple nonproblems.
Content-Length: 641
Lines: 19


> And i would like to now i there is a port to SGI Indigo or indy R3000 to
> R5000 whith graphics XGE or XZ.

Linux is working just fine on the Indy with R5000 and some R4xxx
processor, I can't remember which one Ralf had.  Check the web page at
http://www.linux.sgi.com for more information on Linux on the Indy.

> I work with both machines and have chances to test software.

We need hacking hands right now.

> I would like to now also if there is any IRIX emulator do Linux runing
> on Intel x86.

IRIX binaries can be run on Linux/MIPS.   I do not know of any effort
to write an emulator to run IRIX binaries on Linux/Intel.

Miguel.

From dam@njcc.com  Fri Oct  3 20:19:15 1997
Received: from vader.alk.com (root@[205.246.138.5]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id UAA12102; Fri, 3 Oct 1997 20:19:13 +0200 (MET DST)
Received-Date: Fri, 3 Oct 1997 20:19:13 +0200 (MET DST)
Sender: dam@vader.alk.com
Message-ID: <343537FF.A16B2740@njcc.com>
Date: Fri, 03 Oct 1997 14:22:55 -0400
From: "E.Damaskine" <dam@njcc.com>
Organization: ALK Associates Inc.
X-Mailer: Mozilla 4.03 [en] (X11; I; HP-UX B.10.20 9000/712)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 68
Lines: 4

--
E.Damaskine
dam@alk.com, dam@njcc.com
http://pluto.njcc.com/~dam

From jchrr@hrz.Uni-Bielefeld.DE  Mon Oct  6 18:10:08 1997
Received: from hermes.hrz.uni-bielefeld.de (hermes.hrz.uni-bielefeld.de [129.70.4.55]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id SAA03635; Mon, 6 Oct 1997 18:09:48 +0200 (MET DST)
Received-Date: Mon, 6 Oct 1997 18:09:48 +0200 (MET DST)
Received: from tina (tina.hrz.uni-bielefeld.de) by hermes.hrz.uni-bielefeld.de with SMTP
	(1.37.109.17/16.2) id AA082794283; Mon, 6 Oct 1997 18:11:23 +0200
Sender: jchrr@HRZ.Uni-Bielefeld.DE
Message-Id: <34390D0B.5CE0@hrz.uni-bielefeld.de>
Date: Mon, 06 Oct 1997 18:08:43 +0200
From: Jens Christian Restemeier <jchrr@hrz.Uni-Bielefeld.DE>
Organization: Universitaet Bielefeld
X-Mailer: Mozilla 3.01Gold (X11; I; HP-UX B.10.10 9000/735)
Mime-Version: 1.0
To: linux-mips@fnet.fr
Subject: MIPS Linux
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 579
Lines: 14

Hi !

I have two MIPS-boxes, that aren't supported by Linux/MIPS. It's a
Nintendo 64 and a Sony Playstation, having a R4300 and a R3000. I feel
like hacking them, so do you know if anybody else is working on this
topic ? RAM-extension may be a problem, but otherwise it'd be a cool
project.
				Jens Ch. Restemeier
-- 
----
"Five to one against and falling ...  four to one against and falling
... three to one ... two ... one ... probability factor one to one ...
we have normality, I repeat we have normality. Anything you still can't
cope with is therefore your own problem."

From miguel@athena.nuclecu.unam.mx  Mon Oct  6 20:25:24 1997
Received: from athena.nuclecu.unam.mx (athena.nuclecu.unam.mx [132.248.29.9]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id UAA04670; Mon, 6 Oct 1997 20:25:04 +0200 (MET DST)
Received-Date: Mon, 6 Oct 1997 20:25:04 +0200 (MET DST)
Received: (from miguel@localhost)
	by athena.nuclecu.unam.mx (8.8.5/8.8.5) id NAA14821;
	Mon, 6 Oct 1997 13:19:46 -0500
Date: Mon, 6 Oct 1997 13:19:46 -0500
Message-Id: <199710061819.NAA14821@athena.nuclecu.unam.mx>
From: Miguel de Icaza <miguel@nuclecu.unam.mx>
To: linux-mips@fnet.fr
In-reply-to: <34390D0B.5CE0@hrz.uni-bielefeld.de> (message from Jens Christian
	Restemeier on Mon, 06 Oct 1997 18:08:43 +0200)
Subject: Re: MIPS Linux
X-Windows: A moment of convenience, a lifetime of regret.
Content-Length: 868
Lines: 23


Jens author of Gmix said:

> I have two MIPS-boxes, that aren't supported by Linux/MIPS. It's a
> Nintendo 64 and a Sony Playstation, having a R4300 and a R3000. I feel
> like hacking them, so do you know if anybody else is working on this
> topic ? RAM-extension may be a problem, but otherwise it'd be a cool
> project.

Todd Shrider showed interest in workin in this project
(tshrider@cs.indiana.edu). 

The main problem is that it will be difficult to get information on
the internals of the machine.  The R4300 should be pretty easy to
support with the current kernel.  The R3000 support is not yet quite
ready, so some hacking in this area will be required.

I have never used a nintendo 64, but I imagine that the only solution
may be to disassemble their rom and some games to figure out how to
access some of the machine precious resources.

Cheers,
Miguel.

From miguel@athena.nuclecu.unam.mx  Wed Oct  8 00:53:03 1997
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id AAA16686; Wed, 8 Oct 1997 00:53:03 +0200 (MET DST)
Received-Date: Wed, 8 Oct 1997 00:53:03 +0200 (MET DST)
Received: (from miguel@localhost)
	by athena.nuclecu.unam.mx (8.8.5/8.8.5) id RAA01259;
	Tue, 7 Oct 1997 17:41:38 -0500
Date: Tue, 7 Oct 1997 17:41:38 -0500
Message-Id: <199710072241.RAA01259@athena.nuclecu.unam.mx>
From: Miguel de Icaza <miguel@nuclecu.unam.mx>
To: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: More Linux/SGI status
Content-Length: 708
Lines: 26


Hello guys,

   Ralf's fixes to the dynamic linker fixed the Xt applications.  Now,
only the PAM remains to be fixed.

   So, where do we stand now?  So, the only bits missing now are:

	1. me finishing the support for the X server.  just a hack
	   here and there.

	1.b. Getting the other important bits of the RRM code in the
	   kernel. 

	2. me fixing the mouse.

	3. Would it be possible to negotiate with SGI management 
	   the posibility of shipping the IRIX runtime libraries and
	   the X server as found on IRIX with a Linux disrtibution?

	4. A nice, easy-to use install program.  Taking the existing
	   Red Hat/Mustand install program and port it should be
	   pretty easy. 

Cheers,
Miguel.

From ralf@mail2.cobaltmicro.com  Wed Oct  8 01:30:31 1997
Received: from dns.cobaltmicro.com ([209.19.61.1]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id BAA17404; Wed, 8 Oct 1997 01:30:30 +0200 (MET DST)
Received-Date: Wed, 8 Oct 1997 01:30:30 +0200 (MET DST)
Received: from dull.cobaltmicro.com (dull.cobaltmicro.com [209.19.61.35])
	by dns.cobaltmicro.com (8.8.5/8.8.5) with ESMTP id QAA24302;
	Tue, 7 Oct 1997 16:30:14 -0700
From: Ralf Baechle <ralf@cobaltmicro.com>
Received: (from ralf@localhost)
	by dull.cobaltmicro.com (8.8.5/8.8.5) id QAA17826;
	Tue, 7 Oct 1997 16:28:08 -0700
Message-Id: <199710072328.QAA17826@dull.cobaltmicro.com>
Subject: Re: More Linux/SGI status
To: miguel@nuclecu.unam.mx (Miguel de Icaza)
Date: Tue, 7 Oct 1997 16:28:07 -0700 (PDT)
Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
In-Reply-To: <199710072241.RAA01259@athena.nuclecu.unam.mx> from "Miguel de Icaza" at Oct 7, 97 05:41:38 pm
Content-Type: text
Content-Length: 1715
Lines: 44

Hi,

>    Ralf's fixes to the dynamic linker fixed the Xt applications.  Now,
> only the PAM remains to be fixed.

The PAM problem is also a dynamic linker problem.  It's (I hope) one the
last major showstopper class bugs that prevent just building a
Linux/MIPS distribution from 95% unchanged source packages - and
fullfilling all the promises to those loading hardware to me ...

Btw, I stopped the mega load test (Running many compilers and tools in
parallel) I posted recently after some more hours because the machine ran
out of swap, some processes died therefore and load < 100 isn't that
interesting ...

System call latencies were pretty lousy bad for MIPS kernel because
we were using a syscall handler written in C.  I rewrote the entire
thing in assembler and now we're as fast as a MMX Pentium accounting
for the different clock rates.  Pretty nice, because we actually have
to save/restore many more registers and deal with a more complex
system call convention.  Seven nops left to eleminate ...

>    So, where do we stand now?  So, the only bits missing now are:
> 
> 	1. me finishing the support for the X server.  just a hack
> 	   here and there.
> 
> 	1.b. Getting the other important bits of the RRM code in the
> 	   kernel. 
> 
> 	2. me fixing the mouse.
> 
> 	3. Would it be possible to negotiate with SGI management 
> 	   the posibility of shipping the IRIX runtime libraries and
> 	   the X server as found on IRIX with a Linux disrtibution?

Bad point in time, it has been pointed out to me that SGI's stock
was doing pretty bad ;-)

> 	4. A nice, easy-to use install program.  Taking the existing
> 	   Red Hat/Mustand install program and port it should be
> 	   pretty easy. 

  Ralf

From ariel@oz.engr.sgi.com  Wed Oct  8 02:00:15 1997
Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id CAA18044; Wed, 8 Oct 1997 02:00:13 +0200 (MET DST)
Received-Date: Wed, 8 Oct 1997 02:00:13 +0200 (MET DST)
Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by sgi.sgi.com (950413.SGI.8.6.12/970507) via ESMTP id QAA13911; Tue, 7 Oct 1997 16:57:03 -0700
	env-from (ariel@oz.engr.sgi.com)
Received: from oz.engr.sgi.com (oz.engr.sgi.com [150.166.61.27]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA25295; Tue, 7 Oct 1997 16:56:40 -0700
Received: (from ariel@localhost) by oz.engr.sgi.com (970903.SGI.8.8.7/960327.SGI.AUTOCF) id QAA23399; Tue, 7 Oct 1997 16:56:35 -0700 (PDT)
From: ariel@oz.engr.sgi.com (Ariel Faigon)
Message-Id: <199710072356.QAA23399@oz.engr.sgi.com>
Subject: Re: More Linux/SGI status
To: miguel@nuclecu.unam.mx (Miguel de Icaza)
Date: Tue, 7 Oct 1997 16:56:35 -0700 (PDT)
Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
In-Reply-To: <199710072241.RAA01259@athena.nuclecu.unam.mx> from "Miguel de Icaza" at Oct 7, 97 05:41:38 pm
Reply-To: ariel@cthulhu.engr.sgi.com (Ariel Faigon)
Organization: Silicon Graphics Inc.
X-Mailer: ELM [version 2.4 PL24 ME5a]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 578
Lines: 18

:
:
:	3. Would it be possible to negotiate with SGI management 
:	   the posibility of shipping the IRIX runtime libraries and
:	   the X server as found on IRIX with a Linux disrtibution?
:

My take on this is that since whoever bought that Indy
already paid for the OS including the X server and other
binaries there should be no reason why not to allow
them to run it on top of linux.

Putting it in a distribution that anyone can download
however is different and would require management approval
could someone on the list ask their directors about this?

-- 
Peace, Ariel

From wje@fir.engr.sgi.com  Wed Oct  8 04:08:17 1997
Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id EAA19199; Wed, 8 Oct 1997 04:08:15 +0200 (MET DST)
Received-Date: Wed, 8 Oct 1997 04:08:15 +0200 (MET DST)
Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by sgi.sgi.com (950413.SGI.8.6.12/970507) via ESMTP id RAA22721; Tue, 7 Oct 1997 17:30:43 -0700
	env-from (wje@fir.engr.sgi.com)
Received: from fir.engr.sgi.com (fir.engr.sgi.com [150.166.49.183]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA04168; Tue, 7 Oct 1997 17:30:42 -0700
Received: (from wje@localhost) by fir.engr.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) id RAA22931; Tue, 7 Oct 1997 17:30:41 -0700
Date: Tue, 7 Oct 1997 17:30:41 -0700
Message-Id: <199710080030.RAA22931@fir.engr.sgi.com>
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Miguel de Icaza <miguel@nuclecu.unam.mx>
Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Re: More Linux/SGI status
In-Reply-To: <199710072241.RAA01259@athena.nuclecu.unam.mx>
References: <199710072241.RAA01259@athena.nuclecu.unam.mx>
Content-Length: 1467
Lines: 26

Miguel de Icaza writes:
...
 > 	3. Would it be possible to negotiate with SGI management 
 > 	   the posibility of shipping the IRIX runtime libraries and
 > 	   the X server as found on IRIX with a Linux disrtibution?
...

      Perhaps Ariel can check on this, but I suspect that there are licensing
problems.  Each SGI system comes with a license to use one copy of the
software, where the fees which SGI must pay for each copy are bundled
in the cost of the system.  That is, if you have a system, the system 
includes the license.  The licenses involved include more than just
the basic UNIX and NFS licenses.  For example, the X server includes
optional Display Postscript support licensed from Adobe.  

      You could consider a scheme for automatically extracting the parts
you need from an IRIX distribution CD.  That is, the system normally
comes with the CD for the software (although that may be lost for an older
system), and the user has the right to use the CD on that system.
If the linux installation were willing to mount that CD and pull out
the components, the user model would not be too awkward (although obviously
not as nice as having one distribution).  If you were able to run the
IRIX inst on linux, you could extract it from the CD and ask it
to pull the files from the distribution.  (There is a miniroot EFS file
system image on the CD, and inst is on that image; the rest of the distribution
is in packed data files decoded by inst.)

From alan@lxorguk.ukuu.org.uk  Wed Oct  8 09:39:05 1997
Received: from snowcrash.cymru.net (snowcrash.cymru.net [163.164.160.3]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id JAA22245; Wed, 8 Oct 1997 09:39:01 +0200 (MET DST)
Received-Date: Wed, 8 Oct 1997 09:39:01 +0200 (MET DST)
Received: from lightning.swansea.linux.org.uk (centre.swanlink.ukuu.org.uk [137.44.10.205]) by snowcrash.cymru.net (8.8.5-q-beta3/8.7.1) with SMTP id IAA15255; Wed, 8 Oct 1997 08:35:12 +0100
Received: by lightning.swansea.linux.org.uk (Smail3.1.29.1 #2)
	id m0xIqbs-0005FiC; Wed, 8 Oct 97 08:32 BST
Message-Id: <m0xIqbs-0005FiC@lightning.swansea.linux.org.uk>
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
Subject: Re: More Linux/SGI status
To: miguel@nuclecu.unam.mx (Miguel de Icaza)
Date: Wed, 8 Oct 1997 08:32:43 +0100 (BST)
Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
In-Reply-To: <199710072241.RAA01259@athena.nuclecu.unam.mx> from "Miguel de Icaza" at Oct 7, 97 05:41:38 pm
Content-Type: text
Content-Length: 374
Lines: 11

> 	4. A nice, easy-to use install program.  Taking the existing
> 	   Red Hat/Mustand install program and port it should be
> 	   pretty easy. 

The big install problem is repartitioning an EFS system without damaging
the EFS. There seem to be tools to do it via tape from reading the CD's.

Once my SGI appears cranking out a distribution set is still my first goal


Alan

From alan@lxorguk.ukuu.org.uk  Wed Oct  8 09:43:29 1997
Received: from snowcrash.cymru.net (snowcrash.cymru.net [163.164.160.3]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id JAA22304; Wed, 8 Oct 1997 09:43:26 +0200 (MET DST)
Received-Date: Wed, 8 Oct 1997 09:43:26 +0200 (MET DST)
Received: from lightning.swansea.linux.org.uk (centre.swanlink.ukuu.org.uk [137.44.10.205]) by snowcrash.cymru.net (8.8.5-q-beta3/8.7.1) with SMTP id IAA15276; Wed, 8 Oct 1997 08:41:52 +0100
Received: by lightning.swansea.linux.org.uk (Smail3.1.29.1 #2)
	id m0xIqiF-0005FiC; Wed, 8 Oct 97 08:39 BST
Message-Id: <m0xIqiF-0005FiC@lightning.swansea.linux.org.uk>
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
Subject: Re: More Linux/SGI status
To: ariel@cthulhu.engr.sgi.com
Date: Wed, 8 Oct 1997 08:39:19 +0100 (BST)
Cc: miguel@nuclecu.unam.mx, linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
In-Reply-To: <199710072356.QAA23399@oz.engr.sgi.com> from "Ariel Faigon" at Oct 7, 97 04:56:35 pm
Content-Type: text
Content-Length: 503
Lines: 10

> My take on this is that since whoever bought that Indy
> already paid for the OS including the X server and other
> binaries there should be no reason why not to allow
> them to run it on top of linux.

Thats simple until someone builds a clone SGI box. RedHat rpms
actually have some provision for a tool called rhmask which 
requires you have some "original" to generate the new rpm. Anyway
we don't want to encourage folks not to make the Linux version
kick the backside of any SGI original item..

From wje@fir.engr.sgi.com  Wed Oct  8 19:49:22 1997
Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id TAA26666; Wed, 8 Oct 1997 19:49:18 +0200 (MET DST)
Received-Date: Wed, 8 Oct 1997 19:49:18 +0200 (MET DST)
Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by sgi.sgi.com (950413.SGI.8.6.12/970507) via ESMTP id KAA27386; Wed, 8 Oct 1997 10:47:29 -0700
	env-from (wje@fir.engr.sgi.com)
Received: from fir.engr.sgi.com (fir.engr.sgi.com [150.166.49.183]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA12327; Wed, 8 Oct 1997 10:46:30 -0700
Received: (from wje@localhost) by fir.engr.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) id KAA23629; Wed, 8 Oct 1997 10:46:29 -0700
Date: Wed, 8 Oct 1997 10:46:29 -0700
Message-Id: <199710081746.KAA23629@fir.engr.sgi.com>
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: alan@lxorguk.ukuu.org.uk (Alan Cox)
Cc: ariel@cthulhu.engr.sgi.com, miguel@nuclecu.unam.mx,
        linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Re: More Linux/SGI status
In-Reply-To: <m0xIqiF-0005FiC@lightning.swansea.linux.org.uk>
References: <199710072356.QAA23399@oz.engr.sgi.com>
	<m0xIqiF-0005FiC@lightning.swansea.linux.org.uk>
Content-Length: 1090
Lines: 21

Alan Cox writes:
 > > My take on this is that since whoever bought that Indy
 > > already paid for the OS including the X server and other
 > > binaries there should be no reason why not to allow
 > > them to run it on top of linux.
 > 
 > Thats simple until someone builds a clone SGI box. RedHat rpms
 > actually have some provision for a tool called rhmask which 
 > requires you have some "original" to generate the new rpm. Anyway
 > we don't want to encourage folks not to make the Linux version
 > kick the backside of any SGI original item..

      It makes no sense to clone an SGI box, since there is no
long-term standard hardware profile.  That is, the combination
of hardware and system software provides a consistent model, but
the hardware/software interface changes each generation, both
in graphics and in I/O.  For people building MIPS-based linux boxes,
starting with the XFree86 source base, and adding good OpenGL support,
is a better model than trying to use Xsgi.  Using Xsgi (and libGL.so)
is simply an expedient way to get graphics support for linux on an
SGI box.

From brandon_welsh@lmsmail.lms.com  Thu Oct  9 12:17:38 1997
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id MAA29115; Thu, 9 Oct 1997 12:17:36 +0200 (MET DST)
Received-Date: Thu, 9 Oct 1997 12:17:36 +0200 (MET DST)
Received: from lmsmail.lms.com by lms (SMI-8.6/SMI-SVR4)
	id NAA18934; Wed, 8 Oct 1997 13:29:43 -0600
Received: from ccMail by lmsmail.lms.com (SMTPLINK V2.11.01)
	id AA876342419; Wed, 08 Oct 97 13:24:21 MST
Date: Wed, 08 Oct 97 13:24:21 MST
From: "Brandon Welsh" <brandon_welsh@lmsmail.lms.com>
Message-Id: <9709088763.AA876342419@lmsmail.lms.com>
To: linux-mips@fnet.fr
Subject: Adding my system
Content-Length: 517
Lines: 17

Could you add my system to a future release of MILO.
Here's the information:

ARC Vendor ID:          [NeTPower]
ARC Product ID: [00a0040003a000b7]
ARC System ID:  [NeTPower-Falcon-UP]
ARC CPU ID:             [MIPS-R4400 @ 200 Mhz - Pr 4/6.0, Fp 5/0]
Processor Type:         [UNKNOWN I04 V6.0]
Primary ICache size:    [0x4000 bytes]
Primary ICache line size:       [0x0020 bytes]
Primary DCache size:    [0x4000 bytes]
Primary DCache line size:       [0x0010 bytes]
Secondary Cache size:   [unknown]

Thanks

Brandon

From ralf@mail2.cobaltmicro.com  Thu Oct  9 13:22:01 1997
Received: from dns.cobaltmicro.com ([209.19.61.1]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id NAA29877; Thu, 9 Oct 1997 13:21:49 +0200 (MET DST)
Received-Date: Thu, 9 Oct 1997 13:21:49 +0200 (MET DST)
Received: from dull.cobaltmicro.com (dull.cobaltmicro.com [209.19.61.35])
	by dns.cobaltmicro.com (8.8.5/8.8.5) with ESMTP id EAA07211;
	Thu, 9 Oct 1997 04:22:46 -0700
From: Ralf Baechle <ralf@cobaltmicro.com>
Received: (from ralf@localhost)
	by dull.cobaltmicro.com (8.8.5/8.8.5) id EAA07469;
	Thu, 9 Oct 1997 04:19:29 -0700
Message-Id: <199710091119.EAA07469@dull.cobaltmicro.com>
Subject: Re: Adding my system
To: linux-mips@fnet.fr, brandon_welsh@lmsmail.lms.com
Date: Thu, 9 Oct 1997 04:19:29 -0700 (PDT)
In-Reply-To: <9709088763.AA876342419@lmsmail.lms.com> from "Brandon Welsh" at Oct 8, 97 01:24:21 pm
Content-Type: text
Content-Length: 671
Lines: 19

> 
> Could you add my system to a future release of MILO.
> Here's the information:
> 
> ARC Vendor ID:          [NeTPower]
> ARC Product ID: [00a0040003a000b7]
> ARC System ID:  [NeTPower-Falcon-UP]
> ARC CPU ID:             [MIPS-R4400 @ 200 Mhz - Pr 4/6.0, Fp 5/0]
> Processor Type:         [UNKNOWN I04 V6.0]
> Primary ICache size:    [0x4000 bytes]
> Primary ICache line size:       [0x0020 bytes]
> Primary DCache size:    [0x4000 bytes]
> Primary DCache line size:       [0x0010 bytes]
> Secondary Cache size:   [unknown]

Just adding a system isn't enough, the kernel would need to be ported
also and so far nobody had done more than looking a bit at it.

  Ralf

From ralf@mail2.cobaltmicro.com  Wed Oct 15 01:25:00 1997
Received: from dns.cobaltmicro.com ([209.19.61.1]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id BAA16278; Wed, 15 Oct 1997 01:24:59 +0200 (MET DST)
Received-Date: Wed, 15 Oct 1997 01:24:59 +0200 (MET DST)
Received: from dull.cobaltmicro.com (dull.cobaltmicro.com [209.19.61.35])
	by dns.cobaltmicro.com (8.8.5/8.8.5) with ESMTP id QAA06487;
	Tue, 14 Oct 1997 16:25:55 -0700
From: Ralf Baechle <ralf@cobaltmicro.com>
Received: (from ralf@localhost)
	by dull.cobaltmicro.com (8.8.5/8.8.5) id QAA32612;
	Tue, 14 Oct 1997 16:22:28 -0700
Message-Id: <199710142322.QAA32612@dull.cobaltmicro.com>
Subject: Ancient files
Date: Tue, 14 Oct 1997 16:22:28 -0700 (PDT)
Content-Type: text
Content-Length: 664
Lines: 17

Hi all,

from a time long ago many systems probably still have the directory
/usr/include/bsd/ existing on their disk.  I guess most people got
them as a part of the root-0.01.tar.gz package.  That directory contains
a include files that originate from Linux libc which we're not using.
This files are not usefull for anything and may cause problems building
certain software, especially RedHat RPM packages from the tbird/mustang
releases that still pass the option -I/usr/include/bsd to the compiler.
The bug fix is simple:

  rm -rf /usr/include/bsd

You have to remove these packages manually; upgrading the installed
RPMs will not remove these files.

  Ralf

From ralf@informatik.uni-koblenz.de  Wed Oct 15 01:58:28 1997
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id BAA16567; Wed, 15 Oct 1997 01:58:27 +0200 (MET DST)
Received-Date: Wed, 15 Oct 1997 01:58:27 +0200 (MET DST)
Received: from erbse (ralf@erbse.uni-koblenz.de [141.26.5.44]) by informatik.uni-koblenz.de (8.8.7/8.6.9) with SMTP id BAA08226; Wed, 15 Oct 1997 01:58:21 +0200 (MEST)
From: Ralf Baechle <ralf@informatik.uni-koblenz.de>
Message-Id: <199710142358.BAA08226@informatik.uni-koblenz.de>
Received: by erbse (SMI-8.6/KO-2.0)
	id BAA25872; Wed, 15 Oct 1997 01:58:19 +0200
Subject: static rpm bug, dynamic linker
To: linux@engr.sgi.com, linux-mips@fnet.fr
Date: Wed, 15 Oct 1997 01:58:18 +0200 (MET DST)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Length: 647
Lines: 15

Hi all,

I spent a lot of time on fixing the dynamic linker.  The bugs Miguel
found by building native X libraries are fixed by now.  The only one
that still is still giving me a miracle to solve is the fact that
certain statically linked executables, most prominently rpm, are
failing.

I'm about to fix that one also and that long want to remind people that
static linking is a dead concept anyway.  rpm for example will load a
dynamic libc when using the nss services, so all you get is bloat while
the knowledge about the kernel interfaces embedded into the statically
linked libc makes it very difficult to improve system interfaces.

  Ralf

From ralf@tbird.cobaltmicro.com  Thu Oct 16 06:54:11 1997
Received: from tbird.cobaltmicro.com ([209.19.61.36]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id GAA03098; Thu, 16 Oct 1997 06:54:09 +0200 (MET DST)
Received-Date: Thu, 16 Oct 1997 06:54:09 +0200 (MET DST)
Received: (from ralf@localhost)
	by tbird.cobaltmicro.com (8.8.5/8.8.5) id VAA13781;
	Wed, 15 Oct 1997 21:48:27 -0700
Message-ID: <19971015214825.01081@tbird.cobaltmicro.com>
Date: Wed, 15 Oct 1997 21:48:25 -0700
From: Ralf Baechle <ralf@cobaltmicro.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Miguel de Icaza <miguel@nuclecu.unam.mx>, linux@cthulhu.engr.sgi.com,
        linux-mips@fnet.fr
Subject: Re: More Linux/SGI status
References: <199710072241.RAA01259@athena.nuclecu.unam.mx> <m0xIqbs-0005FiC@lightning.swansea.linux.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81e
In-Reply-To: <m0xIqbs-0005FiC@lightning.swansea.linux.org.uk>; from Alan Cox on Wed, Oct 08, 1997 at 08:32:43AM +0100
Content-Length: 6515
Lines: 107

On Wed, Oct 08, 1997 at 08:32:43AM +0100, Alan Cox wrote:
> > 	4. A nice, easy-to use install program.  Taking the existing
> > 	   Red Hat/Mustand install program and port it should be
> > 	   pretty easy. 
> 
> The big install problem is repartitioning an EFS system without damaging
> the EFS. There seem to be tools to do it via tape from reading the CD's.
> 
> Once my SGI appears cranking out a distribution set is still my first goal

I asked Ariel, your box is on it's way.  I hope the transport guys
hurry as I'm getting pretty close to a useable distribution.  Appended
is a list of the RPMs which I'm currently using.  They're mostly from
the RedHat 4.9 aka Mustang distribution.  There are just a few things
left to fix to build the entire distribution:

 - rpm just returns to the shell prompt after short time for some packages.
   Haven't yet tried to figure out what's the problem.
 - some packages containing shared libraries link them against libc.  While
   this is the right thing to do it will break with the binutils 2.7 we're
   still using.  Fix: finally upgrade to binutils 2.7.
 - some other packages depend on the presence of X11 for at least building.
   Among them for example tcsh.  Should be fixed rsn as Miguel had some
   X clients up.
 - A couple of other packages contain real bugs, usually pretty trivial
   things.
 - yet other package don't build because they depend on other packages that
   don't build, need to be ported to MIPS (Kaffee, eg.) or that are just
   useless on a MIPS box like for example Lilo.

I'll start to upload the SRPM packages listed below plus little endian
binaries.  All in all that's over 150mb, so don't hold the breath.

  Ralf

MAKEDEV-2.2-10.src.rpm SysVinit-2.71-3.src.rpm TheNextLevel-1.1-3.src.rpm
adduser-1.7-2.src.rpm amd-920824upl102-8.src.rpm apache-1.1.3-4.src.rpm
ash-0.2-9.src.rpm at-2.9b-3.src.rpm autoconf-2.12-2.src.rpm
automake-1.2-1.src.rpm bash-1.14.7-2.src.rpm bc-1.03-6.src.rpm
bc-1.04-1.src.rpm bdflush-1.5-6.src.rpm biff-0.10-1.src.rpm
bind-4.9.5p1-3.src.rpm bison-1.25-1.src.rpm bison-1.25-2.src.rpm
bm2font-3.0-6.src.rpm bm2font-3.0-7.src.rpm bootp-2.4.3-3.src.rpm
bootparamd-0.10-1.src.rpm bootpc-061-3.src.rpm byacc-1.9-4.src.rpm
byacc-1.9-5.src.rpm caching-nameserver-1.1-1.src.rpm cdecl-2.5-4.src.rpm
cdp-0.33-7.src.rpm christminster-3-3.src.rpm colour-yahtzee-1.0-4.src.rpm
control-panel-2.6-1.src.rpm cpio-2.4.2-5.src.rpm cproto-4.4-5.src.rpm
cracklib-2.5-2.src.rpm crontabs-1.5-1.src.rpm ctags-1.5-2.src.rpm
cvs-1.9-2.src.rpm dev-2.5.2-1.src.rpm dhcpcd-0.65-1.src.rpm
dialog-0.6-8.src.rpm diffstat-1.25-2.src.rpm diffutils-2.7-7.src.rpm
e2fsprogs-1.10-0.src.rpm ed-0.2-6.src.rpm efax-0.8a-4.src.rpm
eject-1.4-4.src.rpm etcskel-1.3-2.src.rpm ext2ed-0.1-9.src.rpm
f2c-19960205-9.src.rpm faq-4.0-1.src.rpm fetchmail-2.2-3.src.rpm
file-3.22-6.src.rpm filesystem-1.3-1.src.rpm fileutils-3.16-3.src.rpm
findutils-4.1-13.src.rpm finger-0.10-2.src.rpm flex-2.5.4-2.src.rpm
fort77-1.14a-2.src.rpm fortune-mod-1.0-4.src.rpm fstool-2.5-1.src.rpm
ftp-0.10-1.src.rpm fwhois-1.00-6.src.rpm gawk-3.0.2-2.src.rpm
gencat-022591-4.src.rpm gettext-0.10-2.src.rpm gettext-0.10-5.src.rpm
getty_ps-2.0.7h-5.src.rpm giftrans-1.11.1-5.src.rpm git-4.3.16-2.src.rpm
gnuchess-4.0.pl77-2.src.rpm grail-0.3b2-1.src.rpm grep-2.0-6.src.rpm
groff-1.10-9.src.rpm gzip-1.2.4-9.src.rpm hdparm-3.1-3.src.rpm
helptool-2.3-1.src.rpm howto-4.2-3.src.rpm imap-4.1.BETA-6.src.rpm
indent-1.9.1-6.src.rpm indexhtml-4.2-1.src.rpm initscripts-3.16-1.src.rpm
intimed-1.10-3.src.rpm intimed-1.10-4.src.rpm ircii-2.8.2-7.src.rpm
ircii-2.8.2-8.src.rpm jdk-1.0.2.2-3.src.rpm joe-2.8-8.src.rpm
kbd-0.91-10.src.rpm ldp-4.2-1.src.rpm less-321-4.src.rpm
lha-1.00-5.src.rpm linuxdoc-sgml-1.5-7.src.rpm logrotate-2.3-4.src.rpm
lout-3.08-1.src.rpm lout-3.08-2.src.rpm lpr-0.19-1.src.rpm
lrzsz-0.12.14-2.src.rpm lynx-2.6-3.src.rpm m4-1.4-7.src.rpm
macutils-2.0b3-5.src.rpm mailcap-1.0-3.src.rpm mailx-5.5.kw-7.src.rpm
make-3.75-2.src.rpm man-1.4j-2.src.rpm man-pages-1.15-1.src.rpm
mb-5.0-7.src.rpm mgetty-1.1.5-3.src.rpm mingetty-0.9.4-4.src.rpm
minicom-1.75-3.src.rpm mkdosfs-ygg-0.3b-5.src.rpm mkisofs-1.10rel-1.src.rpm
mkisofs-1.10rel-2.src.rpm mktemp-1.4-2.src.rpm modemtool-1.1-2.src.rpm
modutils-2.1.55-1.src.rpm mount-2.6h-1.src.rpm mpage-2.4-2.src.rpm
mt-st-0.4-3.src.rpm mtools-3.6-2.src.rpm mtools-3.6-3.src.rpm
mutt-0.81e-3.src.rpm mysterious-1.0-2.src.rpm ncftp-2.3.0-6.src.rpm
ncompress-4.2.4-7.src.rpm ncurses-1.9.9e-4.src.rpm nenscript-1.13++-9.src.rpm
net-tools-1.32.alpha-2.src.rpm netkit-base-0.10-2.src.rpm nls-1.0-2.src.rpm
ntalk-0.10-1.src.rpm open-1.3-5.src.rpm open-1.3-6.src.rpm
p2c-1.20-8.src.rpm pam-0.57-3.src.rpm pamconfig-0.51-2.src.rpm
pamconfig-0.51-3.src.rpm passwd-0.50-8.src.rpm patch-2.1-5.src.rpm
pdksh-5.2.12-2.src.rpm perl-5.003-9.src.rpm pidentd-2.5.1-6.src.rpm
pine-3.96-1.src.rpm pinfocom-3.0-4.src.rpm pmake-1.0-5.src.rpm
popt-1.0-1.src.rpm portmap-4.0-4.src.rpm ppp-2.2.0f-4.src.rpm
procinfo-0.9-2.src.rpm procmail-3.10-11.src.rpm psacct-6.2-2.src.rpm
psmisc-11-5.src.rpm pwdb-0.54-5.src.rpm rcs-5.7-5.src.rpm
rdate-0.960923-2.src.rpm rdist-1.0-6.src.rpm readline-2.1-1.src.rpm
redhat-release-4.8-1.src.rpm rhmask-1.0-2.src.rpm rootfiles-1.5-1.src.rpm
routed-0.10-1.src.rpm rpm-2.4.7-1glibc.src.rpm rsh-0.10-1.src.rpm
rusers-0.10-1.src.rpm rwall-0.10-1.src.rpm rwho-0.10-1.src.rpm
samba-1.9.16p11-4rh.src.rpm scottfree-1.14-3.src.rpm screen-3.7.2-3.src.rpm
sed-2.05-7.src.rpm setconsole-1.0-1.src.rpm sh-utils-1.16-6.src.rpm
shadow-utils-970616-4.src.rpm sharutils-4.2-7.src.rpm slang-0.99.37-2.src.rpm
slang-0.99.38-1.src.rpm sliplogin-2.1.0-7.src.rpm slrn-0.9.3.2-2.src.rpm
sox-11g-5.src.rpm stat-1.5-6.src.rpm statnet-2.00-4.src.rpm
statserial-1.1-8.src.rpm symlinks-1.0-6.src.rpm sysklogd-1.3-16.src.rpm
taper-6.7.4-3.src.rpm tcp_wrappers-7.5-2.src.rpm tcpdump-3.3-2.src.rpm
telnet-0.10-1.src.rpm tetex-0.4pl8-5.src.rpm textutils-1.22-2.src.rpm
tftp-0.10-2.src.rpm time-1.7-2.src.rpm timed-0.10-1.src.rpm
timetool-2.3-1.src.rpm tin-1.22-7.src.rpm tmpwatch-1.2-2.src.rpm
traceroute-1.4a5-2.src.rpm tracker-4.3-5.src.rpm tree-1.0-4.src.rpm
trojka-1.1-8.src.rpm ttcp-1.4-1.src.rpm tunelp-1.3-6.src.rpm
umb-scheme-3.2-3.src.rpm unarj-2.41a-4.src.rpm units-1.0-6.src.rpm
unzip-5.12-6.src.rpm uucp-1.06.1-11.src.rpm vixie-cron-3.0.1-15.src.rpm
vlock-1.0-6.src.rpm which-1.0-6.src.rpm words-2-3.src.rpm
wu-ftpd-2.4.2b15-2.src.rpm ypbind-3.0-2.src.rpm yppasswd-0.9-1.src.rpm
zip-2.1-2.src.rpm zlib-1.0.4-1.src.rpm zsh-3.0.2-2.src.rpm

From eak@cygnus.detroit.sgi.com  Thu Oct 16 15:08:06 1997
Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id PAA05658; Thu, 16 Oct 1997 15:07:52 +0200 (MET DST)
Received-Date: Thu, 16 Oct 1997 15:07:52 +0200 (MET DST)
Received: from dataserv.detroit.sgi.com (dataserv.detroit.sgi.com [169.238.128.2]) by deliverator.sgi.com (950413.SGI.8.6.12/970507) via ESMTP id GAA03962; Thu, 16 Oct 1997 06:07:17 -0700
	env-from (eak@cygnus.detroit.sgi.com)
Received: from cygnus.detroit.sgi.com by dataserv.detroit.sgi.com via ESMTP (940816.SGI.8.6.9/930416.SGI)
	 id JAA21327; Thu, 16 Oct 1997 09:07:02 -0400
Sender: eak@cygnus.detroit.sgi.com
Message-ID: <34461176.55EF32BE@cygnus.detroit.sgi.com>
Date: Thu, 16 Oct 1997 09:07:02 -0400
From: Eric Kimminau <eak@cygnus.detroit.sgi.com>
Reply-To: eak@detroit.sgi.com
Organization: Silicon Graphics, Inc
X-Mailer: Mozilla 4.03C-SGI [en] (X11; I; IRIX 6.3 IP32)
MIME-Version: 1.0
To: Ralf Baechle <ralf@cobaltmicro.com>
CC: Alan Cox <alan@lxorguk.ukuu.org.uk>,
        Miguel de Icaza <miguel@nuclecu.unam.mx>, linux@cthulhu.engr.sgi.com,
        linux-mips@fnet.fr
Subject: Re: More Linux/SGI status
References: <199710072241.RAA01259@athena.nuclecu.unam.mx> <m0xIqbs-0005FiC@lightning.swansea.linux.org.uk> <19971015214825.01081@tbird.cobaltmicro.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 7904
Lines: 139

I am still having problems just getting our Indy to boot linux. I am in
a completely SGI environment with no PC already running linux to boot
from. 

Is there anyone else using this type of environment that has done a
basic HOWTO for getting up and running? If you have the basics, I
PROMISE to document it fully with graphics, images, etc. Ill do it in an
HTML form which will immediately be placed on linus.linux.

Thanks,
                    Eric.

P.S. I haven't made much progress because I haven't spent much time on
it. I hoping this is going to dramatically change over the next several
days.


Ralf Baechle wrote:
> 
> On Wed, Oct 08, 1997 at 08:32:43AM +0100, Alan Cox wrote:
> > >     4. A nice, easy-to use install program.  Taking the existing
> > >        Red Hat/Mustand install program and port it should be
> > >        pretty easy.
> >
> > The big install problem is repartitioning an EFS system without damaging
> > the EFS. There seem to be tools to do it via tape from reading the CD's.
> >
> > Once my SGI appears cranking out a distribution set is still my first goal
> 
> I asked Ariel, your box is on it's way.  I hope the transport guys
> hurry as I'm getting pretty close to a useable distribution.  Appended
> is a list of the RPMs which I'm currently using.  They're mostly from
> the RedHat 4.9 aka Mustang distribution.  There are just a few things
> left to fix to build the entire distribution:
> 
>  - rpm just returns to the shell prompt after short time for some packages.
>    Haven't yet tried to figure out what's the problem.
>  - some packages containing shared libraries link them against libc.  While
>    this is the right thing to do it will break with the binutils 2.7 we're
>    still using.  Fix: finally upgrade to binutils 2.7.
>  - some other packages depend on the presence of X11 for at least building.
>    Among them for example tcsh.  Should be fixed rsn as Miguel had some
>    X clients up.
>  - A couple of other packages contain real bugs, usually pretty trivial
>    things.
>  - yet other package don't build because they depend on other packages that
>    don't build, need to be ported to MIPS (Kaffee, eg.) or that are just
>    useless on a MIPS box like for example Lilo.
> 
> I'll start to upload the SRPM packages listed below plus little endian
> binaries.  All in all that's over 150mb, so don't hold the breath.
> 
>   Ralf
> 
> MAKEDEV-2.2-10.src.rpm SysVinit-2.71-3.src.rpm TheNextLevel-1.1-3.src.rpm
> adduser-1.7-2.src.rpm amd-920824upl102-8.src.rpm apache-1.1.3-4.src.rpm
> ash-0.2-9.src.rpm at-2.9b-3.src.rpm autoconf-2.12-2.src.rpm
> automake-1.2-1.src.rpm bash-1.14.7-2.src.rpm bc-1.03-6.src.rpm
> bc-1.04-1.src.rpm bdflush-1.5-6.src.rpm biff-0.10-1.src.rpm
> bind-4.9.5p1-3.src.rpm bison-1.25-1.src.rpm bison-1.25-2.src.rpm
> bm2font-3.0-6.src.rpm bm2font-3.0-7.src.rpm bootp-2.4.3-3.src.rpm
> bootparamd-0.10-1.src.rpm bootpc-061-3.src.rpm byacc-1.9-4.src.rpm
> byacc-1.9-5.src.rpm caching-nameserver-1.1-1.src.rpm cdecl-2.5-4.src.rpm
> cdp-0.33-7.src.rpm christminster-3-3.src.rpm colour-yahtzee-1.0-4.src.rpm
> control-panel-2.6-1.src.rpm cpio-2.4.2-5.src.rpm cproto-4.4-5.src.rpm
> cracklib-2.5-2.src.rpm crontabs-1.5-1.src.rpm ctags-1.5-2.src.rpm
> cvs-1.9-2.src.rpm dev-2.5.2-1.src.rpm dhcpcd-0.65-1.src.rpm
> dialog-0.6-8.src.rpm diffstat-1.25-2.src.rpm diffutils-2.7-7.src.rpm
> e2fsprogs-1.10-0.src.rpm ed-0.2-6.src.rpm efax-0.8a-4.src.rpm
> eject-1.4-4.src.rpm etcskel-1.3-2.src.rpm ext2ed-0.1-9.src.rpm
> f2c-19960205-9.src.rpm faq-4.0-1.src.rpm fetchmail-2.2-3.src.rpm
> file-3.22-6.src.rpm filesystem-1.3-1.src.rpm fileutils-3.16-3.src.rpm
> findutils-4.1-13.src.rpm finger-0.10-2.src.rpm flex-2.5.4-2.src.rpm
> fort77-1.14a-2.src.rpm fortune-mod-1.0-4.src.rpm fstool-2.5-1.src.rpm
> ftp-0.10-1.src.rpm fwhois-1.00-6.src.rpm gawk-3.0.2-2.src.rpm
> gencat-022591-4.src.rpm gettext-0.10-2.src.rpm gettext-0.10-5.src.rpm
> getty_ps-2.0.7h-5.src.rpm giftrans-1.11.1-5.src.rpm git-4.3.16-2.src.rpm
> gnuchess-4.0.pl77-2.src.rpm grail-0.3b2-1.src.rpm grep-2.0-6.src.rpm
> groff-1.10-9.src.rpm gzip-1.2.4-9.src.rpm hdparm-3.1-3.src.rpm
> helptool-2.3-1.src.rpm howto-4.2-3.src.rpm imap-4.1.BETA-6.src.rpm
> indent-1.9.1-6.src.rpm indexhtml-4.2-1.src.rpm initscripts-3.16-1.src.rpm
> intimed-1.10-3.src.rpm intimed-1.10-4.src.rpm ircii-2.8.2-7.src.rpm
> ircii-2.8.2-8.src.rpm jdk-1.0.2.2-3.src.rpm joe-2.8-8.src.rpm
> kbd-0.91-10.src.rpm ldp-4.2-1.src.rpm less-321-4.src.rpm
> lha-1.00-5.src.rpm linuxdoc-sgml-1.5-7.src.rpm logrotate-2.3-4.src.rpm
> lout-3.08-1.src.rpm lout-3.08-2.src.rpm lpr-0.19-1.src.rpm
> lrzsz-0.12.14-2.src.rpm lynx-2.6-3.src.rpm m4-1.4-7.src.rpm
> macutils-2.0b3-5.src.rpm mailcap-1.0-3.src.rpm mailx-5.5.kw-7.src.rpm
> make-3.75-2.src.rpm man-1.4j-2.src.rpm man-pages-1.15-1.src.rpm
> mb-5.0-7.src.rpm mgetty-1.1.5-3.src.rpm mingetty-0.9.4-4.src.rpm
> minicom-1.75-3.src.rpm mkdosfs-ygg-0.3b-5.src.rpm mkisofs-1.10rel-1.src.rpm
> mkisofs-1.10rel-2.src.rpm mktemp-1.4-2.src.rpm modemtool-1.1-2.src.rpm
> modutils-2.1.55-1.src.rpm mount-2.6h-1.src.rpm mpage-2.4-2.src.rpm
> mt-st-0.4-3.src.rpm mtools-3.6-2.src.rpm mtools-3.6-3.src.rpm
> mutt-0.81e-3.src.rpm mysterious-1.0-2.src.rpm ncftp-2.3.0-6.src.rpm
> ncompress-4.2.4-7.src.rpm ncurses-1.9.9e-4.src.rpm nenscript-1.13++-9.src.rpm
> net-tools-1.32.alpha-2.src.rpm netkit-base-0.10-2.src.rpm nls-1.0-2.src.rpm
> ntalk-0.10-1.src.rpm open-1.3-5.src.rpm open-1.3-6.src.rpm
> p2c-1.20-8.src.rpm pam-0.57-3.src.rpm pamconfig-0.51-2.src.rpm
> pamconfig-0.51-3.src.rpm passwd-0.50-8.src.rpm patch-2.1-5.src.rpm
> pdksh-5.2.12-2.src.rpm perl-5.003-9.src.rpm pidentd-2.5.1-6.src.rpm
> pine-3.96-1.src.rpm pinfocom-3.0-4.src.rpm pmake-1.0-5.src.rpm
> popt-1.0-1.src.rpm portmap-4.0-4.src.rpm ppp-2.2.0f-4.src.rpm
> procinfo-0.9-2.src.rpm procmail-3.10-11.src.rpm psacct-6.2-2.src.rpm
> psmisc-11-5.src.rpm pwdb-0.54-5.src.rpm rcs-5.7-5.src.rpm
> rdate-0.960923-2.src.rpm rdist-1.0-6.src.rpm readline-2.1-1.src.rpm
> redhat-release-4.8-1.src.rpm rhmask-1.0-2.src.rpm rootfiles-1.5-1.src.rpm
> routed-0.10-1.src.rpm rpm-2.4.7-1glibc.src.rpm rsh-0.10-1.src.rpm
> rusers-0.10-1.src.rpm rwall-0.10-1.src.rpm rwho-0.10-1.src.rpm
> samba-1.9.16p11-4rh.src.rpm scottfree-1.14-3.src.rpm screen-3.7.2-3.src.rpm
> sed-2.05-7.src.rpm setconsole-1.0-1.src.rpm sh-utils-1.16-6.src.rpm
> shadow-utils-970616-4.src.rpm sharutils-4.2-7.src.rpm slang-0.99.37-2.src.rpm
> slang-0.99.38-1.src.rpm sliplogin-2.1.0-7.src.rpm slrn-0.9.3.2-2.src.rpm
> sox-11g-5.src.rpm stat-1.5-6.src.rpm statnet-2.00-4.src.rpm
> statserial-1.1-8.src.rpm symlinks-1.0-6.src.rpm sysklogd-1.3-16.src.rpm
> taper-6.7.4-3.src.rpm tcp_wrappers-7.5-2.src.rpm tcpdump-3.3-2.src.rpm
> telnet-0.10-1.src.rpm tetex-0.4pl8-5.src.rpm textutils-1.22-2.src.rpm
> tftp-0.10-2.src.rpm time-1.7-2.src.rpm timed-0.10-1.src.rpm
> timetool-2.3-1.src.rpm tin-1.22-7.src.rpm tmpwatch-1.2-2.src.rpm
> traceroute-1.4a5-2.src.rpm tracker-4.3-5.src.rpm tree-1.0-4.src.rpm
> trojka-1.1-8.src.rpm ttcp-1.4-1.src.rpm tunelp-1.3-6.src.rpm
> umb-scheme-3.2-3.src.rpm unarj-2.41a-4.src.rpm units-1.0-6.src.rpm
> unzip-5.12-6.src.rpm uucp-1.06.1-11.src.rpm vixie-cron-3.0.1-15.src.rpm
> vlock-1.0-6.src.rpm which-1.0-6.src.rpm words-2-3.src.rpm
> wu-ftpd-2.4.2b15-2.src.rpm ypbind-3.0-2.src.rpm yppasswd-0.9-1.src.rpm
> zip-2.1-2.src.rpm zlib-1.0.4-1.src.rpm zsh-3.0.2-2.src.rpm

-- 
Eric Kimminau                           System Engineer/RSA
eak@detroit.sgi.com                     Silicon Graphics, Inc
Voice: (248) 848-4455                   39001 West 12 Mile Rd.
Fax:   (248) 848-5600                   Farmington, MI 48331-2903

                 VNet Extension - 6-327-4455
              "I speak my mind and no one else's."
       http://www.dcs.ex.ac.uk/~aba/rsa/perl-rsa-sig.html

    When confronted by a difficult problem, solve it by reducing 
    it to the question, "How would the Lone Ranger handle this?"

From adevries@engsoc.carleton.ca  Thu Oct 16 17:39:52 1997
Received: from lager.engsoc.carleton.ca (adevries@lager.engsoc.carleton.ca [134.117.69.26]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id RAA06348; Thu, 16 Oct 1997 17:39:41 +0200 (MET DST)
Received-Date: Thu, 16 Oct 1997 17:39:41 +0200 (MET DST)
Received: from localhost (adevries@localhost)
          by lager.engsoc.carleton.ca (8.8.5/8.8.4) with SMTP
	  id LAA02086; Thu, 16 Oct 1997 11:39:30 -0400
Date: Thu, 16 Oct 1997 11:39:29 -0400 (EDT)
From: Alex deVries <adevries@engsoc.carleton.ca>
To: eak@detroit.sgi.com
cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Re: More Linux/SGI status
In-Reply-To: <34461176.55EF32BE@cygnus.detroit.sgi.com>
Message-ID: <Pine.LNX.3.95.971016113322.32057A-100000@lager.engsoc.carleton.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1094
Lines: 27


On Thu, 16 Oct 1997, Eric Kimminau wrote:

> I am still having problems just getting our Indy to boot linux. I am in
> a completely SGI environment with no PC already running linux to boot
> from. 
> 
> Is there anyone else using this type of environment that has done a
> basic HOWTO for getting up and running? If you have the basics, I
> PROMISE to document it fully with graphics, images, etc. Ill do it in an
> HTML form which will immediately be placed on linus.linux.

I can think of only one way of doing it...

Stick your kernel in /, and boot it.  That kernel would have to have the
EFS file system enabled so that you could mount a local disk with a Linux
image as /.  Then, partition your other disk, and install RPM's to your
heart's content.

The better way of doing this, though, is to stick all the RPM's on a SCSI
disk on an ext2 partition.  Make a Linux ramdisk (no ARC or anything
else... just the usual Linux ramdisk as found in Sparc and i386) with a
base filesystem.  From that, partition your second disk, and install RPMs.

I'm working on the ramdisk stuff... 

- Alex

From tim@caddyshack.  Thu Oct 16 19:15:26 1997
Received: from cobaltmicro.com ([209.19.61.2]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id TAA06778; Thu, 16 Oct 1997 19:15:25 +0200 (MET DST)
Received-Date: Thu, 16 Oct 1997 19:15:25 +0200 (MET DST)
Received: from caddyshack.cobaltmicro.com (209.19.61.17) by cobaltmicro.com
 with SMTP (Eudora Internet Mail Server 1.2); Thu, 16 Oct 1997 10:18:37 -0700
Date: Thu, 16 Oct 1997 10:21:27 -0700 (PDT)
From: Timothy Stonis <tim@caddyshack.>
To: linux-mips@fnet.fr
cc: ralf@cobaltmicro.com
Subject: Re: More Linux/SGI status
In-Reply-To: <19971015214825.01081@tbird.cobaltmicro.com>
Message-ID: <Pine.LNX.3.96.971016101737.29805F-100000@caddyshack>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 502
Lines: 18

	

On Wed, 15 Oct 1997, Ralf Baechle wrote:

> On Wed, Oct 08, 1997 at 08:32:43AM +0100, Alan Cox wrote:
> 
>  - rpm just returns to the shell prompt after short time for some packages.
>    Haven't yet tried to figure out what's the problem.
> 

  This happens for all of the noarch (architecture independant) packages
(filesystem, setup, etc).  You have to change the /usr/lib/rpmrc file so
that mips is compatible with noarch packages. Just search for sparc or
alpha and copy what they do. 

_Tim



From ewt@redhat.com  Thu Oct 16 19:36:14 1997
Received: from lacrosse.redhat.com (ewt@lacrosse.redhat.com [207.175.42.154]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id TAA06883; Thu, 16 Oct 1997 19:36:12 +0200 (MET DST)
Received-Date: Thu, 16 Oct 1997 19:36:12 +0200 (MET DST)
Received: from localhost (ewt@localhost)
	by lacrosse.redhat.com (8.8.5/8.8.7) with SMTP id NAA29155;
	Thu, 16 Oct 1997 13:36:08 -0400
Date: Thu, 16 Oct 1997 13:36:08 -0400 (EDT)
From: Erik Troan <ewt@redhat.com>
To: linux-mips@fnet.fr
cc: ralf@cobaltmicro.com
Subject: Re: More Linux/SGI status
In-Reply-To: <Pine.LNX.3.96.971016101737.29805F-100000@caddyshack>
Message-ID: <Pine.LNX.3.95.971016133551.28999D-100000@lacrosse.redhat.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 698
Lines: 15

On Thu, 16 Oct 1997, Timothy Stonis wrote:

>   This happens for all of the noarch (architecture independant) packages
> (filesystem, setup, etc).  You have to change the /usr/lib/rpmrc file so
> that mips is compatible with noarch packages. Just search for sparc or
> alpha and copy what they do. 

I just fixed this in my build tree; RPM 2.4.9 will handle this better.

Erik

-------------------------------------------------------------------------------
| "Tarball is idiomatically related to furball and hairball" -- Carl D. Roth  |
|                                                                             |
|       Erik Troan   =   ewt@redhat.com     =    ewt@sunsite.unc.edu          |

From alan@lxorguk.ukuu.org.uk  Thu Oct 16 22:14:04 1997
Received: from snowcrash.cymru.net (snowcrash.cymru.net [163.164.160.3]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id WAA08693; Thu, 16 Oct 1997 22:14:02 +0200 (MET DST)
Received-Date: Thu, 16 Oct 1997 22:14:02 +0200 (MET DST)
Received: from lightning.swansea.linux.org.uk (centre.swanlink.ukuu.org.uk [137.44.10.205]) by snowcrash.cymru.net (8.8.5-q-beta3/8.7.1) with SMTP id VAA26939; Thu, 16 Oct 1997 21:10:20 +0100
Received: by lightning.swansea.linux.org.uk (Smail3.1.29.1 #2)
	id m0xLvHY-0005G4C; Thu, 16 Oct 97 20:08 BST
Message-Id: <m0xLvHY-0005G4C@lightning.swansea.linux.org.uk>
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
Subject: Re: More Linux/SGI status
To: adevries@engsoc.carleton.ca (Alex deVries)
Date: Thu, 16 Oct 1997 20:08:28 +0100 (BST)
Cc: eak@detroit.sgi.com, linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
In-Reply-To: <Pine.LNX.3.95.971016113322.32057A-100000@lager.engsoc.carleton.ca> from "Alex deVries" at Oct 16, 97 11:39:29 am
Content-Type: text
Content-Length: 286
Lines: 8

> Stick your kernel in /, and boot it.  That kernel would have to have the
> EFS file system enabled so that you could mount a local disk with a Linux
> image as /.  Then, partition your other disk, and install RPM's to your
> heart's content.

NFSroot is another possible way...

Alan

From adevries@engsoc.carleton.ca  Thu Oct 16 22:19:44 1997
Received: from lager.engsoc.carleton.ca (adevries@lager.engsoc.carleton.ca [134.117.69.26]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id WAA08739; Thu, 16 Oct 1997 22:19:42 +0200 (MET DST)
Received-Date: Thu, 16 Oct 1997 22:19:42 +0200 (MET DST)
Received: from localhost (adevries@localhost)
          by lager.engsoc.carleton.ca (8.8.5/8.8.4) with SMTP
	  id QAA24444; Thu, 16 Oct 1997 16:16:44 -0400
Date: Thu, 16 Oct 1997 16:16:44 -0400 (EDT)
From: Alex deVries <adevries@engsoc.carleton.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
cc: eak@detroit.sgi.com, linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Re: More Linux/SGI status
In-Reply-To: <m0xLvHY-0005G4C@lightning.swansea.linux.org.uk>
Message-ID: <Pine.LNX.3.95.971016161554.32057I-100000@lager.engsoc.carleton.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 416
Lines: 12


On Thu, 16 Oct 1997, Alan Cox wrote:
> > Stick your kernel in /, and boot it.  That kernel would have to have the
> > EFS file system enabled so that you could mount a local disk with a Linux
> > image as /.  Then, partition your other disk, and install RPM's to your
> > heart's content.
> NFSroot is another possible way...

But, I believe the problem was that he had no other machine to NFS root
off of.

- Alex

From alfonso@borak.es  Fri Oct 17 12:05:05 1997
Received: from borak.es (alfonso@dns.borak.es [194.224.14.10]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id MAA18370; Fri, 17 Oct 1997 12:00:56 +0200 (MET DST)
Received-Date: Fri, 17 Oct 1997 12:00:56 +0200 (MET DST)
Received: from localhost by borak.es (SMI-8.6/SMI-SVR4)
	id LAA05831; Fri, 17 Oct 1997 11:56:23 +0200
Date: Fri, 17 Oct 1997 11:56:23 +0200 (MET DST)
From: AlFonSO CaRabanTEs AlaMo <alfonso@borak.es>
X-Sender: alfonso@dns
To: linux-mips@fnet.fr
Subject: Where is vmlinux to boot from nfs??
Message-ID: <Pine.SOL.3.95.971017115359.5826A-100000@dns>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 431
Lines: 19

I not find vmlinux at
ftp://ftp.linux.sgi.com/pub/mips-linux/GettingStarted/vmlinux

Where is???

Thanks,

///////////////////////////////////////////
-------**********-------
AlFonSO CaRabanTEs AlaMo
-------***********------
BORAK INFORMATICA
Avda. Ronda de Poniente, 4
28760 Tres Cantos (MADRID)
Tlf: 34-1-804 44 26
Fax: 34-1-804 40 93
e-mail: alfonso@borak.es
WWW: http://www.borak.es
//////////////////////////////////////////

From nigel@ingenius.co.uk  Fri Oct 17 18:24:36 1997
Received: from post.mail.demon.net (post-10.mail.demon.net [194.217.242.154]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id SAA20424; Fri, 17 Oct 1997 18:24:33 +0200 (MET DST)
Received-Date: Fri, 17 Oct 1997 18:24:33 +0200 (MET DST)
Received: from ingenius.demon.co.uk ([158.152.143.72]) by post.mail.demon.net
           id aa1007743; 17 Oct 97 17:19 BST
From: Nigel Atkinson <nigel@ingenius.co.uk>
To: linux-mips@fnet.fr
MMDF-Warning: Parse error in original version of preceding line at post.mail.demon.net
Subject: MIPS R3000 Port
Date: Fri, 17 Oct 1997 17:22:24 +0100
Message-ID: <01bcdb18$d9ff0c40$488f989e@ingenius.demon.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0004_01BCDB21.3BC37440"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.71.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3
Content-Length: 1777
Lines: 52

This is a multi-part message in MIME format.

------=_NextPart_000_0004_01BCDB21.3BC37440
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear All,

I am about to start writing a port of the Java VM to run on a Sony =
Playstation. I am therefore interested in how much work has been done on =
the Linux port. I am willing to help out with that in any way I can in =
return for any support you can give me! It is a third year computer =
science degree project and I have some experience porting Java and using =
Linux.

cheers,

Nigel

------=_NextPart_000_0004_01BCDB21.3BC37440
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.71.1712.3"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>Dear All,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>I am about to start writing a port =
of the Java=20
VM to run on a Sony Playstation. I am therefore interested in how much =
work has=20
been done on the Linux port. I am willing to help out with that in any =
way I can=20
in return for any support you can give me! It is a third year computer =
science=20
degree project and I have some experience porting Java and using=20
Linux.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>cheers,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>Nigel</FONT></DIV></BODY></HTML>

------=_NextPart_000_0004_01BCDB21.3BC37440--

From ralf@tbird.cobaltmicro.com  Sat Oct 18 08:42:40 1997
Received: from tbird.cobaltmicro.com (ralf@[209.19.61.36]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id IAA26119; Sat, 18 Oct 1997 08:42:39 +0200 (MET DST)
Received-Date: Sat, 18 Oct 1997 08:42:39 +0200 (MET DST)
Received: (from ralf@localhost)
	by tbird.cobaltmicro.com (8.8.5/8.8.5) id XAA30223;
	Fri, 17 Oct 1997 23:40:04 -0700
Message-ID: <19971017234003.40055@tbird.cobaltmicro.com>
Date: Fri, 17 Oct 1997 23:40:03 -0700
From: Ralf Baechle <ralf@tbird.cobaltmicro.com>
To: linux-mips@fnet.fr, linux@engr.sgi.com, alfonso@borak.es
Subject: Re: Where is vmlinux to boot from nfs??
References: <Pine.SOL.3.95.971017115359.5826A-100000@dns>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81e
In-Reply-To: <Pine.SOL.3.95.971017115359.5826A-100000@dns>; from AlFonSO CaRabanTEs AlaMo on Fri, Oct 17, 1997 at 11:56:23AM +0200
Content-Length: 240
Lines: 9

On Fri, Oct 17, 1997 at 11:56:23AM +0200, AlFonSO CaRabanTEs AlaMo wrote:
> I not find vmlinux at
> ftp://ftp.linux.sgi.com/pub/mips-linux/GettingStarted/vmlinux
> 
> Where is???

Could somebody place a kernel image there?  Thanks.

  Ralf

From mrbill@texas.net  Tue Oct 21 00:02:02 1997
Received: from staff1.texas.net (mrbill@staff1.texas.net [207.207.0.38]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id AAA02246; Tue, 21 Oct 1997 00:02:01 +0200 (MET DST)
Received-Date: Tue, 21 Oct 1997 00:02:01 +0200 (MET DST)
Received: (from mrbill@localhost) by staff1.texas.net (8.8.3/8.7.5) id RAA28244; Mon, 20 Oct 1997 17:01:55 -0500 (CDT)
Message-ID: <19971020170154.23056@texas.net>
Date: Mon, 20 Oct 1997 17:01:54 -0500
From: Bill Bradford <mrbill@texas.net>
To: linux-mips@fnet.fr
Subject: subscribe me!
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.74
Content-Length: 335
Lines: 11

Please add me to the Linux-MIPS mailing list.

Thanks.

-- 
Bill Bradford     Senior Systems Engineer, BOFH
mrbill@texas.net     Texas Networking, Inc.  
ICQ: 1864511	      http://www.texas.net
-------------------------------------------------
Catapultam habeo. Nisi pecuniam omnem mihi dabis, 
     ad caput tuum saxum immane mittam.

From easchwei@eos.ncsu.edu  Tue Oct 21 20:19:03 1997
Received: from c11106-211dan.ece.ncsu.edu (c11106-211dan.ece.ncsu.edu [152.1.59.179]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id UAA09908; Tue, 21 Oct 1997 20:19:00 +0200 (MET DST)
Received-Date: Tue, 21 Oct 1997 20:19:00 +0200 (MET DST)
From: easchwei@eos.ncsu.edu
Received: (from easchwei@localhost)
          by c11106-211dan.ece.ncsu.edu (8.8.4/EC02Jan97)
	  id OAA16287; Tue, 21 Oct 1997 14:18:49 -0400 (EDT)
Message-Id: <199710211818.OAA16287@c11106-211dan.ece.ncsu.edu>
Subject: Linux/MIPS help needed
To: linux-mips@fnet.fr
Date: Tue, 21 Oct 1997 14:18:48 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL24/POP]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 233
Lines: 8


I am interested in the status of the Linux/MIPS port and
any information on installation on DEC 5000 machines.
(We have the hardware, but we need to know what software
to get and what to do with it.)  Thanks for any help.

-- 
Eric

From JOHNMTDM@aol.com  Wed Oct 22 10:08:28 1997
Received: from emout32.mail.aol.com (emout32.mx.aol.com [198.81.11.15]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id KAA16132; Wed, 22 Oct 1997 10:08:24 +0200 (MET DST)
Received-Date: Wed, 22 Oct 1997 10:08:24 +0200 (MET DST)
From: JOHNMTDM@aol.com
Received: (from root@localhost)
	  by emout32.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0)
	  id EAA11016 for linux-mips@fnet.fr;
	  Wed, 22 Oct 1997 04:07:28 -0400 (EDT)
Date: Wed, 22 Oct 1997 04:07:28 -0400 (EDT)
Message-ID: <971021121252_1167700148@emout13.mail.aol.com>
To: linux-mips@fnet.fr
Subject: Linux for MIPS R4000
Content-Length: 194
Lines: 5

Hello, 
I have a NeTPower MIPS R4000 machine currently running Windows NT 4.0 and I
was wondering what the state of the port of Linux for this machine is.
 Thanks in advance for your help,
John

From email@domain.com  Wed Oct 22 18:06:41 1997
Received: from sarah.ocs.lsumc.edu (SARAH.OCS.LSUMC.EDU [155.58.128.154]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id SAA18520; Wed, 22 Oct 1997 18:05:57 +0200 (MET DST)
Received-Date: Wed, 22 Oct 1997 18:05:57 +0200 (MET DST)
Received: from [155.58.112.211] by sarah.ocs.lsumc.edu
          (Post.Office MTA v3.1.2 release (PO205-101c)
          ID# 0-42511U8000L8000S0) with SMTP id AAA219
          for <linux-mips@fnet.fr>; Wed, 22 Oct 1997 11:06:39 -0500
Message-ID: <344E3385.23A6@domain.com>
Date: Wed, 22 Oct 1997 11:10:29 -0600
From: "Charles A. Dempsey" <email@domain.com>
Reply-To: email@domain.com
Organization: LSU Med Ctr
X-Mailer: Mozilla 2.02 (Macintosh; I; PPC)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: Problems booting a 4000SC.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 1086
Lines: 33

I've got my Magnum 4000SC-50 set up, but I can't get a kernel to boot.

Using either the precompiled milo-0.27.1 milo/pandora or a milo that I 
compiled against linux-970710 (the corresponding pandora compiles but 
doesn't work) the machine appears to load the kernel but then just sits 
there with a blue screen. 

At the "run a program" prompt;

a:milo (floppy spins 1 min, drive light goes out, blue screen forever)

a:pandora
Pandora> boot 
	Kernel text at 0x80000000, size 1211344 bytes
	Kernel data at 0x80127bd0, size 0 bytes
	Kernel bss at 0x80127bd0, size 127636
	Kernel entry at 0x80000494
(the floppy spins 8 min, drive light goes out, blue screen forever)

Pandora> boot vmlinux (Same as above)

I've tried this with three different 970710 kernels including the one 
that works on my 4000PC. I believe I had this problem with my 4000PC-50, 
but milo-0.27.1 with 970710 fixed it.

The machine has the standard Magnum video card, 16 MB RAM, Matsushita CD 
on ID=3, no hard drive.

Does anyone have their 4000SC booting? What kernel/milo/pandora did you 
use?

Thanks,
Charles

From cdemps@lsumc.edu  Wed Oct 22 18:19:29 1997
Received: from sarah.ocs.lsumc.edu (SARAH.OCS.LSUMC.EDU [155.58.128.154]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id SAA18579; Wed, 22 Oct 1997 18:19:19 +0200 (MET DST)
Received-Date: Wed, 22 Oct 1997 18:19:19 +0200 (MET DST)
Received: from [155.58.112.211] by sarah.ocs.lsumc.edu
          (Post.Office MTA v3.1.2 release (PO205-101c)
          ID# 0-42511U8000L8000S0) with SMTP id AAA176
          for <linux-mips@fnet.fr>; Wed, 22 Oct 1997 11:20:08 -0500
Message-ID: <344E36AF.DD7@lsumc.edu>
Date: Wed, 22 Oct 1997 11:23:59 -0600
From: cdemps@lsumc.edu (Dempsey, Charles)
Reply-To: cdemps@lsumc.edu
Organization: LSU Med Ctr
X-Mailer: Mozilla 2.02 (Macintosh; I; PPC)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: Ramdisk and previous message.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 316
Lines: 9

Sorry about that previous message. Netscape wonked my return address.

Does initrd support compile into any of the kernels? The ones I've tried 
(2.0.14, 2.1.21 and 970710) won't compile if ramdisk is enabled. I'm 
trying to build a distribution for the fun of it, but without the 
ramdisk I'm SOL.

Thanks,
Charles

From ralf@tbird.cobaltmicro.com  Thu Oct 23 02:57:04 1997
Received: from tbird.cobaltmicro.com (ralf@[209.19.61.36]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id CAA22450; Thu, 23 Oct 1997 02:57:03 +0200 (MET DST)
Received-Date: Thu, 23 Oct 1997 02:57:03 +0200 (MET DST)
Received: (from ralf@localhost)
	by tbird.cobaltmicro.com (8.8.5/8.8.5) id RAA31840;
	Wed, 22 Oct 1997 17:54:22 -0700
Message-ID: <19971022175420.14413@tbird.cobaltmicro.com>
Date: Wed, 22 Oct 1997 17:54:20 -0700
From: Ralf Baechle <ralf@tbird.cobaltmicro.com>
To: linux-mips@fnet.fr
Subject: Re: Problems booting a 4000SC.
References: <344E3385.23A6@domain.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81e
In-Reply-To: <344E3385.23A6@domain.com>; from Charles A. Dempsey on Wed, Oct 22, 1997 at 11:10:29AM -0600
Content-Length: 1686
Lines: 43

On Wed, Oct 22, 1997 at 11:10:29AM -0600, Charles A. Dempsey wrote:
> I've got my Magnum 4000SC-50 set up, but I can't get a kernel to boot.
> 
> Using either the precompiled milo-0.27.1 milo/pandora or a milo that I 
> compiled against linux-970710 (the corresponding pandora compiles but 
> doesn't work) the machine appears to load the kernel but then just sits 
> there with a blue screen. 
> 
> At the "run a program" prompt;
> 
> a:milo (floppy spins 1 min, drive light goes out, blue screen forever)
> 
> a:pandora
> Pandora> boot 
> 	Kernel text at 0x80000000, size 1211344 bytes
> 	Kernel data at 0x80127bd0, size 0 bytes
> 	Kernel bss at 0x80127bd0, size 127636
> 	Kernel entry at 0x80000494
> (the floppy spins 8 min, drive light goes out, blue screen forever)

The awful low speed is "normal", the ARC firmware is Magnum is buggy.
Somebody should probably try to find a faster workaround ...

> Pandora> boot vmlinux (Same as above)
> 
> I've tried this with three different 970710 kernels including the one 
> that works on my 4000PC. I believe I had this problem with my 4000PC-50, 
> but milo-0.27.1 with 970710 fixed it.
> 
> The machine has the standard Magnum video card, 16 MB RAM, Matsushita CD 
> on ID=3, no hard drive.
> 
> Does anyone have their 4000SC booting? What kernel/milo/pandora did you 
> use?

I suspect we've got still a bug in the handling of the SC/MC caches.
Hard to fix without having a machine with such a CPU.  Another cache
problem we have to fix are I/D caches with different line sizes like
in the Olivetti M700-10.  And we don't handle split I/D level 2
SC/MC caches correctly, but I so far I don't of any machine using such
caches.

  Ralf

From ratkins@osix.com.au  Thu Oct 23 04:33:53 1997
Received: from arnie.osix.com.au (ether.arnie.osix.com.au [203.18.59.2]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id EAA23280; Thu, 23 Oct 1997 04:33:47 +0200 (MET DST)
Received-Date: Thu, 23 Oct 1997 04:33:47 +0200 (MET DST)
Received: by arnie.osix.com.au (AIX 3.2/UCB 5.64/4.03)
          id AA15929; Thu, 23 Oct 1997 12:37:22 +1100
From: ratkins@osix.com.au (Robert Atkins)
Message-Id: <9710230137.AA15929@arnie.osix.com.au>
Subject: Linux/MIPS on M/120?
To: linux-mips@fnet.fr
Date: Thu, 23 Oct 1997 12:37:22 +1100 (EETDT)
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 633
Lines: 17

Hi Guys,

I've just managed to pick up an old Mips M/120 for free, and I was
wondering if Linux would run on it. Currently it's running something
called "RISC OS 4.02", which appears to be some sort of bastardised
BSD. However I don't have the original OS tapes or anything :(.

The machine has a Mips R2000A CPU. From what I've managed to find on the
web so far, R2000 CPUs aren't properly supported? 

Cheers,
-- 
/**
 * @author Robert Atkins, ratkins@osix.com.au, www.osix.com.au/~ratkins
 * "Robert must learn to sit still." - My kindergarten report 
 */
I've lost my PalmPilot somewhere in Surfer's Paradise! See my web page...

From cdemps@lsumc.edu  Thu Oct 23 16:41:39 1997
Received: from sarah.ocs.lsumc.edu (SARAH.OCS.LSUMC.EDU [155.58.128.154]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id QAA27415; Thu, 23 Oct 1997 16:41:36 +0200 (MET DST)
Received-Date: Thu, 23 Oct 1997 16:41:36 +0200 (MET DST)
Received: from [155.58.112.211] by sarah.ocs.lsumc.edu
          (Post.Office MTA v3.1.2 release (PO205-101c)
          ID# 0-42511U8000L8000S0) with SMTP id AAA172
          for <linux-mips@fnet.fr>; Thu, 23 Oct 1997 09:42:22 -0500
Message-ID: <344F713E.4E4C@lsumc.edu>
Date: Thu, 23 Oct 1997 09:46:06 -0600
From: cdemps@lsumc.edu (Dempsey, Charles)
Reply-To: cdemps@lsumc.edu
Organization: LSU Med Ctr
X-Mailer: Mozilla 2.02 (Macintosh; I; PPC)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: Re: Problems booting a 4000SC.
References: <344E3385.23A6@domain.com> <19971022175420.14413@tbird.cobaltmicro.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 1963
Lines: 52

Ralf Baechle wrote:
> 
> On Wed, Oct 22, 1997 at 11:10:29AM -0600, Charles A. Dempsey wrote:
> > I've got my Magnum 4000SC-50 set up, but I can't get a kernel to boot.

> I suspect we've got still a bug in the handling of the SC/MC caches.
> Hard to fix without having a machine with such a CPU.  Another cache
> problem we have to fix are I/D caches with different line sizes like
> in the Olivetti M700-10.  And we don't handle split I/D level 2
> SC/MC caches correctly, but I so far I don't of any machine using such
> caches.

Comparing the pandora output on the two machines the 4000PC-50 says;

Arc Vendor ID												:[MIPS MAG]
Arc Product ID											:[00006b8283c0051]
Arc System ID												:[Microsoft-Jazz]
Arc CPU ID															:[Mips R4000 PC]
Processor type											:[R4000PC I04 V3.0]
Primary ICache size						:[0x2000]
Primary ICache line size	:[0x0020]
Primary DCache size						:[0x2000]
Primary DCache line size	:[0x0010]
Secondary Cache size					:[unknown]
Arc System identified as	:Mips Magnum 4000 (Jazz)

The 4000SC-50 says;

Arc Vendor ID												:[MIPS MAG]
Arc Product ID											:[00006b829034004d]
Arc System ID												:[Microsoft-Jazz]
Arc CPU ID															:[Mips R4000 SC]
Processor type											:[R4000PC I04 V3.0]
Primary ICache size						:[0x2000]
Primary ICache line size	:[0x0010]
Primary DCache size						:[0x2000]
Primary DCache line size	:[0x0010]
Secondary Cache size					:[unknown]
Arc System identified as	:Mips Magnum 4000 (Jazz)

The odd things are;

1. The SC "processor type" is the same as the PC.
2. The cache numbers are the same except for the primary Icache line size, and
3. The secondary cache size is "unknown" in the SC. 

Could this be a boot loader problem? I believe from comparing the floppy disk access 
times on the two machines that the kernel loads but the launch fails before video 
output begins. How does one determine the failed process in such a case?

Thanks,
Charles

From ralf@mail2.cobaltmicro.com  Thu Oct 23 20:02:54 1997
Received: from dns.cobaltmicro.com ([209.19.61.1]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id UAA28841; Thu, 23 Oct 1997 20:02:53 +0200 (MET DST)
Received-Date: Thu, 23 Oct 1997 20:02:53 +0200 (MET DST)
Received: from tbird.cobaltmicro.com (tbird.cobaltmicro.com [209.19.61.36])
	by dns.cobaltmicro.com (8.8.5/8.8.5) with ESMTP id LAA03483
	for <linux-mips@fnet.fr>; Thu, 23 Oct 1997 11:01:15 -0700
Received: (from ralf@localhost)
	by tbird.cobaltmicro.com (8.8.5/8.8.5) id KAA19035;
	Thu, 23 Oct 1997 10:58:41 -0700
Message-ID: <19971023105840.18726@tbird.cobaltmicro.com>
Date: Thu, 23 Oct 1997 10:58:40 -0700
From: Ralf Baechle <ralf@cobaltmicro.com>
To: linux-mips@fnet.fr
Subject: Re: Problems booting a 4000SC.
References: <344E3385.23A6@domain.com> <19971022175420.14413@tbird.cobaltmicro.com> <344F713E.4E4C@lsumc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81e
In-Reply-To: <344F713E.4E4C@lsumc.edu>; from Dempsey, Charles on Thu, Oct 23, 1997 at 09:46:06AM -0600
Content-Length: 1423
Lines: 34

On Thu, Oct 23, 1997 at 09:46:06AM -0600, Dempsey, Charles wrote:
> The odd things are;
> 
> 1. The SC "processor type" is the same as the PC.

Milo doesn't know that there are subtypes of the R4000 / R4400 processors
and calls them all a R4000PC.

> 2. The cache numbers are the same except for the primary Icache line size, and

Sigh.  I didn't know before that the Magnum PC version caches also have
assymetric linesizes.  Linux doesn't handle that.  Actually I thought
that nobody's using something like that.  I or Thomas will fix that.

If you were wondering why it recognices the machine as "Magnum 4000 SC"
though - the string it's printing is returned by the firmware.

> 3. The secondary cache size is "unknown" in the SC. 

Milo is too dumb to figure the linesize.  In fact it is too dumb to handle
the Magnum's caches.  Luckily it's easy to fix by just transplanting
a couple of the kernel's routines.

> Could this be a boot loader problem? I believe from comparing the floppy
> disk access times on the two machines that the kernel loads but the
> launch fails before video output begins. How does one determine the
> failed process in such a case?

It's hard to trace that, no debugger can do it.  Also at the point of the
boot, where the kernel crashes you don't even have a printf like function
available as Milo killed the ARC firmware and the kernel's console isn't
running yet.  Don't worry ...

  Ralf

From mortenh@powertech.no  Thu Oct 23 22:54:50 1997
Received: from mail.powertech.no (root@intentia.powertech.no [195.159.0.220]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id WAA00423; Thu, 23 Oct 1997 22:54:48 +0200 (MET DST)
Received-Date: Thu, 23 Oct 1997 22:54:48 +0200 (MET DST)
Received: from s02i16-0042.no.powertech.net (s02i16-0042.no.powertech.net [195.159.4.42])
	by mail.powertech.no (8.8.5/8.8.5) with SMTP id WAA22845
	for <linux-mips@fnet.fr>; Thu, 23 Oct 1997 22:54:44 +0200
Date: Thu, 23 Oct 1997 22:54:44 +0200
Message-Id: <199710232054.WAA22845@mail.powertech.no>
From: Morten Helgesen <mortenh@powertech.no>
To: linux-mips@fnet.fr
Subject: URL ftp://ftp.fnet.fr/linux-mips/www/linux-mips.html
Organization: AmiWrz Inc.
X-Mailer: Voyager/AmigaOS 2.88
Content-Length: 63
Lines: 3

is there a mailing list fir linux mips ?

mortenh@powertech.no

From mrityu@npi.stpn.soft.net  Sat Oct 25 02:13:40 1997
Received: from dirtpan.npiww.com (dirtpan.npiww.com [207.113.23.2]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id CAA11269; Sat, 25 Oct 1997 02:13:39 +0200 (MET DST)
Received-Date: Sat, 25 Oct 1997 02:13:39 +0200 (MET DST)
Received: from dirtpan-gw.npiww.com [192.9.202.1] by dirtpan.npiww.com (8.6.9/8.6.9) with SMTP id QAA08854 for <linux-mips@fnet.fr>; Fri, 24 Oct 1997 16:24:44 -0400
Message-ID: <34513703.FCC@npi.stpn.soft.net>
Date: Fri, 24 Oct 1997 20:02:11 -0400
From: Mrityunjay Kumar <mrityu@npi.stpn.soft.net>
Reply-To: mrityu@npi.stpn.soft.net
Organization: Network Programs Network Machines Inc
X-Mailer: Mozilla 3.0 (WinNT; I)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: some info please!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 672
Lines: 22

Hi!

I am evaluating a toshiba chip which has a MIPS "R3000A based R3900
Processor Core". I am to find out if we can run Linux on it, or we have
to use pSOS or any other realtime commercial OS. And I know nothing
about MIPS, I have always worked on Linux on x86(not that I know much
about x86!).
So how should I go about it? Is there a way to find out if Linux will
run on that processor, how can I be sure that it is OK to use Linux on
the processor?
And if Linux doesn't work on it, can I make it work?!!
Is pSOS better/equal to Linux?

Any help will be great.

Regards,
Mrityunjay

Network Programs Network Machines Inc.
Piscataway,
New Jersey.
Ph: (908) 562-1111(245)

From dittman@hibernia.dseg.ti.com  Sat Oct 25 02:58:13 1997
Received: from tower.ti.com (tower.ti.com [192.94.94.5]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id CAA11958; Sat, 25 Oct 1997 02:58:12 +0200 (MET DST)
Received-Date: Sat, 25 Oct 1997 02:58:12 +0200 (MET DST)
Received: from hibernia.dseg.ti.com ([157.170.156.89]) by tower.ti.com (8.8.7) with ESMTP id TAA20061 for <linux-mips@fnet.fr>; Fri, 24 Oct 1997 19:57:38 -0500 (CDT)
Received: (from dittman@localhost)
          by hibernia.dseg.ti.com (8.8.5/8.8.4)
	  id TAA01591 for linux-mips@fnet.fr; Fri, 24 Oct 1997 19:58:22 -0500
From: Eric Dittman <dittman@hibernia.dseg.ti.com>
Message-Id: <199710250058.TAA01591@hibernia.dseg.ti.com>
Subject: DECstation 3100
To: linux-mips@fnet.fr
Date: Fri, 24 Oct 1997 19:58:22 -0500 (CDT)
Content-Type: text
Content-Length: 832
Lines: 18

Paul recently forwarded a message to the list from
me about a DECstation 3100 I am willing to give to
anyone that can honestly use it for porting Linux.
I haven't had anyone offer to pay to have the unit
shipped to them (all I am asking for the DS3100 is
shipping; the DS3100 is free).  I need to get this
out of my house soon, and I would really prefer to
find a home for it rather than just placing it for
garbage collection.  The deadline for claiming the
DS3100 is next Wednesday (Oct. 29).

This is the base only, no drives, keyboards, mice,
or monitors.  The unit has 16MB RAM and a MFB SIMM
module.
-- 
Eric Dittman                Raytheon TI Systems - Component Test Facility
dittman@hibernia.dseg.ti.com                               (972) 462-4292
Disclaimer:  Not even my opinions.  I found them by the side of the road.

From dom@algor.co.uk  Sun Oct 26 17:36:58 1997
Received: from embankment.algor.co.uk (0@embankment.algor.co.uk [193.117.190.2]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id RAA23001; Sun, 26 Oct 1997 17:36:56 +0100 (MET)
Received-Date: Sun, 26 Oct 1997 17:36:56 +0100 (MET)
Received: from gladsmuir.algor.co.uk (2041@gladsmuir.algor.co.uk [193.117.190.129])
	by embankment.algor.co.uk (8.8.7/8.8.7) with ESMTP id QAA12766;
	Sun, 26 Oct 1997 16:36:52 GMT
Received: (from dom@localhost) by gladsmuir.algor.co.uk (8.7.3/8.7.3) id QAA00228; Sun, 26 Oct 1997 16:36:48 GMT
Date: Sun, 26 Oct 1997 16:36:48 GMT
From: Dom Sweetman <dom@algor.co.uk>
Message-Id: <199710261636.QAA00228@gladsmuir.algor.co.uk>
To: linux-mips@fnet.fr
Subject: Re: some info please!
In-Reply-To: <34513703.FCC@npi.stpn.soft.net>
References: <34513703.FCC@npi.stpn.soft.net>
Content-Length: 740
Lines: 23


Mrityunjay Kumar (mrityu@npi.stpn.soft.net) writes:

> I am evaluating a toshiba chip which has a MIPS "R3000A based R3900
> Processor Core". I am to find out if we can run Linux on it...

The critical thing is: does it have a TLB (that's memory management
and mapping hardware).  No TLB, no Linux.  Otherwise, the R3900 is an
R3000 superset and will happily run vanilla R3000 code.

Of course you still have to get the right device drivers and stuff.

> Is pSOS better/equal to Linux?

Completely different.  pSOS is a microkernel running threads in a
single address space.  Compared with other real-time OS' it's fairly
well supported, fairly expensive, and doesn't need too much memory.

-- 
Regards,

Dominic Sweetman
Algorithmics Ltd

From Rocky@cnad.dl.nec.com  Fri Oct 31 17:47:17 1997
Received: from telemann.inoc.dl.nec.com (telemann.inoc.dl.nec.com [143.101.112.2]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id RAA07106; Fri, 31 Oct 1997 17:47:15 +0100 (MET)
Received-Date: Fri, 31 Oct 1997 17:47:15 +0100 (MET)
Received: from spitfire.cnad.dl.nec.com (spitfire.cnad.dl.nec.com [143.101.90.2])
	by telemann.inoc.dl.nec.com (8.8.5/8.8.5) with ESMTP id KAA01976
	for <linux-mips@fnet.fr>; Fri, 31 Oct 1997 10:46:59 -0600 (CST)
Received: from saratoga.cnad.dl.nec.com (saratoga.cnad.dl.nec.com [143.101.74.3])
	by spitfire.cnad.dl.nec.com (8.8.7/8.8.5) with ESMTP id KAA06441
	for <linux-mips@fnet.fr>; Fri, 31 Oct 1997 10:46:58 -0600 (CST)
Received: by saratoga.cnad.dl.nec.com with Internet Mail Service (5.0.1458.49)
	id <47TZBA4N>; Fri, 31 Oct 1997 10:46:57 -0600
Message-ID: <95D0F0793CD1D0118AFA00A0C95DC68B014272@saratoga.cnad.dl.nec.com>
From: "Johnson, Rocky" <Rocky@cnad.dl.nec.com>
To: linux-mips@fnet.fr
Subject: NEC Mips support
Date: Fri, 31 Oct 1997 10:46:56 -0600
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1458.49)
Content-Type: text/plain
Content-Length: 399
Lines: 11

To whom it may concern,

I've got 2 NEC RISCServer 2200's catching dust as you say, and I would
like to put Linux on them.  Being from an i386 world I'm not sure I
understand why it can run on a DEC machine, but not on a NEC...  Is it
lack of support or are the processors fundamentally different?  Anyway,
does any port exist for the NEC?  If you have the time let me know.

Thanks

Rocky Johnson	

From imp@village.org  Fri Oct 31 19:50:10 1997
Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with SMTP (8.8.5/97.02.12/Guadalquivir); id TAA07754; Fri, 31 Oct 1997 19:50:08 +0100 (MET)
Received-Date: Fri, 31 Oct 1997 19:50:08 +0100 (MET)
Received: from harmony [10.0.0.6] 
	by rover.village.org with esmtp (Exim 1.71 #1)
	id 0xRM8p-0005Xu-00; Fri, 31 Oct 1997 11:49:55 -0700
Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.7/8.8.3) with ESMTP id LAA10826; Fri, 31 Oct 1997 11:49:45 -0700 (MST)
Message-Id: <199710311849.LAA10826@harmony.village.org>
To: linux-mips@fnet.fr
Cc: "Johnson, Rocky" <Rocky@cnad.dl.nec.com>
Subject: Re: NEC Mips support 
In-reply-to: Your message of "Fri, 31 Oct 1997 10:46:56 CST."
		<95D0F0793CD1D0118AFA00A0C95DC68B014272@saratoga.cnad.dl.nec.com> 
References: <95D0F0793CD1D0118AFA00A0C95DC68B014272@saratoga.cnad.dl.nec.com>  
Date: Fri, 31 Oct 1997 11:49:44 -0700
From: Warner Losh <imp@village.org>
Content-Length: 1154
Lines: 21

In message <95D0F0793CD1D0118AFA00A0C95DC68B014272@saratoga.cnad.dl.nec.com> "Johnson, Rocky" writes:
: I've got 2 NEC RISCServer 2200's catching dust as you say, and I would
: like to put Linux on them.  Being from an i386 world I'm not sure I
: understand why it can run on a DEC machine, but not on a NEC...  Is it
: lack of support or are the processors fundamentally different?  Anyway,
: does any port exist for the NEC?  If you have the time let me know.

The NEC would likely be easy to support, if there was adequate
documenation on the hardware.  There will be some hacking needed to
MILO to get it to recognize things, as well as some minor (and not so
minor maybe) hacking to the kernel to add support for the chipsets
around the NEC board.  If my memory from past posts is accurate, these
machines are little more than the Microsoft JAZZ with a couple of
interesting twists.  They have R4400's inside of them and are
basically supported hardware, modulo a couple of things that are
escaping my memory at the moment.

Since none of the expert kernel folks have access to the NEC boxes,
they have remained unsupported for a long time.

Warner

From ralf@informatik.uni-koblenz.de  Fri Oct 31 20:29:38 1997
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.5/97.02.12/Guadalquivir); id UAA08031; Fri, 31 Oct 1997 20:29:37 +0100 (MET)
Received-Date: Fri, 31 Oct 1997 20:29:37 +0100 (MET)
Received: from thoma (ralf@thoma.uni-koblenz.de [141.26.4.61]) by informatik.uni-koblenz.de (8.8.7/8.6.9) with SMTP id UAA08466 for <linux-mips@fnet.fr>; Fri, 31 Oct 1997 20:29:35 +0100 (MET)
Received: by thoma (SMI-8.6/KO-2.0)
	id UAA08000; Fri, 31 Oct 1997 20:29:35 +0100
Message-ID: <19971031202934.63579@thoma.uni-koblenz.de>
Date: Fri, 31 Oct 1997 20:29:34 +0100
From: Ralf Baechle <ralf@informatik.uni-koblenz.de>
To: linux-mips@fnet.fr
Subject: Re: NEC Mips support
References: <95D0F0793CD1D0118AFA00A0C95DC68B014272@saratoga.cnad.dl.nec.com> <199710311849.LAA10826@harmony.village.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84e
In-Reply-To: <199710311849.LAA10826@harmony.village.org>; from Warner Losh on Fri, Oct 31, 1997 at 11:49:44AM -0700
Content-Length: 354
Lines: 10

On Fri, Oct 31, 1997 at 11:49:44AM -0700, Warner Losh wrote:
> 
> The NEC would likely be easy to support, if there was adequate
> documenation on the hardware.  There will be some hacking needed to
> MILO to get it to recognize things, as well as some minor (and not so
> minor maybe) hacking to the kernel to add support for the chipsets

SMP.

  Ralf