From ab@ivm.net  Sun Aug  2 15:32:21 1998
Received: from aw.ivm.net (root@mail.ivm.net [195.78.161.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id PAA15270; Sun, 2 Aug 1998 15:32:20 +0200 (MET DST)
Received-Date: Sun, 2 Aug 1998 15:32:20 +0200 (MET DST)
Received: from newton (newton.office.aw.ivm.net [195.247.227.132])
	by aw.ivm.net (8.8.8/8.8.8-ivm) with SMTP id PAA20842
	for <linux-mips@fnet.fr>; Sun, 2 Aug 1998 15:32:15 +0200
Date: Sun, 2 Aug 1998 15:34:27 +0200 (MET DST)
From: Andreas Busse <ab@ivm.net>
X-Sender: ab@newton
To: linux-mips@fnet.fr
Subject: mips stuff - box going to be available (fwd)
Message-ID: <Pine.LNX.3.91.980802153327.19241U-100000-100000@newton>
X-NCC-RegID: de.ivm
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1055
Lines: 34


Hi all,

could please someone help this guy -- if possible?

Thanks,
Andy

--

IVM Gesellschaft fuer Internet, Vernetzung und Mehrwertdienste mbH
    Zissener Strasse 8 - D-53498 Waldorf - Fon 02636-9769-0
    Fax 02636-9769-999 - http://www.ivm.net/ - info@ivm.net
  Internet Services & Consulting im Grossraum Bonn/Aachen/Koblenz

---------- Forwarded message ----------
Date: Tue, 28 Jul 1998 13:20:43 -0000
From: Drew Mouton <drew@etool.com>
To: andy@waldorf-gmbh.de
Subject: mips stuff - box going to be available

Hi Andy,

It doesn't appear as though the Linux/Mips port has moved forward much 
lately, but fwiw I have an Nec RiscServer 2200 that I'm about to take out 
of primary service (in a few weeks) and a RiscStation 2200 that's more or 
less available for testing. Since the faqs all say "Sure, you can help! 
If you have a Mips box, please let us know," I guess I'm letting you know.

I can't tell you how stoked I'd be if we could stick Linux on this box. 
I'd put it back in prime service as soon as it was stable.

Cheers,
Drew Mouton

From mota@bocal.cs.univ-paris8.fr  Tue Aug  4 20:36:41 1998
Received: from inferno.cs.univ-paris8.fr (inferno.cs.univ-paris8.fr [193.54.152.10]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id UAA03265; Tue, 4 Aug 1998 20:36:40 +0200 (MET DST)
Received-Date: Tue, 4 Aug 1998 20:36:40 +0200 (MET DST)
Received: from neptune.bocal.cs.univ-paris8.fr (neptune.bocal.cs.univ-paris8.fr [192.168.3.2]) by inferno.cs.univ-paris8.fr (8.8.7/8.7.3) with ESMTP id UAA28654 for <linux-mips@fnet.fr>; Tue, 4 Aug 1998 20:39:16 +0200 (CEST)
Received: from aqua.bocal.cs.univ-paris8.fr (aqua.bocal.cs.univ-paris8.fr [192.168.3.3])
	by neptune.bocal.cs.univ-paris8.fr (8.8.8/8.8.8) with ESMTP id UAA13682
	for <linux-mips@fnet.fr>; Tue, 4 Aug 1998 20:39:15 +0200 (MET DST)
Received: from aqua.bocal.cs.univ-paris8.fr (localhost [127.0.0.1])
	by aqua.bocal.cs.univ-paris8.fr (8.8.8/8.8.8) with SMTP id TAA07674
	for <linux-mips@fnet.fr>; Tue, 4 Aug 1998 19:39:15 +0100 (WET DST)
Sender: mota@bocal.cs.univ-paris8.fr
Message-ID: <35C75552.2DEA@bocal.cs.univ-paris8.fr>
Date: Tue, 04 Aug 1998 19:39:14 +0100
From: Paul MARQUES MOTA <mota@bocal.cs.univ-paris8.fr>
X-Mailer: Mozilla 3.04Gold (X11; I; SunOS 5.6 sun4u)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: I'd like to subscribe
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 349
Lines: 10

Hello

We have a Siemens Targon 420 with a mips R3000 processor and i'd like
to be added to this list.

-- 
                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                       Paul Marques Mota - comte0@mygale.org
                         http://www.mygale.org/04/comte0/
                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

From alhaz@xmission.com  Wed Aug  5 20:26:04 1998
Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id UAA12168; Wed, 5 Aug 1998 20:26:02 +0200 (MET DST)
Received-Date: Wed, 5 Aug 1998 20:26:02 +0200 (MET DST)
Received: from alhaz.users.xmission.com (xmission.com) [207.135.128.199] (alhaz)
	by mail.xmission.com with esmtp (Exim 1.82 #2)
	id 0z48G4-0000UX-00; Wed, 5 Aug 1998 12:25:57 -0600
Sender: alhaz@fnet.fr
Message-ID: <35C84E30.D98A4662@xmission.com>
Date: Wed, 05 Aug 1998 06:21:04 -0600
From: Eric Jorgensen <alhaz@xmission.com>
X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.32 i486)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: current status of support for MIPS Magnum 4000PC? 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 730
Lines: 15

    I've been following the Linux/MIPS effort for some time now,
occasionally returning to the web page, and it's unclear how much
I could do with linux on this particular machine.

    I have one complete with high-rez frame buffer and sound card. I'm
wondering if the status of the port is still such that I would need to
install an ISA IDE controller and ISA network board to use it? Has work
begun on driver support for the integrated peripherals? Lance ethernet
and NCR scsi seem like they ought to be fairly simple to implement.

    I'm sorry if I'm off-base here, it's just that I've had the beast
for some time now, and I'm having a hard time deciding what to do with
it. I'm not interested in running NT on it.

 - Eric

From ralf@uni-koblenz.de  Wed Aug  5 19:56:48 1998
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA11890; Wed, 5 Aug 1998 19:56:47 +0200 (MET DST)
Received-Date: Wed, 5 Aug 1998 19:56:47 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from uni-koblenz.de (pmport-28.uni-koblenz.de [141.26.249.28])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id TAA03823
	for <linux-mips@fnet.fr>; Wed, 5 Aug 1998 19:56:43 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id SAA01057;
	Wed, 5 Aug 1998 18:54:34 +0200
Message-ID: <19980805185434.G386@uni-koblenz.de>
Date: Wed, 5 Aug 1998 18:54:34 +0200
To: linux@engr.sgi.com, linux-mips@fnet.fr
Subject: N32 kernel
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
Content-Length: 278
Lines: 6

FYI, I managed to build the first using the n32 ABI.  It doesn't work
yet perfectly but running n32 will give us the full power of all 64 bits
in the register without the bloat of the 64 bit address space.  Probably
currently the best choice for the supported machines.

  Ralf

From imp@village.org  Thu Aug  6 18:24:52 1998
Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id SAA20603; Thu, 6 Aug 1998 18:24:49 +0200 (MET DST)
Received-Date: Thu, 6 Aug 1998 18:24:49 +0200 (MET DST)
Received: from harmony [10.0.0.6] 
	by rover.village.org with esmtp (Exim 1.71 #1)
	id 0z4SqM-0000Sb-00; Thu, 6 Aug 1998 10:24:46 -0600
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id KAA15964 for <linux-mips@fnet.fr>; Thu, 6 Aug 1998 10:25:06 -0600 (MDT)
Message-Id: <199808061625.KAA15964@harmony.village.org>
To: linux-mips@fnet.fr
Subject: Re: MIPS R4000 Compaq Handheld CE 
In-reply-to: Your message of "Thu, 06 Aug 1998 18:17:21 BST."
		<41256658.005DE31B.00@mail.iss.dk> 
References: <41256658.005DE31B.00@mail.iss.dk>  
Date: Thu, 06 Aug 1998 10:25:06 -0600
From: Warner Losh <imp@village.org>
Content-Length: 827
Lines: 23

In message <41256658.005DE31B.00@mail.iss.dk> chlor@iss-group.com writes:
: I think of buying a Compaq 2010c
: http://www.compaq.com/products/handhelds/2010/index.html
: 
: It has a build in MIPS R4000, no disk, up to 32MB RAM,
: IrDa, RS-232, 1 pcmcia, 10MB ROM (software upgradeable).
: 
: Do you think it would be possible to run Linux on this?
: 
: With a pcmcia netcard it would be a nice little
: network analyzer :-)

The MIPS chip that it seems to be built around is the Vr4111.  This
chip isn't supported in the current Linux software.

The hard part is getting Linux loaded....  Or at least a bot loader
that groks how to upgrade the kernel.

I've looked into doing something similar with the palmtop sized
machines.  Someone even offered to send me one to do the port, but
that offer seems to have dried up.

Warner

From chlor@iss-group.com  Thu Aug  6 18:16:43 1998
Received: from ns.uni2.dk (ns.uni2.dk [129.142.7.100]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA20519; Thu, 6 Aug 1998 18:16:38 +0200 (MET DST)
Received-Date: Thu, 6 Aug 1998 18:16:38 +0200 (MET DST)
From: chlor@iss-group.com
Received: from mail.iss.dk (mail.iss.dk [129.142.93.178]) by ns.uni2.dk (8.9.0/8.6) with SMTP id SAA08497 for <linux-mips@fnet.fr>; Thu, 6 Aug 1998 18:16:36 +0200 (MET DST)
Received: by mail.iss.dk(Lotus SMTP MTA v1.1 (385.6 5-6-1997))  id 41256658.005EE1C4 ; Thu, 6 Aug 1998 18:16:21 +0100
X-Lotus-FromDomain: ISS@ISSHQ
To: linux-mips@fnet.fr
Message-ID: <41256658.005DE31B.00@mail.iss.dk>
Date: Thu, 6 Aug 1998 18:17:21 +0100
Subject: MIPS R4000 Compaq Handheld CE
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Length: 380
Lines: 18



hi Ralf (?)

I think of buying a Compaq 2010c
http://www.compaq.com/products/handhelds/2010/index.html

It has a build in MIPS R4000, no disk, up to 32MB RAM,
IrDa, RS-232, 1 pcmcia, 10MB ROM (software upgradeable).

Do you think it would be possible to run Linux on this?

With a pcmcia netcard it would be a nice little
network analyzer :-)

best regards
Hans Schou, Denmark


From tsbogend@alpha.franken.de  Sat Aug  8 01:51:21 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id BAA02464; Sat, 8 Aug 1998 01:51:21 +0200 (MET DST)
Received-Date: Sat, 8 Aug 1998 01:51:21 +0200 (MET DST)
Received: from alpha.franken.de (tsbogend@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id BAA06213; Sat, 8 Aug 1998 01:51:15 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id BAA03502;
	Sat, 8 Aug 1998 01:47:40 +0200
Message-ID: <19980808014740.56097@alpha.franken.de>
Date: Sat, 8 Aug 1998 01:47:40 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@fnet.fr
Cc: alhaz@xmission.com
Subject: Re: current status of support for MIPS Magnum 4000PC?
References: <35C84E30.D98A4662@xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
In-Reply-To: <35C84E30.D98A4662@xmission.com>; from Eric Jorgensen on Wed, Aug 05, 1998 at 06:21:04AM -0600
Content-Length: 1188
Lines: 23

On Wed, Aug 05, 1998 at 06:21:04AM -0600, Eric Jorgensen wrote:
>     I have one complete with high-rez frame buffer and sound card. I'm
> wondering if the status of the port is still such that I would need to
> install an ISA IDE controller and ISA network board to use it? Has work
> begun on driver support for the integrated peripherals? Lance ethernet
> and NCR scsi seem like they ought to be fairly simple to implement.

You better use the ISA network card, but you can dump the IDE controller.
I've also written a driver for the onboard ethernet, which is based on
a NatSemi sonic chip (no lance), but it isn't stable under more than 
light load. Sound support is still on my todo list. X is up and running
(which isn't a big deal, as the g364 is just a dumb framebuffer).

I've compiled more than half of the RedHat src.rpms and I'm now stuck,
because of egcs/ld/libstdc++ problems. After solving this, there should
be a little endian HardHat (or however it will be called) RSN.

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From mtidwell@mail.com  Sun Aug  9 07:05:18 1998
Received: from pop01.globecomm.net (pop01.globecomm.net [206.253.129.185]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id HAA11649; Sun, 9 Aug 1998 07:05:17 +0200 (MET DST)
Received-Date: Sun, 9 Aug 1998 07:05:17 +0200 (MET DST)
Received: from mail.com (dial170.magiclink.net [207.5.59.170]) by pop01.globecomm.net (8.9.0/8.8.0) with ESMTP id BAA08127 for <linux-mips@fnet.fr>; Sun, 9 Aug 1998 01:04:52 -0400 (EDT)
Message-ID: <35CD2CFC.32CACC90@mail.com>
Date: Sat, 08 Aug 1998 22:00:44 -0700
From: "montgomery f. tidwell" <mtidwell@mail.com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: Linux on MIPS RC3230
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 165
Lines: 9

Howdy,

what is the status of a Linux port to the RC3230?

other than donating my computer (a RC3230), is there anyway that i can
help?


                     \\//_

From tsbogend@alpha.franken.de  Sun Aug  9 15:36:02 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id PAA14179; Sun, 9 Aug 1998 15:36:01 +0200 (MET DST)
Received-Date: Sun, 9 Aug 1998 15:36:01 +0200 (MET DST)
Received: from alpha.franken.de (tsbogend@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id PAA10598; Sun, 9 Aug 1998 15:35:55 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id PAA01603;
	Sun, 9 Aug 1998 15:27:15 +0200
Message-ID: <19980809152715.19085@alpha.franken.de>
Date: Sun, 9 Aug 1998 15:27:15 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: binutils 2.9.1.0.4 considered harmful
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
Content-Length: 1182
Lines: 36

Hi,

look what gas from binutils-2.9.1.0.4 produces, when building _eh.o
(libgcc.a).

RELOCATION RECORDS FOR [.eh_frame]:
OFFSET   TYPE              VALUE 
0000001c R_MIPS_32         .text
00000038 R_MIPS_32         .text
00000054 R_MIPS_32         .text
00000074 R_MIPS_32         .text
00000084 R_MIPS_32         .text
00000094 R_MIPS_32         .text
000000e4 R_MIPS_32         .text
00000134 R_MIPS_32         .text
00000144 R_MIPS_32         .text
00000160 R_MIPS_32         .text
0000017c R_MIPS_32         .text
00000198 R_MIPS_32         .text

000001b5 R_MIPS_32         .text
     ^^^

This bug is most likely responsible for my problems with libstdc++ on
my little endian box (SIGBUS in ld.so.1, when a program is linked against
libstc++). On the Indy I've build egcs with patched binutils 2.8.1 and there 
libstdc++ works, while on my Olli it doesn't (build with binutils 2.9.1.0.4).
Right now I'm rebuilding egcs to see, whether all of my libcstdc++ problems
are gone.

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From ralf@uni-koblenz.de  Mon Aug 10 03:12:40 1998
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id DAA19009; Mon, 10 Aug 1998 03:12:39 +0200 (MET DST)
Received-Date: Mon, 10 Aug 1998 03:12:39 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from uni-koblenz.de (pmport-21.uni-koblenz.de [141.26.249.21])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id DAA04918
	for <linux-mips@fnet.fr>; Mon, 10 Aug 1998 03:12:37 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id RAA07862;
	Sun, 9 Aug 1998 17:13:12 +0200
Message-ID: <19980809171312.U938@uni-koblenz.de>
Date: Sun, 9 Aug 1998 17:13:12 +0200
To: "montgomery f. tidwell" <mtidwell@mail.com>, linux-mips@fnet.fr
Subject: Re: Linux on MIPS RC3230
References: <35CD2CFC.32CACC90@mail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <35CD2CFC.32CACC90@mail.com>; from montgomery f. tidwell on Sat, Aug 08, 1998 at 10:00:44PM -0700
Content-Length: 248
Lines: 10

On Sat, Aug 08, 1998 at 10:00:44PM -0700, montgomery f. tidwell wrote:

> what is the status of a Linux port to the RC3230?
> 
> other than donating my computer (a RC3230), is there anyway that i can
> help?

I'm working on it, stay tuned.

  Ralf

From alhaz@xmission.com  Mon Aug 10 03:20:29 1998
Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id DAA19134; Mon, 10 Aug 1998 03:20:27 +0200 (MET DST)
Received-Date: Mon, 10 Aug 1998 03:20:27 +0200 (MET DST)
Received: from alhaz.users.xmission.com (xmission.com) [207.135.128.199] (alhaz)
	by mail.xmission.com with esmtp (Exim 1.82 #2)
	id 0z5gdH-0003Wx-00; Sun, 9 Aug 1998 19:20:19 -0600
Sender: alhaz@fnet.fr
Message-ID: <35CDF5FF.C2AC335F@xmission.com>
Date: Sun, 09 Aug 1998 13:18:23 -0600
From: Eric Jorgensen <alhaz@xmission.com>
X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.32 i486)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: Re: Linux on MIPS RC3230
References: <35CD2CFC.32CACC90@mail.com> <19980809171312.U938@uni-koblenz.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 402
Lines: 15

ralf@uni-koblenz.de wrote:

> On Sat, Aug 08, 1998 at 10:00:44PM -0700, montgomery f. tidwell wrote:
>
> > what is the status of a Linux port to the RC3230?
> >
> > other than donating my computer (a RC3230), is there anyway that i can
> > help?
>
> I'm working on it, stay tuned.

    Any chance this will port easily to other r3000 boxes? I have an RC3240
and RS2030 not doing a damn thing.

 - Eric

From alhaz@xmission.com  Mon Aug 10 03:34:05 1998
Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id DAA19207; Mon, 10 Aug 1998 03:34:03 +0200 (MET DST)
Received-Date: Mon, 10 Aug 1998 03:34:03 +0200 (MET DST)
Received: from alhaz.users.xmission.com (xmission.com) [207.135.128.199] (alhaz)
	by mail.xmission.com with esmtp (Exim 1.82 #2)
	id 0z5gqW-0004fn-00; Sun, 9 Aug 1998 19:34:01 -0600
Sender: alhaz@fnet.fr
Message-ID: <35CDF934.293BB67@xmission.com>
Date: Sun, 09 Aug 1998 13:32:04 -0600
From: Eric Jorgensen <alhaz@xmission.com>
X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.32 i486)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: ISA audio in Magnum 4000pc,possibly? 
References: <35CD2CFC.32CACC90@mail.com> <19980809171312.U938@uni-koblenz.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 1072
Lines: 22

    I have a MIPS Magnum 4000PC-50 I'm working up to installing linux on.
I've got a few things left to work out, like a monitor.

    Anyway, I'm aware that support for the audio board in my Magnum is
still on the to-do list, so, I'm wondering if I could get away with
installing an ISA sound board in the box - is this at all possible? or is
audio in general still not quite here? I also use linux on some Sparc
systems, and audio has been slow to materialize on those boxes, so
I understand if it just isn't possible yet.

    It just seemed like the box might make an outstanding MP3 server.

    On a completely unrelated note - out of curiosity I pulled the heatsink
off the cpu in my system - Never seen a mips 4k processor before. Anyway, I
was surprised to find the word "PROTOTYPE" emblazoned acrost the chip. Is
this common? Or do I have something really cool/funky here? if anybody
wants to see, I have a digital camera here.

    Thanks much - non-coder types such as myself owe the linux dev.
community a lot of gratitude and probably a few favors.

 - Eric

From harald.koerfgen@netcologne.de  Wed Aug 12 13:17:49 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id NAA02745; Wed, 12 Aug 1998 13:17:46 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 13:17:46 +0200 (MET DST)
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id UAA15982; Mon, 10 Aug 1998 20:43:45 +0200 (MET DST)
Received: from franz.no.dom (dial10-19.netcologne.de [195.14.235.19])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id UAA28143
	for <linux-mips@fnet.fr>; Mon, 10 Aug 1998 20:40:08 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980810204120.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <35CDF5FF.C2AC335F@xmission.com>
Date: Mon, 10 Aug 1998 20:41:20 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: Re: Linux on MIPS RC3230
Content-Length: 836
Lines: 29

Hi all,

I'm back, alive and kicking.

On 09-Aug-98 Eric Jorgensen wrote:
> ralf@uni-koblenz.de wrote:
> 
>> On Sat, Aug 08, 1998 at 10:00:44PM -0700, montgomery f. tidwell wrote:
>>
>> > what is the status of a Linux port to the RC3230?
>> >
>> > other than donating my computer (a RC3230), is there anyway that i can
>> > help?
>>
>> I'm working on it, stay tuned.
> 
>     Any chance this will port easily to other r3000 boxes? I have an RC3240
> and RS2030 not doing a damn thing.

You should be able to use the DECstation-Linux source tree as a starting point.
The R3000 support seems to work pretty well, at least the first user process is
running. You may want to have a look at http://decstation.unix-ag.org.

BTW, I have sent the DECstation patches to Ralf as a request for discussion.
Any comments, Ralf?

---
Regards,
Harald

From tsbogend@alpha.franken.de  Wed Aug 12 13:15:00 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id NAA02554; Wed, 12 Aug 1998 13:14:56 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 13:14:56 +0200 (MET DST)
Received: from alpha.franken.de (tsbogend@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id AAA17355; Tue, 11 Aug 1998 00:42:58 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id AAA03812;
	Tue, 11 Aug 1998 00:40:28 +0200
Message-ID: <19980811004027.65074@alpha.franken.de>
Date: Tue, 11 Aug 1998 00:40:27 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@fnet.fr
Subject: Re: ISA audio in Magnum 4000pc,possibly?
References: <35CD2CFC.32CACC90@mail.com> <19980809171312.U938@uni-koblenz.de> <35CDF934.293BB67@xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
In-Reply-To: <35CDF934.293BB67@xmission.com>; from Eric Jorgensen on Sun, Aug 09, 1998 at 01:32:04PM -0600
Content-Length: 1363
Lines: 30

On Sun, Aug 09, 1998 at 01:32:04PM -0600, Eric Jorgensen wrote:
>     Anyway, I'm aware that support for the audio board in my Magnum is
> still on the to-do list, so, I'm wondering if I could get away with
> installing an ISA sound board in the box - is this at all possible? 

installing yes, but all DMA based functions will not work. To get DMA
working the driver needs to program the virtual DMA engine of the Magnum
and handle cache flushes. This isn't needed for Intel, so the ISA
sounddriver don't do this. 

> or is audio in general still not quite here? 

I've never looked at the ISA sound support. I had a quick look over
the spec of the Magnum sound board (I hope, that's the same one, which
is built in on my M700 mainboard) and pulled together all the needed
datasheets. But there is still more important stuff to do, than sound.

>     On a completely unrelated note - out of curiosity I pulled the heatsink
> off the cpu in my system - Never seen a mips 4k processor before. Anyway, I
> was surprised to find the word "PROTOTYPE" emblazoned acrost the chip. Is
> this common? 

I haven't look at my processor. Maybe next time when I open my box.

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From ralf@uni-koblenz.de  Wed Aug 12 13:07:37 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id NAA01674; Wed, 12 Aug 1998 13:07:36 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 13:07:36 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id CAA22870; Wed, 12 Aug 1998 02:26:04 +0200 (MET DST)
Received: from uni-koblenz.de (pmport-18.uni-koblenz.de [141.26.249.18])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id CAA20023
	for <linux-mips@fnet.fr>; Wed, 12 Aug 1998 02:24:48 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id MAA00485;
	Tue, 11 Aug 1998 12:36:15 +0200
Message-ID: <19980811123615.A480@uni-koblenz.de>
Date: Tue, 11 Aug 1998 12:36:15 +0200
To: Eric Jorgensen <alhaz@xmission.com>, linux-mips@fnet.fr
Subject: Re: Linux on MIPS RC3230
References: <35CD2CFC.32CACC90@mail.com> <19980809171312.U938@uni-koblenz.de> <35CDF5FF.C2AC335F@xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <35CDF5FF.C2AC335F@xmission.com>; from Eric Jorgensen on Sun, Aug 09, 1998 at 01:18:23PM -0600
Content-Length: 691
Lines: 21

On Sun, Aug 09, 1998 at 01:18:23PM -0600, Eric Jorgensen wrote:

> ralf@uni-koblenz.de wrote:
> 
> > On Sat, Aug 08, 1998 at 10:00:44PM -0700, montgomery f. tidwell wrote:
> >
> > > what is the status of a Linux port to the RC3230?
> > >
> > > other than donating my computer (a RC3230), is there anyway that i can
> > > help?
> >
> > I'm working on it, stay tuned.
> 
>     Any chance this will port easily to other r3000 boxes? I have an RC3240
> and RS2030 not doing a damn thing.

I'll have to research the differences between these machines, I've got no
idea how similar / different they are.  Whatever, I should have tackled the
larger portability issues with the RS3230 port.

  Ralf

From ralf@uni-koblenz.de  Wed Aug 12 13:07:47 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id NAA01732; Wed, 12 Aug 1998 13:07:45 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 13:07:45 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id CAA22856; Wed, 12 Aug 1998 02:25:52 +0200 (MET DST)
Received: from uni-koblenz.de (pmport-18.uni-koblenz.de [141.26.249.18])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id CAA20007
	for <linux-mips@fnet.fr>; Wed, 12 Aug 1998 02:24:35 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id NAA00527;
	Tue, 11 Aug 1998 13:11:22 +0200
Message-ID: <19980811131122.B480@uni-koblenz.de>
Date: Tue, 11 Aug 1998 13:11:22 +0200
To: Eric Jorgensen <alhaz@xmission.com>, linux-mips@fnet.fr
Subject: Re: ISA audio in Magnum 4000pc,possibly?
References: <35CD2CFC.32CACC90@mail.com> <19980809171312.U938@uni-koblenz.de> <35CDF934.293BB67@xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <35CDF934.293BB67@xmission.com>; from Eric Jorgensen on Sun, Aug 09, 1998 at 01:32:04PM -0600
Content-Length: 1748
Lines: 39

On Sun, Aug 09, 1998 at 01:32:04PM -0600, Eric Jorgensen wrote:

>     I have a MIPS Magnum 4000PC-50 I'm working up to installing linux on.
> I've got a few things left to work out, like a monitor.
> 
>     Anyway, I'm aware that support for the audio board in my Magnum is
> still on the to-do list, so, I'm wondering if I could get away with
> installing an ISA sound board in the box - is this at all possible? or is
> audio in general still not quite here? I also use linux on some Sparc
> systems, and audio has been slow to materialize on those boxes, so
> I understand if it just isn't possible yet.

All drivers that use DMA need modifications for MIPS systems, so most, if
not all of the ISA/EISA drivers should currently not usable.

The PC speaker driver should probably work ;-)

>     It just seemed like the box might make an outstanding MP3 server.

The machine will definately make a nice job in that.  People have already
reported to me that they're quite satisfied with the Magnum's performance
for mp3 encoding as well.  (I wonder what software they use or is there
already a free mp3 encoder available as source?)

>     On a completely unrelated note - out of curiosity I pulled the heatsink
> off the cpu in my system - Never seen a mips 4k processor before. Anyway, I
> was surprised to find the word "PROTOTYPE" emblazoned acrost the chip. Is
> this common? Or do I have something really cool/funky here? if anybody
> wants to see, I have a digital camera here.

I've never seen a processor like that before.  The only thing I bet on is
that this processor is buggy like shit.

>     Thanks much - non-coder types such as myself owe the linux dev.
> community a lot of gratitude and probably a few favors.

Thanks!

  Ralf

From ralf@uni-koblenz.de  Wed Aug 12 13:07:36 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id NAA01666; Wed, 12 Aug 1998 13:07:35 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 13:07:35 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id CAA22866; Wed, 12 Aug 1998 02:26:01 +0200 (MET DST)
Received: from uni-koblenz.de (pmport-18.uni-koblenz.de [141.26.249.18])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id CAA20017
	for <linux-mips@fnet.fr>; Wed, 12 Aug 1998 02:24:45 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id NAA00533;
	Tue, 11 Aug 1998 13:14:58 +0200
Message-ID: <19980811131458.C480@uni-koblenz.de>
Date: Tue, 11 Aug 1998 13:14:58 +0200
To: Eric Jorgensen <alhaz@xmission.com>, linux-mips@fnet.fr,
        linux@engr.sgi.com
Subject: R4000 PROTOTYPE
References: <35CD2CFC.32CACC90@mail.com> <19980809171312.U938@uni-koblenz.de> <35CDF934.293BB67@xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <35CDF934.293BB67@xmission.com>; from Eric Jorgensen on Sun, Aug 09, 1998 at 01:32:04PM -0600
Content-Length: 598
Lines: 15

On Sun, Aug 09, 1998 at 01:32:04PM -0600, Eric Jorgensen wrote:

>     On a completely unrelated note - out of curiosity I pulled the heatsink
> off the cpu in my system - Never seen a mips 4k processor before. Anyway, I
> was surprised to find the word "PROTOTYPE" emblazoned acrost the chip. Is
> this common? Or do I have something really cool/funky here? if anybody
> wants to see, I have a digital camera here.

Maybe some long time MIPSer can tell something about this chip?  Is this
the CPU version which identifies itself as version 2.2 which is the oldest
I've ever seen?

Thanks,

  Ralf

From alhaz@xmission.com  Wed Aug 12 13:07:34 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id NAA01661; Wed, 12 Aug 1998 13:07:33 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 13:07:33 +0200 (MET DST)
Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by louis-blanc.univ-evry.fr with SMTP (8.8.8/980318/louis-blanc); id CAA23000; Wed, 12 Aug 1998 02:50:10 +0200 (MET DST)
Received: from alhaz.users.xmission.com (xmission.com) [207.135.128.199] (alhaz)
	by mail.xmission.com with esmtp (Exim 1.82 #2)
	id 0z6P3m-0002Rt-00; Tue, 11 Aug 1998 18:46:39 -0600
Sender: alhaz@univ-evry.fr
Message-ID: <35D09103.DB8B8DA3@xmission.com>
Date: Tue, 11 Aug 1998 12:44:19 -0600
From: Eric Jorgensen <alhaz@xmission.com>
X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.32 i486)
MIME-Version: 1.0
To: ralf@uni-koblenz.de, linux-mips@fnet.fr
Subject: Re: ISA audio in Magnum 4000pc,possibly?
References: <35CD2CFC.32CACC90@mail.com> <19980809171312.U938@uni-koblenz.de> <35CDF934.293BB67@xmission.com> <19980811131122.B480@uni-koblenz.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 3136
Lines: 61

ralf@uni-koblenz.de wrote:

> >     It just seemed like the box might make an outstanding MP3 server.
>
> The machine will definately make a nice job in that.  People have already
> reported to me that they're quite satisfied with the Magnum's performance
> for mp3 encoding as well.  (I wonder what software they use or is there
> already a free mp3 encoder available as source?)

    Yeah. I've used an OS/2 binary compiled from it. I didn't think it was very
good, but the guy who did the port didn't know what he was doing.  It was slower
on a P133 than the linux binary for l3enc was on my DX4-100.. And it distorted
some things that l3enc didn't.

> >     On a completely unrelated note - out of curiosity I pulled the heatsink
> > off the cpu in my system - Never seen a mips 4k processor before. Anyway, I
> > was surprised to find the word "PROTOTYPE" emblazoned acrost the chip. Is
> > this common? Or do I have something really cool/funky here? if anybody
> > wants to see, I have a digital camera here.
>
> I've never seen a processor like that before.  The only thing I bet on is
> that this processor is buggy like shit.

    Well, it has what I believe is a Fujitsu logo (has that curly S thing on it
that was used as an F centuries ago, if you look at old documents like the
US constitution) and it identifies itself as (unless I'm remembering wrong) a
76R4000PC-50G - there is also a letter G hand-written in pencil on the corner of
the ceramic, and two other places on the ceramic where it looks like things have
been scribbled over.

    Possibly this is an early low-power version?

    The thing is, there's no way this was a pre-release prototype of the
original magnum, because the original magnum was Microsoft-designed box
code-named Jazz. I actually have the whole story from the horses mouth (Atleast,
a guy who was at mips during the fiasco) of how Mips was falling behind on their
own design, and ended up buying the design that Microsoft had built to Dave
Cutler's specs. So, since the board has Mips logos all over it, it's clearly not
first-run, tho it could be something from the transitional period after MIPS
bought the design from microsoft.

    On the other hand, only the processor says "prototoype" on it.

    I don't know much about where this box came from. I bought it as a surplus
item from a local university. Word has it that a professor retired and nobody
wanted his computers, so they stripped them for memory and storage devices, kept
the monitors, and surplused the rest. I bought my Magnum for $5 USD, including
the high-rez frame buffer and sound card. I also bought his old fileserver -
DELL 4066/XE - a 486 but it's the size of a doghouse. Cost me $10.

    I've actually never successfully booted it, still building a video cable to
let it hook up to a Sun monitor that should support it's rez/refresh but has
different wiring and possibly composite sync.

    So maybe after everything else stablizes it won't be too hard to adjust a
linux/i386 driver won't be too hard to adjust.

    One question - is there an ECU disk to configure EISA devices or is it in
firmware?

 - Eric

From alhaz@xmission.com  Wed Aug 12 13:05:22 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id NAA01350; Wed, 12 Aug 1998 13:05:19 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 13:05:19 +0200 (MET DST)
Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by louis-blanc.univ-evry.fr with SMTP (8.8.8/980318/louis-blanc); id GAA23743; Wed, 12 Aug 1998 06:32:51 +0200 (MET DST)
Received: from alhaz.users.xmission.com (xmission.com) [207.135.128.199] (alhaz)
	by mail.xmission.com with esmtp (Exim 1.82 #2)
	id 0z6SXR-0001dj-00; Tue, 11 Aug 1998 22:29:30 -0600
Sender: alhaz@univ-evry.fr
Message-ID: <35D0C53C.4B7F3D57@xmission.com>
Date: Tue, 11 Aug 1998 16:27:08 -0600
From: Eric Jorgensen <alhaz@xmission.com>
X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.32 i486)
MIME-Version: 1.0
To: "Steven G. Parker" <sparker@taz.cs.utah.edu>, linux-mips@fnet.fr
Subject: Re: R4000 PROTOTYPE
References: <35CD2CFC.32CACC90@mail.com>  <19980809171312.U938@uni-koblenz.de> 
		<35CDF934.293BB67@xmission.com> 
		<19980811131458.C480@uni-koblenz.de> <9808112032.ZM232940@taz.cs.utah.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 1179
Lines: 30

Steven G. Parker wrote:

> We have an Indy (one of the earlier) that identifies itself as version 2.2.
> I've never pulled the heat sink off though...

    I've never booted this box, so i'm not sure what revision it is. If anybody
wants accurate chip numbers I can pull the heatsink off again and check. If i had
a tool to extract the chip without destroying the flimsy cage thingy the heatsink
attaches to I could throw it on my flatbed scanner and let everybody have a
looksee. I've got a digital camera too, but the picture is fuzzy.

 - Eric


> > >     On a completely unrelated note - out of curiosity I pulled the heatsink
> > > off the cpu in my system - Never seen a mips 4k processor before. Anyway, I
> > > was surprised to find the word "PROTOTYPE" emblazoned acrost the chip. Is
> > > this common? Or do I have something really cool/funky here? if anybody
> > > wants to see, I have a digital camera here.
> >
> > Maybe some long time MIPSer can tell something about this chip?  Is this
> > the CPU version which identifies itself as version 2.2 which is the oldest
> > I've ever seen?
> >
> > Thanks,
> >
> >   Ralf
> >-- End of excerpt from ralf@uni-koblenz.de



From sparker@taz.cs.utah.edu  Wed Aug 12 13:06:49 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id NAA01485; Wed, 12 Aug 1998 13:06:45 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 13:06:45 +0200 (MET DST)
Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id EAA23387; Wed, 12 Aug 1998 04:36:06 +0200 (MET DST)
Received: from taz.cs.utah.edu (taz.cs.utah.edu [155.99.203.51])
	by wrath.cs.utah.edu (8.8.8/8.8.8) with SMTP id UAA00061;
	Tue, 11 Aug 1998 20:32:49 -0600 (MDT)
Received: by taz.cs.utah.edu (950413.SGI.8.6.12/utah-2.15sun-leaf)
	id UAA223574; Tue, 11 Aug 1998 20:32:48 -0600
Date: Tue, 11 Aug 1998 20:32:48 -0600
From: sparker@taz.cs.utah.edu (Steven G. Parker)
Message-Id: <9808112032.ZM232940@taz.cs.utah.edu>
In-Reply-To: ralf@uni-koblenz.de
        "R4000 PROTOTYPE" (Aug 11,  1:14pm)
References: <35CD2CFC.32CACC90@mail.com>  <19980809171312.U938@uni-koblenz.de> 
	<35CDF934.293BB67@xmission.com> 
	<19980811131458.C480@uni-koblenz.de>
X-Mailer: Z-Mail-SGI (3.2S.3 08feb96 MediaMail)
To: ralf@uni-koblenz.de, Eric Jorgensen <alhaz@xmission.com>,
        linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: R4000 PROTOTYPE
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 873
Lines: 24

We have an Indy (one of the earlier) that identifies itself as version 2.2.
I've never pulled the heat sink off though...

Steve

On Aug 11,  1:14pm, ralf@uni-koblenz.de wrote:
> Subject: R4000 PROTOTYPE
> On Sun, Aug 09, 1998 at 01:32:04PM -0600, Eric Jorgensen wrote:
>
> >     On a completely unrelated note - out of curiosity I pulled the heatsink
> > off the cpu in my system - Never seen a mips 4k processor before. Anyway, I
> > was surprised to find the word "PROTOTYPE" emblazoned acrost the chip. Is
> > this common? Or do I have something really cool/funky here? if anybody
> > wants to see, I have a digital camera here.
>
> Maybe some long time MIPSer can tell something about this chip?  Is this
> the CPU version which identifies itself as version 2.2 which is the oldest
> I've ever seen?
>
> Thanks,
>
>   Ralf
>-- End of excerpt from ralf@uni-koblenz.de


From ralf@uni-koblenz.de  Thu Aug 13 02:18:14 1998
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id CAA18238; Thu, 13 Aug 1998 02:18:08 +0200 (MET DST)
Received-Date: Thu, 13 Aug 1998 02:18:08 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from uni-koblenz.de (pmport-03.uni-koblenz.de [141.26.249.3])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id CAA10740
	for <linux-mips@fnet.fr>; Thu, 13 Aug 1998 02:18:00 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id QAA02003;
	Wed, 12 Aug 1998 16:06:25 +0200
Message-ID: <19980812160625.R364@uni-koblenz.de>
Date: Wed, 12 Aug 1998 16:06:25 +0200
To: Eric Jorgensen <alhaz@xmission.com>, linux-mips@fnet.fr
Subject: Re: ISA audio in Magnum 4000pc,possibly?
References: <35CD2CFC.32CACC90@mail.com> <19980809171312.U938@uni-koblenz.de> <35CDF934.293BB67@xmission.com> <19980811131122.B480@uni-koblenz.de> <35D09103.DB8B8DA3@xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <35D09103.DB8B8DA3@xmission.com>; from Eric Jorgensen on Tue, Aug 11, 1998 at 12:44:19PM -0600
Content-Length: 3664
Lines: 69

On Tue, Aug 11, 1998 at 12:44:19PM -0600, Eric Jorgensen wrote:

> > >     On a completely unrelated note - out of curiosity I pulled the heatsink
> > > off the cpu in my system - Never seen a mips 4k processor before. Anyway, I
> > > was surprised to find the word "PROTOTYPE" emblazoned acrost the chip. Is
> > > this common? Or do I have something really cool/funky here? if anybody
> > > wants to see, I have a digital camera here.
> >
> > I've never seen a processor like that before.  The only thing I bet on is
> > that this processor is buggy like shit.
> 
>     Well, it has what I believe is a Fujitsu logo (has that curly S thing on it
> that was used as an F centuries ago, if you look at old documents like the
> US constitution) and it identifies itself as (unless I'm remembering wrong) a
> 76R4000PC-50G - there is also a letter G hand-written in pencil on the corner of
> the ceramic, and two other places on the ceramic where it looks like things have
> been scribbled over.

No idea what the G means.  The 50 btw is the external clock feed into the CPU
rsp. the maximum bus clock.  The internal clock rate is twice as fast, so this
is effectivly a 100Mhz machine.  For later CPU versions MIPS started measuring
the CPU just as others do in order to get a 100% bloat factor ...

>     Possibly this is an early low-power version?
> 
>     The thing is, there's no way this was a pre-release prototype of the
> original magnum, because the original magnum was Microsoft-designed box
> code-named Jazz. I actually have the whole story from the horses mouth (Atleast,
> a guy who was at mips during the fiasco) of how Mips was falling behind on their
> own design, and ended up buying the design that Microsoft had built to Dave
> Cutler's specs. So, since the board has Mips logos all over it, it's clearly not
> first-run, tho it could be something from the transitional period after MIPS
> bought the design from microsoft.

I've got one of the first machines, the inside of the Magnum's case has over
dozen signatures of the Magnum's development team on it.  I don't recall this
board to be any different from later versions I've seen.

>     On the other hand, only the processor says "prototoype" on it.
> 
>     I don't know much about where this box came from. I bought it as a surplus
> item from a local university. Word has it that a professor retired and nobody
> wanted his computers, so they stripped them for memory and storage devices, kept
> the monitors, and surplused the rest. I bought my Magnum for $5 USD, including
> the high-rez frame buffer and sound card. I also bought his old fileserver -
> DELL 4066/XE - a 486 but it's the size of a doghouse. Cost me $10.

Boy, you mu$t be rich :-)

>     I've actually never successfully booted it, still building a video cable to
> let it hook up to a Sun monitor that should support it's rez/refresh but has
> different wiring and possibly composite sync.
> 
>     So maybe after everything else stablizes it won't be too hard to adjust a
> linux/i386 driver won't be too hard to adjust.

Correctly written drivers are easy to fix.  The required change is just adding
a couple of subroutine calls.  The problem is that most MIPS boxes don't
deal with cache coherence in hardware.  So that has to be done in software.
So one has to writeback / invalidate the caches before a DMA operation can
start.  See <asm/io.h> in the MIPS kernel sources at the bottom.

>     One question - is there an ECU disk to configure EISA devices or is it in
> firmware?

It's probably a floppy disk as that software isn't in the firmware.  On the
other side I've never seen such a floppy disk.

  Ralf

From R.vandenBerg@inter.NL.net  Wed Aug 12 16:30:39 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id QAA06236; Wed, 12 Aug 1998 16:30:38 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 16:30:38 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-54.Hoorn.NL.net [193.79.46.218] with ESMTP for <linux-mips@fnet.fr>
	id QAA11295 (8.8.8/3.28); Wed, 12 Aug 1998 16:30:36 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0z6bus-0001ZNC@dutch.mountain>
	for <linux-mips@fnet.fr>; Wed, 12 Aug 1998 16:30:18 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Wed, 12 Aug 1998 16:30:18 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: Re: Linux on MIPS RC3230
In-Reply-To: <XFMail.980810204120.harald.koerfgen@netcologne.de>
Message-ID: <Pine.LNX.3.95.980812162907.864B-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 141
Lines: 11

Hi Harald

On Mon, 10 Aug 1998, Harald Koerfgen wrote:

> Hi all,
> 
> I'm back, alive and kicking.

Welcome! Good to hear you. :-)

Richard

From kristoff.bonne@belbone.net  Wed Aug 12 16:34:16 1998
Received: from mail.belbone.be (mail.belbone.be [195.13.1.3]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id QAA06306; Wed, 12 Aug 1998 16:34:14 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 16:34:14 +0200 (MET DST)
Received: from jupiler.belbone.be (unknown-1-182.belbone.be [195.13.1.182])
	by mail.belbone.be (8.8.8/8.8.8) with ESMTP id QAA01242
	for <linux-mips@fnet.fr>; Wed, 12 Aug 1998 16:33:51 +0200 (MET DST)
Received: from jupiler.belbone.be (jupiler.belbone.be [192.168.1.182])
	by jupiler.belbone.be (8.8.5/8.8.5) with SMTP id QAA28552
	for <linux-mips@fnet.fr>; Wed, 12 Aug 1998 16:34:06 +0200 (MET DST)
Message-Id: <199808121434.QAA28552@jupiler.belbone.be>
Date: Wed, 12 Aug 1998 16:34:05 +0200 (MET DST)
From: Kristoff Bonne <kristoff.bonne@belbone.net>
Reply-To: Kristoff Bonne <kristoff.bonne@belbone.net>
Subject: help cross-compiling MIPS-kernel on i386 linux
To: linux-mips@fnet.fr
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: f4wrliqBHSCpgMC2N/uk4Q==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4m sparc 
Content-Length: 2020
Lines: 56

Greetings,

This is the first time I try to cross-compile a linux-kernel, so this may be a stupid 
question, but I'll ask it anyway.

I've ftp'ed and installed the following files onto a (intel) linux-box:
- linux-2.1.99.tar.gz
- mipsel-binutils-2.8.1-linux.i386.tar.gz
- mipsel-gcc-2.7.2-linux.i386.tar.gz
- patch-2.1.99-pl2.tar.gz

$ cd $home/MIPS_linux/linux
$ make menuconfig
$ make dep ; make clean
$ make zImage

And then, thing start to go wrong!

* First of all, this:
as: unrecognized option `-cpu=r3000'

* This was just a warning, but then an error saying he cannot find a file called 
'stdarg.h'.
It appears the mipsel-linux-gcc command misses a '-I' option. (-I 
/home/kristoff/MIPS_linux/usr/local/lib/gcc-lib/mipsel-linux/2.7.2/include/)

I don't really know what file I need to edit to include this. Some 'Makefile', I 
guess?

* when I enter the command manually
$ mipsel-linux-gcc -D__KERNEL__ -I/home/kristoff/MIPS_linux/linux/include  -I 
/home/kristoff/MIPS_linux/usr/local/lib/gcc-lib/mipsel-linux/2.7.2/include/ -Wall 
-Wstrict-prototypes -O2 -fomit-frame-pointer -G 0 -mno-abicalls -fno-pic -mcpu=r3000 
-mips1 -pipe  -c -o init/main.o init/main.c

I get a even stranger error:
--- cut ---
as: unrecognized option `-cpu=r3000'
/home/kristoff/MIPS_linux/linux/include/asm/bugs.h: In function `check_bugs':
In file included from init/main.c:39:
/home/kristoff/MIPS_linux/linux/include/asm/bugs.h:43: output pipe has been closed
cpp: output pipe has been closed
mipsel-linux-gcc: Internal compiler error: program cc1 got fatal signal 13
--- cut ---

Looks to me like some bug in the source-code, but I did not see anything wrong when 
installing the kernel source-code, nor when applying to path.
(I did apply 'patch-2.1.99-pl2.tar.gz' on the original source-code).

Anybody any idea?

Cheerio! Kr. Bonne.
--
Bonne Kristoff                              belgacom multimedia
(C=BE,A=RTT,P=RTTIPC,S=BONNE,G=Kristoff)    operations belbone
Kristoff.bonne@belbone.net                  fax: +32 2 2024123

From engel@numerik.math.uni-siegen.de  Wed Aug 12 16:44:24 1998
Received: from fourier.numerik.math.uni-siegen.de (fourier.numerik.math.uni-siegen.de [141.99.2.230]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id QAA06393; Wed, 12 Aug 1998 16:44:21 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 16:44:21 +0200 (MET DST)
Received: from jordan.numerik (jordan [141.99.112.9]) by fourier.numerik.math.uni-siegen.de (Mailhost) with SMTP id QAA01164 for <linux-mips@fnet.fr>; Wed, 12 Aug 1998 16:44:22 +0200 (MET DST)
Received: by jordan.numerik (SMI-8.6/SMI-SVR4)
	id QAA11301; Wed, 12 Aug 1998 16:44:21 +0200
From: engel@numerik.math.uni-siegen.de (Michael Engel)
Message-Id: <199808121444.QAA11301@jordan.numerik>
Subject: Re: help cross-compiling MIPS-kernel on i386 linux
To: linux-mips@fnet.fr
Date: Wed, 12 Aug 1998 16:44:20 +0200 (MET DST)
In-Reply-To: <199808121434.QAA28552@jupiler.belbone.be> from "Kristoff Bonne" at Aug 12, 98 04:34:05 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1700
Lines: 53


Hi,

> This is the first time I try to cross-compile a linux-kernel, so this may be 
> a stupid question, but I'll ask it anyway.
> 
> I've ftp'ed and installed the following files onto a (intel) linux-box:
> - linux-2.1.99.tar.gz
> - mipsel-binutils-2.8.1-linux.i386.tar.gz
> - mipsel-gcc-2.7.2-linux.i386.tar.gz
> - patch-2.1.99-pl2.tar.gz
> 
> $ cd $home/MIPS_linux/linux
> $ make menuconfig
> $ make dep ; make clean
> $ make zImage

Use make vmlinux instead of make zImage, we can't boot compressed images 
yet ...

> And then, thing start to go wrong!
> 
> * First of all, this:
> as: unrecognized option `-cpu=r3000'

Huh, that's funny. It should usually say "mipsel-linux-as", if I'm not
mistaken. Could you check your kernel Makefile, please ?

> * This was just a warning, but then an error saying he cannot find a file called 
> 'stdarg.h'.
> It appears the mipsel-linux-gcc command misses a '-I' option. (-I 
> /home/kristoff/MIPS_linux/usr/local/lib/gcc-lib/mipsel-linux/2.7.2/include/)
> 
> I don't really know what file I need to edit to include this. Some 
> 'Makefile', I guess?

The top-level Makefile in the linux/mips source tree, correct. Try adding
-I/usr/include
to the compiler definition CC=mipsel-linux-gcc ...

This worked for me but I'm sure it's not the correct way to handle it.

[...]

> Looks to me like some bug in the source-code, but I did not see anything 
> wrong when installing the kernel source-code, nor when applying to path.
> (I did apply 'patch-2.1.99-pl2.tar.gz' on the original source-code).

I'll re-check the kernel and patch but I suspect there's something wrong
with your cross-compile setup.

regards,
	Michael Engel	(engel@unix-ag.uni-siegen.de)

From R.vandenBerg@inter.NL.net  Wed Aug 12 18:31:35 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA12170; Wed, 12 Aug 1998 18:31:34 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 18:31:34 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-7.Hoorn.NL.net [193.79.46.171] with ESMTP for <linux-mips@fnet.fr>
	id SAA28602 (8.8.8/3.28); Wed, 12 Aug 1998 18:31:32 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0z6dmz-0001YdC@dutch.mountain>
	for <linux-mips@fnet.fr>; Wed, 12 Aug 1998 18:30:17 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Wed, 12 Aug 1998 18:30:16 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: Re: help cross-compiling MIPS-kernel on i386 linux
In-Reply-To: <199808121444.QAA11301@jordan.numerik>
Message-ID: <Pine.LNX.3.95.980812182957.864D-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 2678
Lines: 74

On Wed, 12 Aug 1998, Michael Engel wrote:

> Hi,
> 
> > This is the first time I try to cross-compile a linux-kernel, so this may be 
> > a stupid question, but I'll ask it anyway.
> > 
> > I've ftp'ed and installed the following files onto a (intel) linux-box:
> > - linux-2.1.99.tar.gz
> > - mipsel-binutils-2.8.1-linux.i386.tar.gz
> > - mipsel-gcc-2.7.2-linux.i386.tar.gz
> > - patch-2.1.99-pl2.tar.gz

Is the PATH enviroment variable pointing at the cross compile programs? I
installed them in /usr/local/bin, the usual place if you compile binutils
for yourself for example.

> > $ cd $home/MIPS_linux/linux
> > $ make menuconfig
> > $ make dep ; make clean
> > $ make zImage
> 
> Use make vmlinux instead of make zImage, we can't boot compressed images 
> yet ...

Or netboot, check the Makefile in arch/mips/dec/boot for possibilities,
`make netboot` leaves nbImage in that directory from which a DECstation
is able to boot via network.
 
> > And then, thing start to go wrong!
> > 
> > * First of all, this:
> > as: unrecognized option `-cpu=r3000'
> 
> Huh, that's funny. It should usually say "mipsel-linux-as", if I'm not
> mistaken. Could you check your kernel Makefile, please ?
> 
> > * This was just a warning, but then an error saying he cannot find a file called 
> > 'stdarg.h'.
> > It appears the mipsel-linux-gcc command misses a '-I' option. (-I 
> > /home/kristoff/MIPS_linux/usr/local/lib/gcc-lib/mipsel-linux/2.7.2/include/)
> > 
> > I don't really know what file I need to edit to include this. Some 
> > 'Makefile', I guess?

I never had to edit a Makefile of the original source to compile, have
you looked at http://www.inter.nl.net/users/schnecke/html/mips there's
some related info and links.

> The top-level Makefile in the linux/mips source tree, correct. Try adding
> -I/usr/include
> to the compiler definition CC=mipsel-linux-gcc ...
> 
> This worked for me but I'm sure it's not the correct way to handle it.
> 
> [...]
> 
> > Looks to me like some bug in the source-code, but I did not see anything 
> > wrong when installing the kernel source-code, nor when applying to path.
> > (I did apply 'patch-2.1.99-pl2.tar.gz' on the original source-code).
> 
> I'll re-check the kernel and patch but I suspect there's something wrong
> with your cross-compile setup.

Agree with that Michael, the 2.1.99 source from decstation.unix-ag.org
has never given me any troubles, without the logical ones
of course.:-) Trying to compile unsupported hardware for
example. 'patch-2.1.99-pl2.tar.gz' applied correctly, I only had to move
a new file to the right place which can been seen looking at the diff
(the right location that is).

Regards,

Richard

From alhaz@xmission.com  Thu Aug 13 01:29:21 1998
Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id BAA17226; Thu, 13 Aug 1998 01:29:13 +0200 (MET DST)
Received-Date: Thu, 13 Aug 1998 01:29:13 +0200 (MET DST)
Received: from alhaz.users.xmission.com (xmission.com) [207.135.128.199] (alhaz)
	by mail.xmission.com with esmtp (Exim 1.82 #2)
	id 0z6kK4-00068F-00; Wed, 12 Aug 1998 17:28:52 -0600
Sender: alhaz@fnet.fr
Message-ID: <35D1D03D.7EA4474E@xmission.com>
Date: Wed, 12 Aug 1998 11:26:21 -0600
From: Eric Jorgensen <alhaz@xmission.com>
X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.32 i486)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: Re: Philips Velo 500 as a candidate for Linux/MIPS?
References: <c=MX%a=_%p=avantel%l=MTYEHQSA01-980812225630Z-32205@mtymail.avantel.com.mx>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 503
Lines: 15

Jesus Eugenio Sanchez wrote:

> Maybe I'm asking *very* stupid questions, but...
>
> Would it possible to get these machines *without* an OS
> installed? BTW, if you have the developments tools from
> Microsoft to cross-compile, how do you upload the app
> into the gadget?

    Chances are, Microsoft is actually paying them to use WindowsCE. This
is the case with TCI's planned set-tops, for instance. Microsoft is
paying them $20 per machine to include a copy of WindowsCE along side
JavaOS

 - Eric

From petr@i.cz  Wed Aug 12 22:46:09 1998
Received: from ns.i.cz (root@ns.i.cz [193.85.255.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id WAA13805; Wed, 12 Aug 1998 22:46:07 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 22:46:07 +0200 (MET DST)
Received: from petr-nbd.internet.cz (test9.internet.cz [193.85.158.29])
	by ns.i.cz (8.8.8/8.8.8) with SMTP id WAA01344
	for <linux-mips@fnet.fr>; Wed, 12 Aug 1998 22:48:56 +0200
Date: Wed, 12 Aug 1998 22:47:16 +0200 (MET DST)
From: Petr Novak <Petr.Novak@i.cz>
To: linux-mips@fnet.fr
Subject: Philips Velo 500 as a candidate for Linux/MIPS?
Message-ID: <Pine.WNT.3.96.980812224128.-838233C-100000@petr-nbd.internet.cz>
X-X-Sender: petr@ns.i.cz
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 849
Lines: 27

Hello,

I have recently learned about a machine called Philips Velo 500. The
handheld box natively runs Windows CE 2.0, but is based on a
well-documented 2-chip set by Philips, which contains a MIPS 3900 core.
The same chipset is used in recent handhelds by Compaq and Sharp. The
Velo 500 is from $600 in the US with 16MB RAM and 640x240 grayscale
display.

I was wondering wheather somebody has considered to port Linux onto this
box. With a bit of luck, it might even run X one day...

I know there are port efforts to other power-handhelds, namely the ARM
based Psion 5 and Geofox 1, but the Velo seems at least as well documented
and more integrated than the CL-PS7110 based machines.

Any ideas, pointers?

Thanks in advance.

--
Petr Novak <Petr.Novak@i.cz>
ICZ a.s.
Zirovnicka 6
CZ-106 00 Praha 10
Ph:  +420 2 2424 5124
Fax: +420 2 2424 5125

From imp@village.org  Wed Aug 12 22:58:11 1998
Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id WAA13913; Wed, 12 Aug 1998 22:58:09 +0200 (MET DST)
Received-Date: Wed, 12 Aug 1998 22:58:09 +0200 (MET DST)
Received: from harmony [10.0.0.6] 
	by rover.village.org with esmtp (Exim 1.71 #1)
	id 0z6hxy-00058a-00; Wed, 12 Aug 1998 14:57:54 -0600
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id OAA15155 for <linux-mips@fnet.fr>; Wed, 12 Aug 1998 14:59:28 -0600 (MDT)
Message-Id: <199808122059.OAA15155@harmony.village.org>
To: linux-mips@fnet.fr
Subject: Re: Philips Velo 500 as a candidate for Linux/MIPS? 
In-reply-to: Your message of "Wed, 12 Aug 1998 22:47:16 +0200."
		<Pine.WNT.3.96.980812224128.-838233C-100000@petr-nbd.internet.cz> 
References: <Pine.WNT.3.96.980812224128.-838233C-100000@petr-nbd.internet.cz>  
Date: Wed, 12 Aug 1998 14:59:27 -0600
From: Warner Losh <imp@village.org>
Content-Length: 1009
Lines: 22

In message <Pine.WNT.3.96.980812224128.-838233C-100000@petr-nbd.internet.cz> Petr Novak writes:
: I was wondering wheather somebody has considered to port Linux onto this
: box. With a bit of luck, it might even run X one day...

I've started looking into the Nec Vr4111 + Vrc4171 combination which
appears in many of the PalmTop machines.  Namely the Caseo Casiopea
E-10 and something made by Everex.  Getting docs on these from NEC was
rather an easy thing to do.  These are in the $300-$400 range,
depending on memory and options.  NEC also makes a handheld in the
$900 range based on these chips.

Do you have a number at Philips that I can get info on these chips?
Got the exact chip numbers, which seems to help?

I'd love to see some way to run Linux or some other free OS on the CE
machines.  However, I've stated before that I'm not sure how to go
about writing a boot loader, putting WinCE back should the kenrel
build be bad, etc.  I'd love to see a discussion about how to go about
this.

Warner


From rusek@iname.com  Thu Aug 13 00:56:22 1998
Received: from catbert.fdu.edu (catbert.fdu.edu [132.238.12.14]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id AAA16143; Thu, 13 Aug 1998 00:56:17 +0200 (MET DST)
Received-Date: Thu, 13 Aug 1998 00:56:17 +0200 (MET DST)
Received: from laadmin by catbert.fdu.edu via ESMTP (940816.SGI.8.6.9/940406.SGI.AUTO)
	for <linux-mips@fnet.fr> id SAA01562; Wed, 12 Aug 1998 18:49:39 -0400
Message-ID: <003001bdc644$68ca3500$78d7fea9@laadmin>
From: "Robert Rusek" <rusek@iname.com>
To: <linux-mips@fnet.fr>
Subject: Status of Linux-Mips for DecStation 5000/25
Date: Wed, 12 Aug 1998 15:56:10 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Content-Length: 305
Lines: 11

Can anyone tell me what the status of the Linux is for the DecStation
5000/25.  I am currently running OpenBSD 2.3 on it but am interested in
putting Linux on it.

Thank you in advance.
--
Robert Rusek
rusek@iname.com
--------------------------------
http://rusek.fdu.edu
--------------------------------

From eugenio.sanchez@avantel.com.mx  Thu Aug 13 00:55:26 1998
Received: from mty-egw1.avantel.com.mx (mty-egw1.avantel.com.mx [200.33.230.4]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA16113; Thu, 13 Aug 1998 00:55:21 +0200 (MET DST)
Received-Date: Thu, 13 Aug 1998 00:55:21 +0200 (MET DST)
Received: from mty-igw1.avantel.com.mx (root@localhost)
	by mty-egw1.avantel.com.mx with ESMTP id RAA06132
	for <linux-mips@fnet.fr>; Wed, 12 Aug 1998 17:56:11 -0500 (CDT)
Received: from mtymail.avantel.com.mx (mtymsfco01.icom.avantel.com.mx [172.24.2.4])
	by mty-igw1.avantel.com.mx with SMTP id RAA06125
	for <linux-mips@fnet.fr>; Wed, 12 Aug 1998 17:56:11 -0500 (CDT)
Received: by mtymail.avantel.com.mx with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52)
	id <01BDC61A.7BCD8DC0@mtymail.avantel.com.mx>; Wed, 12 Aug 1998 17:56:08 -0500
Message-ID: <c=MX%a=_%p=avantel%l=MTYEHQSA01-980812225630Z-32205@mtymail.avantel.com.mx>
From: Jesus Eugenio Sanchez <eugenio.sanchez@avantel.com.mx>
To: "'linux-mips@fnet.fr'" <linux-mips@fnet.fr>
Subject: RE: Philips Velo 500 as a candidate for Linux/MIPS? 
Date: Wed, 12 Aug 1998 17:56:30 -0500
X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Length: 1442
Lines: 40

Maybe I'm asking *very* stupid questions, but...

Would it possible to get these machines *without* an OS
installed? BTW, if you have the developments tools from
Microsoft to cross-compile, how do you upload the app
into the gadget?


-----Original Message-----
From: Warner Losh [mailto:imp@village.org]
Sent: Wednesday, August 12, 1998 3:59 PM
To: linux-mips@fnet.fr
Subject: Re: Philips Velo 500 as a candidate for Linux/MIPS? 


In message
<Pine.WNT.3.96.980812224128.-838233C-100000@petr-nbd.internet.cz> Petr
Novak writes:
: I was wondering wheather somebody has considered to port Linux onto
this
: box. With a bit of luck, it might even run X one day...

I've started looking into the Nec Vr4111 + Vrc4171 combination which
appears in many of the PalmTop machines.  Namely the Caseo Casiopea
E-10 and something made by Everex.  Getting docs on these from NEC was
rather an easy thing to do.  These are in the $300-$400 range,
depending on memory and options.  NEC also makes a handheld in the
$900 range based on these chips.

Do you have a number at Philips that I can get info on these chips?
Got the exact chip numbers, which seems to help?

I'd love to see some way to run Linux or some other free OS on the CE
machines.  However, I've stated before that I'm not sure how to go
about writing a boot loader, putting WinCE back should the kenrel
build be bad, etc.  I'd love to see a discussion about how to go about
this.

Warner


From ralf@uni-koblenz.de  Thu Aug 13 02:17:53 1998
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id CAA18216; Thu, 13 Aug 1998 02:17:46 +0200 (MET DST)
Received-Date: Thu, 13 Aug 1998 02:17:46 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from uni-koblenz.de (pmport-03.uni-koblenz.de [141.26.249.3])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id CAA10643
	for <linux-mips@fnet.fr>; Thu, 13 Aug 1998 02:17:34 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id CAA02540;
	Thu, 13 Aug 1998 02:07:29 +0200
Message-ID: <19980813020729.A2077@uni-koblenz.de>
Date: Thu, 13 Aug 1998 02:07:29 +0200
To: Kristoff Bonne <kristoff.bonne@belbone.net>, linux-mips@fnet.fr
Subject: Re: help cross-compiling MIPS-kernel on i386 linux
References: <199808121434.QAA28552@jupiler.belbone.be>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <199808121434.QAA28552@jupiler.belbone.be>; from Kristoff Bonne on Wed, Aug 12, 1998 at 04:34:05PM +0200
Content-Length: 2061
Lines: 56

On Wed, Aug 12, 1998 at 04:34:05PM +0200, Kristoff Bonne wrote:

> Greetings,
> 
> This is the first time I try to cross-compile a linux-kernel, so this may be a stupid 
> question, but I'll ask it anyway.
> 
> I've ftp'ed and installed the following files onto a (intel) linux-box:
> - linux-2.1.99.tar.gz
> - mipsel-binutils-2.8.1-linux.i386.tar.gz
> - mipsel-gcc-2.7.2-linux.i386.tar.gz
> - patch-2.1.99-pl2.tar.gz
> 
> $ cd $home/MIPS_linux/linux
> $ make menuconfig
> $ make dep ; make clean
> $ make zImage
> 
> And then, thing start to go wrong!
> 
> * First of all, this:
> as: unrecognized option `-cpu=r3000'
> 
> * This was just a warning, but then an error saying he cannot find a file called 
> 'stdarg.h'.

This happens because you don't have the crossbinutils installed at all or
you have them in a place where gcc doesn't find as.

> It appears the mipsel-linux-gcc command misses a '-I' option. (-I 
> /home/kristoff/MIPS_linux/usr/local/lib/gcc-lib/mipsel-linux/2.7.2/include/)
> 
> I don't really know what file I need to edit to include this. Some 'Makefile', I 
> guess?

Seems you took the binaries and moved everything that should be in /usr/
to /home/kristoff/MIPS_linux/usr/?  That won't work, the compiler driver
mips-linux-gcc knows where it is supposed to search for the other compiler
parts - and fails.  You can force it to search in the right place by adding
the option -B<path> to the compiler flags or setting GCC_EXEC_PREFIX to
the appropriate value (see GCC documentation) but I'd rather recommend to
fix the crosscompiler installation itself.

> --- cut ---
> as: unrecognized option `-cpu=r3000'
> /home/kristoff/MIPS_linux/linux/include/asm/bugs.h: In function `check_bugs':
> In file included from init/main.c:39:
> /home/kristoff/MIPS_linux/linux/include/asm/bugs.h:43: output pipe has been closed
> cpp: output pipe has been closed
> mipsel-linux-gcc: Internal compiler error: program cc1 got fatal signal 13
> --- cut ---

Signal 13 is SIGPIPE on Linux/i386, exactly what is supposed to happen in
this case ...

  Ralf

From dom@algor.co.uk  Thu Aug 13 09:22:21 1998
Received: from embankment.algor.co.uk (0@embankment.algor.co.uk [193.117.190.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id JAA22679; Thu, 13 Aug 1998 09:22:20 +0200 (MET DST)
Received-Date: Thu, 13 Aug 1998 09:22:20 +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.8/8.8.8) with ESMTP id IAA29655
	for <linux-mips@fnet.fr>; Thu, 13 Aug 1998 08:22:13 +0100 (BST)
Received: (from dom@localhost)
	by gladsmuir.algor.co.uk (8.8.5/8.8.5) id IAA00236;
	Thu, 13 Aug 1998 08:22:15 +0100 (GMT/BST)
Date: Thu, 13 Aug 1998 08:22:15 +0100 (GMT/BST)
Message-Id: <199808130722.IAA00236@gladsmuir.algor.co.uk>
From: Dominic Sweetman <dom@algor.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: linux-mips@fnet.fr
Subject: Re: ISA audio in Magnum 4000pc,possibly?
In-Reply-To: <19980812160625.R364@uni-koblenz.de>
References: <35CD2CFC.32CACC90@mail.com>
	<19980809171312.U938@uni-koblenz.de>
	<35CDF934.293BB67@xmission.com>
	<19980811131122.B480@uni-koblenz.de>
	<35D09103.DB8B8DA3@xmission.com>
	<19980812160625.R364@uni-koblenz.de>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Content-Length: 1304
Lines: 31



> On Tue, Aug 11, 1998 at 12:44:19PM -0600, Eric Jorgensen wrote:

> > Well, it has what I believe is a Fujitsu logo (has that curly
> > S thing on it that was used as an F centuries ago...

You're looking at an R4000 made by IDT (Integrated Device Technology)
and their logo is an "integral" sign.  The "G" marks the
pin-grid-array package.  The "PC" meant that this is the economy
package - the "SC" parts devoted lots of extra pins to a dedicated
backdoor cache bus, and "MC" parts had the multiprocessor bugs fixed.

IDT made a lot of the earliest R4000 chips (a typical pattern for MIPS
was that the small, fast-moving US chip makers would deliver early chips
for debug and development, and NEC would then come in and undercut
them for production.  None of the silicon vendors ever made any money
out of this at the time...)

> >     The thing is, there's no way this was a pre-release prototype
> > of the original magnum, because the original magnum was
> > Microsoft-designed box code-named Jazz. 

I think you may be confusing two histories here.  I think the Magnum
all MIPS' own work, since it was related to an earlier R3000-powered
Magnum.  Jazz was a platform for the Windows NT development at
Microsoft, which happened some time later.

Dominic Sweetman
Algorithmics Ltd
dom@algor.co.uk

From dom@algor.co.uk  Thu Aug 13 09:30:15 1998
Received: from embankment.algor.co.uk (0@embankment.algor.co.uk [193.117.190.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id JAA22923; Thu, 13 Aug 1998 09:30:14 +0200 (MET DST)
Received-Date: Thu, 13 Aug 1998 09:30:14 +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.8/8.8.8) with ESMTP id IAA29682;
	Thu, 13 Aug 1998 08:30:12 +0100 (BST)
Received: (from dom@localhost)
	by gladsmuir.algor.co.uk (8.8.5/8.8.5) id IAA00249;
	Thu, 13 Aug 1998 08:30:13 +0100 (GMT/BST)
Date: Thu, 13 Aug 1998 08:30:13 +0100 (GMT/BST)
Message-Id: <199808130730.IAA00249@gladsmuir.algor.co.uk>
From: Dominic Sweetman <dom@algor.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: linux-mips@fnet.fr
Subject: Re: Philips Velo 500 as a candidate for Linux/MIPS? 
In-Reply-To: <199808122059.OAA15155@harmony.village.org>
References: <Pine.WNT.3.96.980812224128.-838233C-100000@petr-nbd.internet.cz>
	<199808122059.OAA15155@harmony.village.org>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Content-Length: 1069
Lines: 32


Warner Losh (imp@village.org) writes:

> Do you have a number at Philips that I can get info on these chips?
> Got the exact chip numbers, which seems to help?

I talked to Marnix Vlot <m.vlot@ehv.sc.philips.com> a couple of years
ago when Philips were developing these things - perhaps he'd be
helpful.  

Philips' MIPS/CE products are PR31100 and PR31500, and you can
download "acrobat" manuals from:

  http://www-us2.semiconductors.philips.com/cgi-bin/searchpdf

try "MIPS" in the search box.

[If you want to read acrobat files on Linux, use a recent gv + Aladdin
 ghostscript]

> I'd love to see some way to run Linux or some other free OS on the CE
> machines.  However, I've stated before that I'm not sure how to go
> about writing a boot loader, putting WinCE back should the kenrel
> build be bad, etc.  I'd love to see a discussion about how to go about
> this.

My firm Algorithmics have signed up as systems integrators for Windows
CE, and we may be able to offer some help; but there's not many of us.

Dominic Sweetman
Algorithmics Ltd
dom@algor.co.uk

From R.vandenBerg@inter.NL.net  Thu Aug 13 15:52:37 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id PAA25752; Thu, 13 Aug 1998 15:52:37 +0200 (MET DST)
Received-Date: Thu, 13 Aug 1998 15:52:37 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-14.Hoorn.NL.net [193.79.46.178] with ESMTP for <linux-mips@fnet.fr>
	id PAA01735 (8.8.8/3.28); Thu, 13 Aug 1998 15:52:35 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0z6xfv-0001YdC@dutch.mountain>
	for <linux-mips@fnet.fr>; Thu, 13 Aug 1998 15:44:19 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Thu, 13 Aug 1998 15:44:18 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: Re: Status of Linux-Mips for DecStation 5000/25
In-Reply-To: <003001bdc644$68ca3500$78d7fea9@laadmin>
Message-ID: <Pine.LNX.3.95.980813154215.475A-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 361
Lines: 12

On Wed, 12 Aug 1998, Robert Rusek wrote:

> Can anyone tell me what the status of the Linux is for the DecStation
> 5000/25.  I am currently running OpenBSD 2.3 on it but am interested in
> putting Linux on it.

That's in development, look at http://decstation.unix-ag.org for details.
Latest status is that the first user proces is running.

Regards,

Richard

From jdouma@ivs.com  Thu Aug 13 19:11:54 1998
Received: from blackberry.ivs.com (www.ivs.com [207.177.145.250]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA27016; Thu, 13 Aug 1998 19:11:52 +0200 (MET DST)
Received-Date: Thu, 13 Aug 1998 19:11:52 +0200 (MET DST)
Received: from ivs.com (mulberry.ivs.com [207.177.145.166])
	by blackberry.ivs.com (8.8.5/8.8.5) with ESMTP id JAA25805
	for <linux-mips@fnet.fr>; Thu, 13 Aug 1998 09:17:36 -0700
Sender: jdouma@blackberry.ivs.com
Message-ID: <35D31E6B.735B84@ivs.com>
Date: Thu, 13 Aug 1998 17:12:11 +0000
From: James Douma <jdouma@ivs.com>
Organization: IVS, Inc
X-Mailer: Mozilla 4.5b1 [en] (X11; I; Linux 2.0.32 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: Re: Philips Velo 500 as a candidate for Linux/MIPS?
References: <c=MX%a=_%p=avantel%l=MTYEHQSA01-980812225630Z-32205@mtymail.avantel.com.mx>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 2413
Lines: 57

The HPC's and Palm PC's being made today have CE in ROM.  Thats ROM, not
PROM. You can't remove it without a soldering iron, and it can't be
modified or updated.  There is, of course, the ability to run installed
applications in RAM after loading from other media - so getting Linux
working on them is not out of the question.  However, because the 8MB of
code space which is in ROM would not be available to another operating
system, Linux would have to run with much reduced resources compared to
the built-in CE OS.

There is probably not much chance of getting an off-the-shelf unit
without CE. These things are made in volume with little to no variation.

It would be a neat hardware hack to remove the ROMs and substitute them
with parts containing Linux, though you'd have to do embedded - style
development with long iteration cycles to get it working.

James

Jesus Eugenio Sanchez wrote:
> 
> Maybe I'm asking *very* stupid questions, but...
> 
> Would it possible to get these machines *without* an OS
> installed? BTW, if you have the developments tools from
> Microsoft to cross-compile, how do you upload the app
> into the gadget?
> 
> -----Original Message-----
> From: Warner Losh [mailto:imp@village.org]
> Sent: Wednesday, August 12, 1998 3:59 PM
> To: linux-mips@fnet.fr
> Subject: Re: Philips Velo 500 as a candidate for Linux/MIPS?
> 
> In message
> <Pine.WNT.3.96.980812224128.-838233C-100000@petr-nbd.internet.cz> Petr
> Novak writes:
> : I was wondering wheather somebody has considered to port Linux onto
> this
> : box. With a bit of luck, it might even run X one day...
> 
> I've started looking into the Nec Vr4111 + Vrc4171 combination which
> appears in many of the PalmTop machines.  Namely the Caseo Casiopea
> E-10 and something made by Everex.  Getting docs on these from NEC was
> rather an easy thing to do.  These are in the $300-$400 range,
> depending on memory and options.  NEC also makes a handheld in the
> $900 range based on these chips.
> 
> Do you have a number at Philips that I can get info on these chips?
> Got the exact chip numbers, which seems to help?
> 
> I'd love to see some way to run Linux or some other free OS on the CE
> machines.  However, I've stated before that I'm not sure how to go
> about writing a boot loader, putting WinCE back should the kenrel
> build be bad, etc.  I'd love to see a discussion about how to go about
> this.
> 
> Warner

From imp@village.org  Thu Aug 13 19:30:42 1998
Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id TAA27567; Thu, 13 Aug 1998 19:30:40 +0200 (MET DST)
Received-Date: Thu, 13 Aug 1998 19:30:40 +0200 (MET DST)
Received: from harmony [10.0.0.6] 
	by rover.village.org with esmtp (Exim 1.71 #1)
	id 0z71Co-0005mh-00; Thu, 13 Aug 1998 11:30:30 -0600
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id LAA07621 for <linux-mips@fnet.fr>; Thu, 13 Aug 1998 11:32:14 -0600 (MDT)
Message-Id: <199808131732.LAA07621@harmony.village.org>
To: linux-mips@fnet.fr
Subject: Re: Philips Velo 500 as a candidate for Linux/MIPS? 
In-reply-to: Your message of "Thu, 13 Aug 1998 17:12:11 -0000."
		<35D31E6B.735B84@ivs.com> 
References: <35D31E6B.735B84@ivs.com>  <c=MX%a=_%p=avantel%l=MTYEHQSA01-980812225630Z-32205@mtymail.avantel.com.mx> 
Date: Thu, 13 Aug 1998 11:32:14 -0600
From: Warner Losh <imp@village.org>
Content-Length: 1094
Lines: 24

In message <35D31E6B.735B84@ivs.com> James Douma writes:
: The HPC's and Palm PC's being made today have CE in ROM.  Thats ROM, not
: PROM. You can't remove it without a soldering iron, and it can't be
: modified or updated.

It was myunderstanding that these were FLASH, at the very least.  At
least from the one CE box I've seen disassembled I saw it had FLASH
chips.  Granted, it wasn't the MIPS based box that I want... If one
can run in kernel mode, then one can reprogram that FLASH memory.  The
data sheets for the Vr4111 are detailed on exactly how to do this, how
to do one bank, while the other acts as your backup, etc.

It may be that WinCE gives the user no supported way to do the
upgrades, and that there is no interface for it.  The bare silicon
should support this, however....

Onsale has Velo 500's (I think, it is MIPS based) 12M for $199.  I
think for that price, it would be worth the risk of getting one,
popping it open and seeing for myself.  I'll have to checkout the
philips datasheet pointer posted earlier to see if that core has flash
functions or not...

Warner


From lukas@cubic.org  Mon Aug 17 19:59:16 1998
Received: from dn.demo.org (root@pppa99.hildesheim.sgh-net.de [193.218.216.99]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA24851; Mon, 17 Aug 1998 19:59:14 +0200 (MET DST)
Received-Date: Mon, 17 Aug 1998 19:59:14 +0200 (MET DST)
Received: from dn.demo.org (lukas@dn.demo.org [192.0.2.254])
	by dn.demo.org (8.8.7/8.8.7) with SMTP id TAA17578;
	Thu, 13 Aug 1998 19:53:38 +0200
Date: Thu, 13 Aug 1998 19:53:38 +0200 (CEST)
From: Lukas Grunwald <lukas@cubic.org>
X-Sender: lukas@dn.demo.org
To: Ulf Carlsson <grim@zigzegv.ml.org>
cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: R4[04]00SC
In-Reply-To: <199808171657.SAA29305@calypso.saturn>
Message-ID: <Pine.LNX.3.96.980813195233.17575A-100000@dn.demo.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 600
Lines: 25

On Mon, 17 Aug 1998, Ulf Carlsson wrote:

Hi,

> Hi,
> 
> I can report that I've a R4000SC running here with Linux. After hard work
> (many long hours, mainly reading MIPS Manual), the VCE exceptions are now
> correctly handled. R4400SC will (probably) also work now. The next step is to
> make this exceptions never happen.

Is this patch only avil via CVS or do you plan to make a SNAPSHOT ?

> 


  ___,/|
  \ o_O|   Greetings from
  =(_|_)=             Lukas
     U                  aka Master of the MatriX  CubiC WHQ / Xography

	    mail:     lukas@cubic.org
	    http:       www.cubic.org 



From jdouma@ivs.com  Thu Aug 13 19:56:16 1998
Received: from blackberry.ivs.com (www.ivs.com [207.177.145.250]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA27748; Thu, 13 Aug 1998 19:56:14 +0200 (MET DST)
Received-Date: Thu, 13 Aug 1998 19:56:14 +0200 (MET DST)
Received: from ivs.com (mulberry.ivs.com [207.177.145.166])
	by blackberry.ivs.com (8.8.5/8.8.5) with ESMTP id KAA26533
	for <linux-mips@fnet.fr>; Thu, 13 Aug 1998 10:01:59 -0700
Sender: jdouma@blackberry.ivs.com
Message-ID: <35D328D2.C2324067@ivs.com>
Date: Thu, 13 Aug 1998 17:56:34 +0000
From: James Douma <jdouma@ivs.com>
Organization: IVS, Inc
X-Mailer: Mozilla 4.5b1 [en] (X11; I; Linux 2.0.32 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: Re: Philips Velo 500 as a candidate for Linux/MIPS?
References: <35D31E6B.735B84@ivs.com>  <c=MX%a=_%p=avantel%l=MTYEHQSA01-980812225630Z-32205@mtymail.avantel.com.mx> <199808131732.LAA07621@harmony.village.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 2241
Lines: 54

Warner Losh wrote:
> 
> In message <35D31E6B.735B84@ivs.com> James Douma writes:
> : The HPC's and Palm PC's being made today have CE in ROM.  Thats ROM, not
> : PROM. You can't remove it without a soldering iron, and it can't be
> : modified or updated.
> 
> It was myunderstanding that these were FLASH, at the very least.  At
> least from the one CE box I've seen disassembled I saw it had FLASH
> chips.  Granted, it wasn't the MIPS based box that I want... If one
> can run in kernel mode, then one can reprogram that FLASH memory.  The
> data sheets for the Vr4111 are detailed on exactly how to do this, how
> to do one bank, while the other acts as your backup, etc.

It is entirely possible that a particular manufacturer would decide to
use Flash rather than ROM to store the OS for their HPC.  It is even
conceivable that they would provide a low level method for changing the
OS (something that MS specifically does NOT want people to do with CE)
as a bug-fix feature.  There are good reasons for this:

Faster time to market, flexibility in dealing with problems on the
production line, the ability to use 'excess' memory (between 'size of OS
binary' and 'top of memory') for non-volatile storage, fewer components
(use 2 flash parts instead of 2 flash + 2 rom)...

> 
> It may be that WinCE gives the user no supported way to do the
> upgrades, and that there is no interface for it.  The bare silicon
> should support this, however....

Yes, CE has NO support for this, but I agree that the hardware might
possibly support this.  OTOH - boot block flash is commonly used in this
situation, and the hardware rarely supports overwriting the boot block
portions of the flash memory.

> 
> Onsale has Velo 500's (I think, it is MIPS based) 12M for $199.  I
> think for that price, it would be worth the risk of getting one,
> popping it open and seeing for myself.  I'll have to checkout the
> philips datasheet pointer posted earlier to see if that core has flash
> functions or not...
> 
> Warner

Cool - let me know what you find out.

James 


-- 
James Douma  --  Manager, Hardware Development
       Interactive Voice Systems Inc
email: jdouma@ivs.com      pager: 818.297.3058
Phone: 626.256.3123          Fax: 626.256.3197

From imp@village.org  Thu Aug 13 20:53:51 1998
Received: from rover.village.org (rover.village.org [204.144.255.49]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id UAA28527; Thu, 13 Aug 1998 20:53:49 +0200 (MET DST)
Received-Date: Thu, 13 Aug 1998 20:53:49 +0200 (MET DST)
Received: from harmony [10.0.0.6] 
	by rover.village.org with esmtp (Exim 1.71 #1)
	id 0z72VI-0005pO-00; Thu, 13 Aug 1998 12:53:40 -0600
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id MAA08103 for <linux-mips@fnet.fr>; Thu, 13 Aug 1998 12:55:25 -0600 (MDT)
Message-Id: <199808131855.MAA08103@harmony.village.org>
To: linux-mips@fnet.fr
Subject: Re: Philips Velo 500 as a candidate for Linux/MIPS? 
In-reply-to: Your message of "Thu, 13 Aug 1998 17:56:34 -0000."
		<35D328D2.C2324067@ivs.com> 
References: <35D328D2.C2324067@ivs.com>  <35D31E6B.735B84@ivs.com> <c=MX%a=_%p=avantel%l=MTYEHQSA01-980812225630Z-32205@mtymail.avantel.com.mx> <199808131732.LAA07621@harmony.village.org> 
Date: Thu, 13 Aug 1998 12:55:25 -0600
From: Warner Losh <imp@village.org>
Content-Length: 1144
Lines: 25

In message <35D328D2.C2324067@ivs.com> James Douma writes:
: Yes, CE has NO support for this, but I agree that the hardware might
: possibly support this.  OTOH - boot block flash is commonly used in this
: situation, and the hardware rarely supports overwriting the boot block
: portions of the flash memory.

Looking at the users' manual for the Vr4111 it shows that this is
possible.  Reading them carefully, however, shows one gotcha.  They
say that in order to write to FLASH, one must assert the Vpp voltage
on the flash chip in question by some undefined means.  They suggest
using the GPIO function of the chip, or, if that's not possible,
arranging for the Vpp signal to be applied.

I have the facilities to run a wire from one of the GPIO ports to the
Vpp pin of the flash ram at the hardware lab at work.  However, not
everyone has this option...

There isn't really a boot block flash here.  There are two banks of
memory, and two sub banks of ROM.  If it is FLASH, then either one of
them can be programmed so long as you aren't running out of that
bank...

Again, I've not yet checked the R3900 that the Velo uses yet...

Warner

From alhaz@xmission.xmission.com  Fri Aug 14 19:06:32 1998
Received: from xmission.xmission.com (alhaz@xmission.xmission.com [198.60.22.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA12833; Fri, 14 Aug 1998 19:06:30 +0200 (MET DST)
Received-Date: Fri, 14 Aug 1998 19:06:30 +0200 (MET DST)
Received: (from alhaz@localhost) by xmission.xmission.com (8.8.8/8.7.5) id LAA29261 for linux-mips@fnet.fr; Fri, 14 Aug 1998 11:06:18 -0600 (MDT)
Envelope-to: alhaz@xmission.com
Delivery-date: Fri, 14 Aug 1998 11:05:49 -0600
Received: from (sam.parlant.com) [207.173.26.1] 
	by mail.xmission.com with smtp (Exim 1.82 #2)
	id 0z7NIG-0002aG-00; Fri, 14 Aug 1998 11:05:36 -0600
Received: from ad.doubleclick.net (unverified [207.173.26.19]) by sam.parlant.com
 (EMWAC SMTPRS 0.83) with SMTP id <B0000062203@sam.parlant.com>;
 Fri, 14 Aug 1998 11:05:51 -0600
Message-ID: <B0000062203@sam.parlant.com>
From: "Eric Jorgensen" <ericj@parlant.com>
To: "alhaz@xmission.com" <alhaz@xmission.com>
Date: Fri, 14 Aug 98 11:05:54 +0700
Reply-To: "Eric Jorgensen" <ericj@parlant.com>
Priority: Normal
X-Mailer: PMMail 1.92 Evaluation Version For OS/2 (Unregistered)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: MIPS Magnum 4000 history from a faq - apocraphal? 
Sender: alhaz@xmission.com
Content-Length: 3532
Lines: 57

Gregory Shippen on c.s.m writes; First a little history. The secret, I
guess, regarding the Magnum was that the MIPS/SGI Magnum 4000PC/SC systems
were originally designed by engineers at Microsoft.  The design was later
purchased by MIPS Computer Systems (before their merger with SGI).  It was
chosen over an internal R4000-based workstation design that was well along
at the time.  The decision was based mostly on the fact that Microsoft had
already done the NT driver support for their design (code named Jazz) and
MIPS didn't wish to invest the resources necessary to write the necessary
HAL and drivers for their internal design if there was already an R4000
design around at Microsoft.  It also didn't help that the internal
workstation design used the DEC Turbochannel expansion bus rather than the
EISA bus used in Jazz and was something like six months later than than the
Microsoft design. 

The decision to scrap the internal design was an agonizing one for all
involved.  Until the R4000, all other MIPS processors had been brought up
on internally designed MIPS systems.  The R4000 turned out to be the first
(and last) to be initially powered on with systems designed out-of-house.
The internal workstation design was originally intended to be the bring-up
vehicle for the R4000 (the project was code named Aftershock -- after
several smaller Silicon Valley earthquakes that occured in the years before
the 1989 Loma Prieta earthquake).  Unfortunately, the design team, in
retrospect, picked the wrong expansion bus and was later to the finish line
than the lean-and-mean (and not thinking about high-volume) Microsoft team.

Once the design was purchased from Microsoft, a number of logic and
mechanical changes were made to make the design volume shippable.  (The
original design was intended to be a low-volume platform for internal code
developement only.) The only significant architectural change was to
completely redesign the audio subsystem (that was my job :-).  The only
other significant change was to tweak the ASIC set in order to support the
R4000SC with secondary cache (the original Microsoft design only supported
the R4000PC).  All other changes were minor component changes, a relayout
of the board, and significant changes to the mechanical design.

With the design rights owned by MIPS, RISC/os was ported to the machine
running in big-endian mode.  The Magnum is the only machine ever built to
my knowledge that was truly bi-endian. Indeed the two OSes supported used
different endiannesses.  The machine, on power-up, was little-endian.  If
the boot PROM was detected to be RISC/os, the machine reset itself and
switched to big-endian. If it detected a little-endian NT ARC prom, it
remained in little-endian and simply jumped to the PROM code.

Essentially, Windows NT was written on MIPS R4000 machines (no suprise here
-- this has been somewhat general knowledge).  What wasn't generally known
was that the R4000 hardware on which the code development was done was
designed by Microsoft themselves and not MIPS.  Later, after the Magnum was
shipped, Microsoft bought many of them to replace their then aging original
Jazz hardware.

Surprisingly, I believe that until NEC and later NeTPower designd MP
R4000MC systems, virtually all MIPS-based NT machines derived from this
original Microsoft design.  This included machines from MIPS, NEC, Olivetti
and Carrera. The only single-processor design which booted NT I know of not
derived from the original Microsoft design was Deskstation...



From kristoff.bonne@belbone.net  Fri Aug 14 13:44:38 1998
Received: from mail.belbone.be (mail.belbone.be [195.13.1.3]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id NAA05378; Fri, 14 Aug 1998 13:44:36 +0200 (MET DST)
Received-Date: Fri, 14 Aug 1998 13:44:36 +0200 (MET DST)
Received: from jupiler.belbone.be (unknown-1-182.belbone.be [195.13.1.182])
	by mail.belbone.be (8.8.8/8.8.8) with ESMTP id NAA11287;
	Fri, 14 Aug 1998 13:44:01 +0200 (MET DST)
Received: from jupiler.belbone.be (jupiler.belbone.be [192.168.1.182])
	by jupiler.belbone.be (8.8.5/8.8.5) with SMTP id NAA00504;
	Fri, 14 Aug 1998 13:44:21 +0200 (MET DST)
Message-Id: <199808141144.NAA00504@jupiler.belbone.be>
Date: Fri, 14 Aug 1998 13:44:21 +0200 (MET DST)
From: Kristoff Bonne <kristoff.bonne@belbone.net>
Reply-To: Kristoff Bonne <kristoff.bonne@belbone.net>
Subject: Re: help cross-compiling MIPS-kernel on i386 linux
To: ralf@uni-koblenz.de
Cc: linux-mips@fnet.fr
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Cdb2+q0qMY4K3brwaq5trg==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4m sparc 
Content-Length: 2650
Lines: 80

Hallo!


> From: ralf@uni-koblenz.de
> Date: Thu, 13 Aug 1998 02:07:29 +0200
> To: Kristoff Bonne <kristoff.bonne@belbone.net>, linux-mips@fnet.fr
> Subject: Re: help cross-compiling MIPS-kernel on i386 linux

>> This is the first time I try to cross-compile a linux-kernel, so this may be 
a stupid 
>> question, but I'll ask it anyway.

> This happens because you don't have the crossbinutils installed at all or
> you have them in a place where gcc doesn't find as.

> Seems you took the binaries and moved everything that should be in /usr/
> to /home/kristoff/MIPS_linux/usr/?  That won't work, the compiler driver
> mips-linux-gcc knows where it is supposed to search for the other compiler
(cut)

Yep. That's it.
I've re-installed the mipsel-gcc in the right directory, and -indead- it seams 
to work OK now. (Althou I did need to set up some additional sym-links)

Anycase, I've managed to get the kernel compiled, and this is the result on my 
personal decstation 5000/33.

--- cut here --- cut here --- cut here ---
>>boot 3/rz2/vmlinux

Ultrixboot - V4.5  Thu Sep 14 07:07:42 EDT 1995

Loading 3/rz2/vmlinux ...

Sizes:
text = 997392
data = 11904
bss  = 102992
Starting at 0x802f25a0

Linux/MIPS DECstation Boot
Copyright (C) Paul M. Antoine 1995, 1996, 1997
and others, 1994, 1995, 1996, 1997, 1998

Found a REX compatible boot PROM
This DECStation is a Personal DS5000/xx with 16384kB RAM
CPU is a R3000A with 64kB I-Cache and 128kB D-Cache
Got the following for the console env. variable: s
Should set to serial console...
Will be using PROM console!
Moving Kernel Image from 80200000 to 80030000
Launching Kernel ...

Loading R[23]00 MMU routines.
Linux version 2.1.99 (kristoff@fortuna.belbone.be) (gcc version 2.7.2) #4 Fri 
Aug 14 13:08:57 CEST 1998
Calibrating delay loop... 32.90 BogoMIPS
Memory: 14916k/16380k available (880k kernel code, 380k data)
Swansea University Computer Society NET3.039 for Linux 2.1
NET3: Unix domain sockets 0.16 for Linux NET3.038.
Swansea University Computer Society TCP/IP for NET3.037
IP Protocols: ICMP, UDP, TCP
Checking for 'wait' instruction...  unavailable.
POSIX conformance testing by UNIFIX
TURBOchannel rev. 1 at 12.5 MHz (no parity)
Starting kswapd v 1.5 
Ramdisk driver initialized : 16 ramdisks of 4096K size
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
--- cut here --- cut here --- cut here ---


Next thing. Study the kernel-source!


Cheerio! Kr. Bonne.
--
Bonne Kristoff                              belgacom multimedia
(C=BE,A=RTT,P=RTTIPC,S=BONNE,G=Kristoff)    operations belbone
Kristoff.bonne@belbone.net                  fax: +32 2 2024123

From rajko@mech.math.msu.su  Fri Aug 14 14:16:50 1998
Received: from mech.math.msu.su (mech.math.msu.su [158.250.33.65]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id OAA06057; Fri, 14 Aug 1998 14:16:48 +0200 (MET DST)
Received-Date: Fri, 14 Aug 1998 14:16:48 +0200 (MET DST)
Received: (from rajko@localhost) by mech.math.msu.su (8.6.10/8.6.10/sasha.040695) id QAA00765; Fri, 14 Aug 1998 16:16:44 +0400
Date: Fri, 14 Aug 1998 16:16:44 +0400 (MSD)
From: "Gleb O. Rajko" <rajko@mech.math.msu.su>
To: linux-mips@fnet.fr
Subject: Linux 2.1.100 on MIPS R3000 VME box
Message-ID: <Pine.SV4.3.91.980814160455.592A@mech>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 926
Lines: 25

Hi Linux Mipsers,

Recently, we (me and my collegue) got linux 2.1.100 working on R3000 VME box.
Now, we are able to run user processes and starting to compile RedHat 
packages. 

The port isn't completed yet and many things should be rewritten in some 
manner but at least the kernel lives. I guess it might be helpful to make 
sources available for developers of Linux for DECstation right now, so 
they work may have some progress.

The only thing that bothers me is that our box likes big endian (strictky 
spaking the booter in our box recognizes big endian elf) but I things it 
shouldn't be a great problem.

Well, the way are
1. To put the patch to 2.1.100 on the net
2. Merge some things from DECstation development (so I need the latest 
sources) and put the patch on the net
3. Polish the code and then put the patch

Feel free to touch me and tell what is the best way and how we could help.

Regards,
Gleb Raiko.

From adevries@engsoc.carleton.ca  Fri Aug 14 14:55:14 1998
Received: from lager.engsoc.carleton.ca (adevries@lager.engsoc.carleton.ca [134.117.69.26]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id OAA07593; Fri, 14 Aug 1998 14:55:12 +0200 (MET DST)
Received-Date: Fri, 14 Aug 1998 14:55:12 +0200 (MET DST)
Received: from localhost (adevries@localhost)
	by lager.engsoc.carleton.ca (8.8.7/8.8.7) with SMTP id IAA04639
	for <linux-mips@fnet.fr>; Fri, 14 Aug 1998 08:55:01 -0400
X-Authentication-Warning: lager.engsoc.carleton.ca: adevries owned process doing -bs
Date: Fri, 14 Aug 1998 08:55:01 -0400 (EDT)
From: Alex deVries <adevries@engsoc.carleton.ca>
To: linux-mips@fnet.fr
Subject: Re: Linux 2.1.100 on MIPS R3000 VME box
In-Reply-To: <Pine.SV4.3.91.980814160455.592A@mech>
Message-ID: <Pine.LNX.3.95.980814085221.4331A-100000@lager.engsoc.carleton.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 700
Lines: 20


On Fri, 14 Aug 1998, Gleb O. Rajko wrote:
> The only thing that bothers me is that our box likes big endian (strictky 
> spaking the booter in our box recognizes big endian elf) but I things it 
> shouldn't be a great problem.

Hey!  Another big endian MIPS architecture!

Actually, you should have an easier time than you think, because the SGI
Indy port is big endian already.  If you have a look around
ftp://ftp.linux.sgi.com/pub/manhattan or similiar, you should see large
chunks of RH 5.1 RPMs there.  We even have an installer, although it
depends on a certain kernel so it won't work yet.

We should _definitely_ get your architecture merged into the install
programs.  

Very cool!

- Alex

From rajko@mech.math.msu.su  Fri Aug 14 15:31:32 1998
Received: from mech.math.msu.su (mech.math.msu.su [158.250.33.65]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id PAA08607; Fri, 14 Aug 1998 15:31:22 +0200 (MET DST)
Received-Date: Fri, 14 Aug 1998 15:31:22 +0200 (MET DST)
Received: (from rajko@localhost) by mech.math.msu.su (8.6.10/8.6.10/sasha.040695) id RAA01433; Fri, 14 Aug 1998 17:31:18 +0400
Date: Fri, 14 Aug 1998 17:31:18 +0400 (MSD)
From: "Gleb O. Rajko" <rajko@mech.math.msu.su>
To: linux-mips@fnet.fr
Subject: Re: Linux 2.1.100 on MIPS R3000 VME box
In-Reply-To: <Pine.LNX.3.95.980814085221.4331A-100000@lager.engsoc.carleton.ca>
Message-ID: <Pine.SV4.3.91.980814172119.1222B-100000@mech>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 789
Lines: 21



On Fri, 14 Aug 1998, Alex deVries wrote:
 
> Actually, you should have an easier time than you think, because the SGI
> Indy port is big endian already.  If you have a look around
> ftp://ftp.linux.sgi.com/pub/manhattan or similiar, you should see large
> chunks of RH 5.1 RPMs there.  We even have an installer, although it
> depends on a certain kernel so it won't work yet.
> 

Unfortunately, RPMs can't help me I guess. I've got r3000 so need to 
compile from sources. Well. perhaps, not everything but at least glibc 
(and port it to r3000, fortunately, we've done it already w/o fpu 
support) and several other tools.

I can't find SRPMSes for mips, ftp sites referenced from www.lena.fr 
don't contain SRPMSes. If I'll get sources it'll be great. Are there such 
a place ?

Gleb.

From adevries@engsoc.carleton.ca  Fri Aug 14 15:43:39 1998
Received: from lager.engsoc.carleton.ca (adevries@lager.engsoc.carleton.ca [134.117.69.26]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id PAA09110; Fri, 14 Aug 1998 15:43:37 +0200 (MET DST)
Received-Date: Fri, 14 Aug 1998 15:43:37 +0200 (MET DST)
Received: from localhost (adevries@localhost)
	by lager.engsoc.carleton.ca (8.8.7/8.8.7) with SMTP id JAA07005
	for <linux-mips@fnet.fr>; Fri, 14 Aug 1998 09:43:33 -0400
X-Authentication-Warning: lager.engsoc.carleton.ca: adevries owned process doing -bs
Date: Fri, 14 Aug 1998 09:43:33 -0400 (EDT)
From: Alex deVries <adevries@engsoc.carleton.ca>
To: linux-mips@fnet.fr
Subject: Re: Linux 2.1.100 on MIPS R3000 VME box
In-Reply-To: <Pine.SV4.3.91.980814172119.1222B-100000@mech>
Message-ID: <Pine.LNX.3.95.980814093818.4331B-100000@lager.engsoc.carleton.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1249
Lines: 29


On Fri, 14 Aug 1998, Gleb O. Rajko wrote:
> Unfortunately, RPMs can't help me I guess. I've got r3000 so need to 
> compile from sources. Well. perhaps, not everything but at least glibc 
> (and port it to r3000, fortunately, we've done it already w/o fpu 
> support) and several other tools.

Hmmm.  How different are R3ks in comparison to R4ks?  I was under the
impression they were binary compatible.

If a different glibc is all you need, you're all set.  That should be an
easy fix to the glibc source rpm, which is on ftp.linux.sgi.com.

> I can't find SRPMSes for mips, ftp sites referenced from www.lena.fr
> don't contain SRPMSes. If I'll get sources it'll be great. Are there
> such a place ? 

For mips_EB_, I'd look more at ftp.linux.sgi.com.  I think we're a little
more complete than the mips_EL_ folks, and with the byte order thing
you'll have more in common.  In many ways it's too bad that the byte order
thing has seperated the MIPS ports so much.

For the sake of ensuring that your port follows a larger architecture
mass, it's wise to merge up with another port if at all possible.

It occurs to me that I haven't put all the source rpms in one easy to find
spot on ftp.linux.sgi.com... I'll do that over the weekend.

- Alex

From rajko@mech.math.msu.su  Fri Aug 14 16:57:47 1998
Received: from mech.math.msu.su (mech.math.msu.su [158.250.33.65]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id QAA09926; Fri, 14 Aug 1998 16:57:45 +0200 (MET DST)
Received-Date: Fri, 14 Aug 1998 16:57:45 +0200 (MET DST)
Received: (from rajko@localhost) by mech.math.msu.su (8.6.10/8.6.10/sasha.040695) id SAA02246; Fri, 14 Aug 1998 18:57:37 +0400
Date: Fri, 14 Aug 1998 18:57:37 +0400 (MSD)
From: "Gleb O. Rajko" <rajko@mech.math.msu.su>
To: linux-mips@fnet.fr
Subject: Re: Linux 2.1.100 on MIPS R3000 VME box
In-Reply-To: <Pine.LNX.3.95.980814093818.4331B-100000@lager.engsoc.carleton.ca>
Message-ID: <Pine.SV4.3.91.980814182836.1948B-100000@mech>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1121
Lines: 28



On Fri, 14 Aug 1998, Alex deVries wrote:
 
> Hmmm.  How different are R3ks in comparison to R4ks?  I was under the
> impression they were binary compatible.
backward only. For example, gcc likes to optimize access and uses double 
word load/store instructions until you specify -mips1. I don't know how many
binaries have it inside. I am afraid, almost all.

> 
> For the sake of ensuring that your port follows a larger architecture
> mass, it's wise to merge up with another port if at all possible.
> 
I don't thing somebody interested in entire port, because it's a quite 
specific machine which developed and produced in Russia. It has VME bus 
that is controlled by VIC068/VAC068 chips. Only thing that comes 
in mind is it's might help to port Linux to VME-based boards with a MIPS CPU.
There should be a lot such machines in the world... Anyway, I prefer to 
polish our code before posting a patch if nobody is interested to look at 
code soon. 

> It occurs to me that I haven't put all the source rpms in one easy to find
> spot on ftp.linux.sgi.com... I'll do that over the weekend.
> 
Great, thanks.

Gleb.

From nec10@admin.cam.ac.uk  Fri Aug 14 17:38:38 1998
Received: from mauve.csi.cam.ac.uk (exim@mauve.csi.cam.ac.uk [131.111.8.38]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA10115; Fri, 14 Aug 1998 17:38:37 +0200 (MET DST)
Received-Date: Fri, 14 Aug 1998 17:38:37 +0200 (MET DST)
Received: from gate.admin.cam.ac.uk ([131.111.150.210])
	by mauve.csi.cam.ac.uk with smtp (Exim 1.92 #1)
	for linux-mips@fnet.fr
	id 0z7Lw1-0007mj-00; Fri, 14 Aug 1998 16:38:33 +0100
Received: by gate.admin.cam.ac.uk; (5.65v3.2/1.3/10May95) id AA20569; Fri, 14 Aug 1998 16:38:33 +0100
Received: from somewhere by smtpxd
X-Lotus-Fromdomain: CENTRAL-ADMIN
From: "Nick E Cole"<nec10@admin.cam.ac.uk>
To: linux-mips@fnet.fr
Message-Id: <80256660.00550B2D.00@homer.internal.admin.cam.ac.uk>
Date: Fri, 14 Aug 1998 16:38:12 +0100
Subject: DecStation 3100
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Length: 540
Lines: 15




Myself and a colleague have been given colour Decstation 3100s. They appear
to be set-up to boot from the network at the moment (i.e. they fail). They
have one internal 100MB disk (rz-something) and no floppy. I'm interested
in getting Linux onto the machine if it's available. In terms of helper
machines, I have only NT/95/OS2 boxes, is it likely that I can install it
using one of these machines ? I'm not a programmer, but have had some
experience of UNIX box fiddling before (Torch TripleX).

Any ideas/help appreciated

Nick Cole


From harald.koerfgen@netcologne.de  Fri Aug 14 17:59:26 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA10710; Fri, 14 Aug 1998 17:59:23 +0200 (MET DST)
Received-Date: Fri, 14 Aug 1998 17:59:23 +0200 (MET DST)
Received: from franz.no.dom (dial3-136.netcologne.de [194.8.196.136])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id RAA15754
	for <linux-mips@fnet.fr>; Fri, 14 Aug 1998 17:59:15 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980814180028.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.SV4.3.91.980814182836.1948B-100000@mech>
Date: Fri, 14 Aug 1998 18:00:28 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: Re: Linux 2.1.100 on MIPS R3000 VME box
Content-Length: 4032
Lines: 116

Hi,

On 14-Aug-98 Gleb O. Rajko wrote:
> 
> 
> On Fri, 14 Aug 1998, Alex deVries wrote:
>  
>> Hmmm.  How different are R3ks in comparison to R4ks?  I was under the
>> impression they were binary compatible.
> backward only. For example, gcc likes to optimize access and uses double 
> word load/store instructions until you specify -mips1. I don't know how many
> binaries have it inside. I am afraid, almost all.

Well, I haven't had the chance yet to prove if this is true, but I think you
may be interested in what Ralf told me about this:

On 05-Mar-98 ralf@uni-koblenz.de wrote:
> Thought this might as well be interesting to other as well, so I copy this
> to the usual lists.
> 
> On Thu, Mar 05, 1998 at 08:29:51PM +0100, Harald Koerfgen wrote:
> 
>> BTW Eine Sache, die ich schon immer wissen wollte, aber nie zu fragen wagte:
>> 
>> Wie sieht das eigentlich mit der CPU-Abhaengigkeit der glibc aus?
>> 
>> Ich habe gerade damit anfgefangen, mich mit dem Ramdisk-Support fuer
>> linux/MIPS zu
>> beschaeftigen und moechte spaeter einmal ein Ramdisk-Image zum Kernel-Image
>> dazulinken, welches als root gemountet werden soll. Auf diesem moechte ich
>> eine
>> statisch gelinkte bash unterbringen. Meine eigentliche Frage ist nun, wuerde
>> das mit
>> der existierenden glibc funktionieren, oder muesste ich eine
>> R3000-spezifische glibc
>> bauen?
> 
> All the published userland binaries have been compiled using MIPS ISA 1.  The
> sole exception is glibc.  As it is usual for Linux, the MIPS binaries of
> glibc have been built using the three add-ons crypt, localedata and
> linuxthreads.  In order to be threadsafe LinuxThreads has to use some kind of
> semaphores etc..  Since it is the natural way of doing things for R6000 and
> better, I choose to implement this using the ll and sc instructions.
> 
> For the members of the MIPS CPU family which are lacking these two
> instructions I suggest to simulate them in the reserved instruction handler.
> This will work for all uniprocessor systems and using the special hardware
> which is part of old R2000/R3000 systems it would even be SMP proof - if
> we ever do R3000 SMP ...  It wouldn't be interrupt safe as well.
> 
> The implementation could roughly look like:
> 
> unsigned long ll_bit, lladdr;
> 
> void simulate_ll(struct pt_regs *regs)
> {
>       unsigned long addr;
> 
>       /*
>        * analyse the ll instruction that just caused a ri exception
>        * and put the referenced address to addr.
>        */
>       [...]
>       
>       lladdr = addr;
>       ll_bit = 1;
>       regs[reg_to_be_loaded] = *addr;
> }
> 
> void simulate_sc(struct pt_regs *regs)
> {
>       /*
>        * analyse the ll instruction that just caused a ri exception
>        * and put the referenced address to addr.
>        */
>       [...]
> 
>       lladdr = addr;
> 
>       if (ll_bit = 0) {
>               regs[reg_to_be_stored] = 0;
>               return;
>       }
> 
>       *addr = regs[reg_to_be_loaded];
>       regs[reg_to_be_loaded] = 1;
> }
> 
> The scheduler would have to clear ll_bit on every context switch in order
> to take care of shared memory and threads sharing their mm_struct.
> 
> There are for shure better ways of doing this, but this implementation would
> keep the 100% binary compatibility.  The way not to do it is to use
> sysmips(MIPS_ATOMIC_SET, ...) syscall which would result in the full
> syscall overhead.  Even though Linux's is way less than RISC/OS's ...
> 
>   Ralf
[end of Ralfs mail]

> I don't thing somebody interested in entire port, because it's a quite 
> specific machine which developed and produced in Russia. It has VME bus 
> that is controlled by VIC068/VAC068 chips. Only thing that comes 
> in mind is it's might help to port Linux to VME-based boards with a MIPS CPU.
> There should be a lot such machines in the world... Anyway, I prefer to 
> polish our code before posting a patch if nobody is interested to look at 
> code soon. 

Well, I am :-).

> Great, thanks.
> 
> Gleb.

---
Regards,
Harald

From harald.koerfgen@netcologne.de  Fri Aug 14 17:59:23 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA10708; Fri, 14 Aug 1998 17:59:22 +0200 (MET DST)
Received-Date: Fri, 14 Aug 1998 17:59:22 +0200 (MET DST)
Received: from franz.no.dom (dial3-136.netcologne.de [194.8.196.136])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id RAA15762
	for <linux-mips@fnet.fr>; Fri, 14 Aug 1998 17:59:18 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980814180031.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.SV4.3.91.980814160455.592A@mech>
Date: Fri, 14 Aug 1998 18:00:31 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: RE: Linux 2.1.100 on MIPS R3000 VME box
Content-Length: 1818
Lines: 50

Hi all,

On 14-Aug-98 Gleb O. Rajko wrote:
> Hi Linux Mipsers,
> 
> Recently, we (me and my collegue) got linux 2.1.100 working on R3000 VME box.
> Now, we are able to run user processes and starting to compile RedHat 
> packages. 

Congratulations!
 
> The port isn't completed yet and many things should be rewritten in some 
> manner but at least the kernel lives. I guess it might be helpful to make 
> sources available for developers of Linux for DECstation right now, so 
> they work may have some progress.

We have the first user process running too :-). Just beeing curious, have you
used code from DECstation-Linux or have you hacked the R3000 support
independantly?

> The only thing that bothers me is that our box likes big endian (strictky 
> spaking the booter in our box recognizes big endian elf) but I things it 
> shouldn't be a great problem.
> 
> Well, the way are
> 1. To put the patch to 2.1.100 on the net
> 2. Merge some things from DECstation development (so I need the latest 
> sources) and put the patch on the net
> 3. Polish the code and then put the patch
> 
> Feel free to touch me and tell what is the best way and how we could help.

Well, I am very interested to have a look at your code, please publish it as
soon as you can. Ralf has agreed that the DECstation code is clean enough to be
commited into the CVS repository. I may as well have overlooked something
or you simply have the better ideas...

I have sent DECstation-linux-2.1.100 to Michael Engel three weeks ago.
Unfortunately the source tree hasn't made it to the DECstation Webpages and I
haven't reached Michael via email so DECstation-linux-2.1.100 isn't available
for download. Nevertheless you may want to have a look at
http://decstation.unix-ag.org.

> Regards,
> Gleb Raiko.

Keep hacking.
---
Regards,
Harald

From narayh@taec.toshiba.com  Sat Aug 15 01:54:50 1998
Received: from godzilla.taec.com (godzilla.taec.com [204.162.152.130]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id BAA19950; Sat, 15 Aug 1998 01:54:49 +0200 (MET DST)
Received-Date: Sat, 15 Aug 1998 01:54:49 +0200 (MET DST)
Received: from mailint.taec.com by godzilla.taec.com
          via smtpd (for guadalquivir.fnet.fr [193.104.112.133]) with SMTP; 14 Aug 1998 23:54:17 UT
Received: from super.sanjose (super.taec.com [198.232.207.62])
	by mailhost.taec.com (8.8.8/8.8.8) with SMTP id QAA08247
	for <linux-mips@fnet.fr>; Fri, 14 Aug 1998 16:54:16 -0700 (PDT)
Received: by super.sanjose (SMI-8.6/SMI-SVR4)
	id QAA29515; Fri, 14 Aug 1998 16:54:16 -0700
From: narayh@taec.toshiba.com (Hari Narayanan)
Message-Id: <199808142354.QAA29515@super.sanjose>
Subject: Please add me to the waiting list.
To: linux-mips@fnet.fr
Date: Fri, 14 Aug 1998 16:54:16 -0700 (PDT)
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Content-Length: 122
Lines: 11

Hi 

Can you please add me to this mailing list ?.

Name : Hari Narayanan
email : narayh@taec.toshiba.com



Thanks
Hari.

From tsbogend@alpha.franken.de  Sun Aug 16 03:47:31 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id DAA01104; Sun, 16 Aug 1998 03:47:31 +0200 (MET DST)
Received-Date: Sun, 16 Aug 1998 03:47:31 +0200 (MET DST)
Received: from alpha.franken.de (tsbogend@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id DAA14716; Sun, 16 Aug 1998 03:47:28 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id DAA02489;
	Sun, 16 Aug 1998 03:44:54 +0200
Message-ID: <19980816034454.28961@alpha.franken.de>
Date: Sun, 16 Aug 1998 03:44:54 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@fnet.fr
Subject: Sonic rocks
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
Content-Length: 411
Lines: 10

I've finaly got some time to fix the Sonic driver. I found two really
stupid bugs, and fixed the race I've found last year and didn't manage
to fix it then. Performance is quite good (1MByte/s both directions).

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From ralf@uni-koblenz.de  Sun Aug 16 23:40:11 1998
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA09641; Sun, 16 Aug 1998 23:40:10 +0200 (MET DST)
Received-Date: Sun, 16 Aug 1998 23:40:10 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from uni-koblenz.de (pmport-19.uni-koblenz.de [141.26.249.19])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id XAA13040;
	Sun, 16 Aug 1998 23:39:51 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id WAA03195;
	Sun, 16 Aug 1998 22:15:14 +0200
Message-ID: <19980816221514.B3128@uni-koblenz.de>
Date: Sun, 16 Aug 1998 22:15:14 +0200
To: Dominic Sweetman <dom@algor.co.uk>, linux-mips@fnet.fr
Subject: Re: ISA audio in Magnum 4000pc,possibly?
References: <35CD2CFC.32CACC90@mail.com> <19980809171312.U938@uni-koblenz.de> <35CDF934.293BB67@xmission.com> <19980811131122.B480@uni-koblenz.de> <35D09103.DB8B8DA3@xmission.com> <19980812160625.R364@uni-koblenz.de> <199808130722.IAA00236@gladsmuir.algor.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <199808130722.IAA00236@gladsmuir.algor.co.uk>; from Dominic Sweetman on Thu, Aug 13, 1998 at 08:22:15AM +0100
Content-Length: 612
Lines: 15

On Thu, Aug 13, 1998 at 08:22:15AM +0100, Dominic Sweetman wrote:

> > >     The thing is, there's no way this was a pre-release prototype
> > > of the original magnum, because the original magnum was
> > > Microsoft-designed box code-named Jazz. 
> 
> I think you may be confusing two histories here.  I think the Magnum
> all MIPS' own work, since it was related to an earlier R3000-powered
> Magnum.  Jazz was a platform for the Windows NT development at
> Microsoft, which happened some time later.

The Mips Magnum 4000 / Olivetti M700-10 machines identify themselfes as
Microsoft-Jazz machines ...

  Ralf

From kristoff.bonne@belbone.net  Mon Aug 17 10:41:03 1998
Received: from mail.belbone.be (mail.belbone.be [195.13.1.3]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id KAA15900; Mon, 17 Aug 1998 10:41:02 +0200 (MET DST)
Received-Date: Mon, 17 Aug 1998 10:41:02 +0200 (MET DST)
Received: from jupiler.belbone.be (unknown-1-182.belbone.be [195.13.1.182])
	by mail.belbone.be (8.8.8/8.8.8) with ESMTP id KAA28314;
	Mon, 17 Aug 1998 10:38:14 +0200 (MET DST)
Received: from jupiler.belbone.be (jupiler.belbone.be [192.168.1.182])
	by jupiler.belbone.be (8.8.5/8.8.5) with SMTP id KAA03664;
	Mon, 17 Aug 1998 10:38:29 +0200 (MET DST)
Message-Id: <199808170838.KAA03664@jupiler.belbone.be>
Date: Mon, 17 Aug 1998 10:38:29 +0200 (MET DST)
From: Kristoff Bonne <kristoff.bonne@belbone.net>
Reply-To: Kristoff Bonne <kristoff.bonne@belbone.net>
Subject: linux-2.1.100 on DS5000/33
To: linux-mips@fnet.fr
Cc: harald.koerfgen@netcologne.de
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: IfSo70NuU/bA4GAFqijHww==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4m sparc 
Content-Length: 2191
Lines: 64

Greetings,

I've just compiled the 2.1.100 kernel (as found on decstation.unix-ag.org) and 
tried it on my maxine-box.

This is the result:
--- cut here --- cut here --- cut here ---
Loading 3/rz2/vmlinux3 ...

Sizes:
text = 890752
data = 12832
bss  = 115648
Starting at 0x802d8500

Linux/MIPS DECstation Boot
Copyright (C) Paul M. Antoine 1995, 1996, 1997
and others, 1994, 1995, 1996, 1997, 1998

Found a REX compatible boot PROM
This DECStation is a Personal DS5000/xx with 16384kB RAM
CPU is a R3000A with 64kB I-Cache and 128kB D-Cache
Got the following for the console env. variable: s
Should set to serial console...
Will be using PROM console!
Moving Kernel Image from 80200000 to 80030000
Launching Kernel ...

Loading R[23]00 MMU routines.
Linux version 2.1.100 (kristoff@fortuna.belbone.be) (gcc version 2.7.2) #1 
Mon A
ug 17 09:03:03 CEST 1998
Calibrating delay loop... 32.90 BogoMIPS
Memory: 15004k/16380k available (772k kernel code, 396k data)
Swansea University Computer Society NET3.039 for Linux 2.1
NET3: Unix domain sockets 0.16 for Linux NET3.038.
Swansea University Computer Society TCP/IP for NET3.037
IP Protocols: ICMP, UDP, TCP
Checking for 'wait' instruction...  unavailable.
POSIX conformance testing by UNIFIX
TURBOchannel rev. 1 at 12.5 MHz (no parity)
Starting kswapd v 1.5 
DECstation Z8530 serial driver version 0.01
get_zsbaud: Got Bus Error at 800e1288
$0 : 00000000 80120000 b8100001 bc040288 00000000 00000001 00000000 00000000
$8 : bfc009e8 0000000d 00000001 00000001 00000000 00000000 bc100000 00000004
$16: 80120840 801208fc 8012030c 00000000 80120310 00708000 00000000 0000000a
$24: 00000020 a0000f88                   80ff2000 80ff3df8 00000009 800e122c
epc  : 800e1288
Status: 10002000
Cause : 3000181c
--- cut here --- cut here --- cut here ---

OK. I'm just trying to start to get to know the kernel-source, so I am not able 
to fix it.
(I DID managed to find to source-file that was responsable for this, not a bad 
start! ;-) )


Cheerio! Kr. Bonne.
--
Bonne Kristoff                              belgacom multimedia
(C=BE,A=RTT,P=RTTIPC,S=BONNE,G=Kristoff)    operations belbone
Kristoff.bonne@belbone.net                  fax: +32 2 2024123

From rajko@mech.math.msu.su  Mon Aug 17 12:46:37 1998
Received: from mech.math.msu.su (mech.math.msu.su [158.250.33.65]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id MAA17292; Mon, 17 Aug 1998 12:46:33 +0200 (MET DST)
Received-Date: Mon, 17 Aug 1998 12:46:33 +0200 (MET DST)
Received: (from rajko@localhost) by mech.math.msu.su (8.6.10/8.6.10/sasha.040695) id OAA01386; Mon, 17 Aug 1998 14:46:29 +0400
Date: Mon, 17 Aug 1998 14:46:28 +0400 (MSD)
From: "Gleb O. Rajko" <rajko@mech.math.msu.su>
To: linux-mips@fnet.fr
Subject: RE: Linux 2.1.100 on MIPS R3000 VME box
In-Reply-To: <XFMail.980814180031.harald.koerfgen@netcologne.de>
Message-ID: <Pine.SV4.3.91.980817142956.1313A-100000@mech>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 753
Lines: 21


Hi Harald,

On Fri, 14 Aug 1998, Harald Koerfgen wrote:

> 
> We have the first user process running too :-). Just beeing curious, have you
> used code from DECstation-Linux or have you hacked the R3000 support
> independantly?

I guessed you have it as init, so fork/exec stuff isn't tested yet. Am I  
right ? We had a lot of problem with fork/exec and signal delivering and
half of time/efforts we spent during entire port was to fix that stuff.

Independently. Unfortunately, Linux/MIPS FAQ doesn't have any links to
DECstation site. That's why, I had to pick up 2.1.100 from SGI tree
instead of 2.1.99. I am going to replace some our assembler routines by
yours because ours are worse. (We haven't experiences with MIPS 
assmebler before.)

Gleb.

From engel@numerik.math.uni-siegen.de  Mon Aug 17 13:32:39 1998
Received: from fourier.numerik.math.uni-siegen.de (fourier.numerik.math.uni-siegen.de [141.99.2.230]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id NAA17949; Mon, 17 Aug 1998 13:32:37 +0200 (MET DST)
Received-Date: Mon, 17 Aug 1998 13:32:37 +0200 (MET DST)
Received: (from engel@localhost) by fourier.numerik.math.uni-siegen.de (Mailhost) id NAA10000 for linux-mips@fnet.fr; Mon, 17 Aug 1998 13:32:34 +0200 (MET DST)
From: Michael Engel <engel@numerik.math.uni-siegen.de>
Message-Id: <199808171132.NAA10000@fourier.numerik.math.uni-siegen.de>
Subject: Re: Linux 2.1.100 on MIPS R3000 VME box
To: linux-mips@fnet.fr
Date: Mon, 17 Aug 1998 13:32:33 +0200 (MET DST)
In-Reply-To: <Pine.SV4.3.91.980817142956.1313A-100000@mech> from "Gleb O. Rajko" at Aug 17, 98 02:46:28 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 186
Lines: 8


> Independently. Unfortunately, Linux/MIPS FAQ doesn't have any links to
> DECstation site. 

Yup, sorry, I'm working on that ...

regards,
	Michael Engel	(engel@unix-ag.uni-siegen.de)

From harald.koerfgen@netcologne.de  Mon Aug 17 18:25:14 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA20169; Mon, 17 Aug 1998 18:25:11 +0200 (MET DST)
Received-Date: Mon, 17 Aug 1998 18:25:11 +0200 (MET DST)
Received: from franz.no.dom (dial2-15.netcologne.de [194.8.195.15])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id SAA13246
	for <linux-mips@fnet.fr>; Mon, 17 Aug 1998 18:25:02 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980817182616.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.SV4.3.91.980817142956.1313A-100000@mech>
Date: Mon, 17 Aug 1998 18:26:16 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: RE: Linux 2.1.100 on MIPS R3000 VME box
Content-Length: 1157
Lines: 38

Hi,

On 17-Aug-98 Gleb O. Rajko wrote:
> 
> Hi Harald,
> 
> On Fri, 14 Aug 1998, Harald Koerfgen wrote:
> 
>> 
>> We have the first user process running too :-). Just beeing curious, have
>> you
>> used code from DECstation-Linux or have you hacked the R3000 support
>> independantly?
> 
> I guessed you have it as init, so fork/exec stuff isn't tested yet. Am I  
> right ?

I wish it were so. Actually it's a little test program which writes "Hello
World" to /dev/ttyS0. I am working on a serial device driver at the moment.

> We had a lot of problem with fork/exec and signal delivering and
> half of time/efforts we spent during entire port was to fix that stuff.
> 
> Independently. Unfortunately, Linux/MIPS FAQ doesn't have any links to
> DECstation site. That's why, I had to pick up 2.1.100 from SGI tree
> instead of 2.1.99. I am going to replace some our assembler routines by
> yours because ours are worse. (We haven't experiences with MIPS 
> assmebler before.)
> 
> Gleb.

Well, that's not bad. We just have to pick the better solution when merging
our ports :-). Would you mind to send me your patches? 

Happy hacking.
---
Regards,
Harald

From harald.koerfgen@netcologne.de  Mon Aug 17 18:25:10 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA20163; Mon, 17 Aug 1998 18:25:08 +0200 (MET DST)
Received-Date: Mon, 17 Aug 1998 18:25:08 +0200 (MET DST)
Received: from franz.no.dom (dial2-15.netcologne.de [194.8.195.15])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id SAA13250
	for <linux-mips@fnet.fr>; Mon, 17 Aug 1998 18:25:04 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980817182619.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199808170838.KAA03664@jupiler.belbone.be>
Date: Mon, 17 Aug 1998 18:26:19 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: RE: linux-2.1.100 on DS5000/33
Content-Length: 1424
Lines: 51

Hi,

On 17-Aug-98 Kristoff Bonne wrote:
> Greetings,
> 
> I've just compiled the 2.1.100 kernel (as found on decstation.unix-ag.org)
> and 
> tried it on my maxine-box.
> 
> This is the result:

[snip]

> TURBOchannel rev. 1 at 12.5 MHz (no parity)
> Starting kswapd v 1.5 
> DECstation Z8530 serial driver version 0.01
> get_zsbaud: Got Bus Error at 800e1288
> $0 : 00000000 80120000 b8100001 bc040288 00000000 00000001 00000000 00000000
> $8 : bfc009e8 0000000d 00000001 00000001 00000000 00000000 bc100000 00000004
> $16: 80120840 801208fc 8012030c 00000000 80120310 00708000 00000000 0000000a
> $24: 00000020 a0000f88                   80ff2000 80ff3df8 00000009 800e122c
> epc  : 800e1288
> Status: 10002000
> Cause : 3000181c

This is supposed to happen. As I've said before, the serial device driver is
*extremely* experimental, non-functional and specific to my kmin. A temporary
fix is quite easy:

In drivers/tc/tc.c replace the line

       system_base = slot0addr + (max_tcslot + 1) * slot_size;

with
       system_base = slot0addr + 3 * slot_size;

and in drivers/tc/decserial.c (in function probe_sccs) replace the line

        for (n = 0; n <= 3; n++) {

with

        for (n = 0; n <= 1; n++) {        

You have to switch back to framebuffer console in your PROM environment
settings. Fiddling around with the scc while printing debugging messages via
the serial port is a no go :-).

---
Regards,
Harald

From grim@zigzegv.ml.org  Mon Aug 17 18:57:53 1998
Received: from calypso.saturn (grim@dialup90-1-22.swipnet.se [130.244.90.22]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA21710; Mon, 17 Aug 1998 18:57:51 +0200 (MET DST)
Received-Date: Mon, 17 Aug 1998 18:57:51 +0200 (MET DST)
Received: (from grim@localhost)
	by calypso.saturn (8.9.1/8.9.1/Debian/GNU) id SAA29305;
	Mon, 17 Aug 1998 18:57:41 +0200
From: Ulf Carlsson <grim@zigzegv.ml.org>
Message-Id: <199808171657.SAA29305@calypso.saturn>
Subject: R4[04]00SC
To: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Date: Mon, 17 Aug 1998 18:57:40 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 331
Lines: 10

Hi,

I can report that I've a R4000SC running here with Linux. After hard work
(many long hours, mainly reading MIPS Manual), the VCE exceptions are now
correctly handled. R4400SC will (probably) also work now. The next step is to
make this exceptions never happen.

Greetings to Ralf, Alex and last but not least - myself.

- Ulf

From alhaz@xmission.com  Mon Aug 17 19:19:44 1998
Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id TAA22702; Mon, 17 Aug 1998 19:19:39 +0200 (MET DST)
Received-Date: Mon, 17 Aug 1998 19:19:39 +0200 (MET DST)
Received: from alhaz.users.xmission.com (xmission.com) [207.135.128.199] (alhaz)
	by mail.xmission.com with esmtp (Exim 1.82 #2)
	id 0z8SwM-0003Tc-00; Mon, 17 Aug 1998 11:19:30 -0600
Sender: alhaz@fnet.fr
Message-ID: <35D866C5.9DC77CD7@xmission.com>
Date: Mon, 17 Aug 1998 11:22:13 -0600
From: Eric Jorgensen <alhaz@xmission.com>
X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.32 i486)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: Magnum 4000 serial console? 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 1118
Lines: 21

    My Magnum does have the framebuffer installed, but I don't yet have
a fully compatible monitor. I have a monitor that should work, but
I need to make a cable. (Sun monitor that should do the same refresh and
rez).

    So, since I've never booted my Magnum, know next to nothing about
it's background, and haven't spent the money on a 13W3 connector to
complete the cable I'm building, I'm wondering if I can boot this thing
with a serial console to see if it works. It would be disappointing to
go to all the trouble to get the video working just to find it doesn't
work at all. I did only spend $5 on it, although the $10 Dell system
I bought the same day from the same surplus sale works fine.

    Also, if it's as good at MP3 decoding as some say it should be once
the sound hardware works, i may end up sticking it in my stereo system
and just using it for that. A man can only use so many consoles at once,
and with my current network at 4 consoles plus one xterminal and one
serial terminal, it's a bit on the unnessisary side, especially if I've
found a task for it that I can controll remotely.

 - Eric

From alhaz@xmission.com  Mon Aug 17 19:29:19 1998
Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id TAA23709; Mon, 17 Aug 1998 19:29:17 +0200 (MET DST)
Received-Date: Mon, 17 Aug 1998 19:29:17 +0200 (MET DST)
Received: from alhaz.users.xmission.com (xmission.com) [207.135.128.199] (alhaz)
	by mail.xmission.com with esmtp (Exim 1.82 #2)
	id 0z8T5k-0004K9-00; Mon, 17 Aug 1998 11:29:14 -0600
Sender: alhaz@fnet.fr
Message-ID: <35D8690B.49FD228@xmission.com>
Date: Mon, 17 Aug 1998 11:31:56 -0600
From: Eric Jorgensen <alhaz@xmission.com>
X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.32 i486)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: shared-memory type ISA boards? 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 476
Lines: 10

    I have an excess video capture device, having upgraded my main
system from a Mediavision ProMovie Studio to a BT848 based board.

    Just for kicks, I was thinking it might be useful to install the
board in my Magnum. From what I understand, this is a board that uses a
range of  memory, an io port, and an irq. I'm also querying the
Video4Linux mailing list, but, in the opinion of this list, are shared
memory boards working well with linux/mips at this time?

 - Eric

From shm@cthulhu.engr.sgi.com  Mon Aug 17 19:43:26 1998
Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA24277; Mon, 17 Aug 1998 19:43:22 +0200 (MET DST)
Received-Date: Mon, 17 Aug 1998 19:43:22 +0200 (MET DST)
Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) 
	by sgi.sgi.com (980309.SGI.8.8.8-aspam-6.2/980304.SGI-aspam:
       SGI does not authorize the use of its proprietary
       systems or networks for unsolicited or bulk email
       from the Internet.) 
	via ESMTP id KAA25860; Mon, 17 Aug 1998 10:43:15 -0700 (PDT)
	mail_from (shm@cthulhu.engr.sgi.com)
Received: from tantrik.engr.sgi.com (tantrik.engr.sgi.com [130.62.245.44])
	by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF)
	via ESMTP id KAA55407;
	Mon, 17 Aug 1998 10:43:14 -0700 (PDT)
	mail_from (shm@engr.sgi.com)
Received: from localhost (shm@localhost) by tantrik.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via SMTP id KAA04017; Mon, 17 Aug 1998 10:43:14 -0700 (PDT)
Date: Mon, 17 Aug 1998 10:43:13 -0700
From: Shrijeet Mukherjee <shm@cthulhu.engr.sgi.com>
To: Ulf Carlsson <grim@zigzegv.ml.org>
cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: R4[04]00SC
In-Reply-To: <199808171657.SAA29305@calypso.saturn>
Message-ID: <Pine.SGI.4.02.9808171042570.3793-100000@tantrik.engr.sgi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1009
Lines: 29

On Mon, 17 Aug 1998, Ulf Carlsson wrote:

->Hi,
->
->I can report that I've a R4000SC running here with Linux. After hard work
->(many long hours, mainly reading MIPS Manual), the VCE exceptions are now
->correctly handled. R4400SC will (probably) also work now. The next step is to
->make this exceptions never happen.
->
->Greetings to Ralf, Alex and last but not least - myself.
->
->- Ulf
->


I have a 4400SC .. how can I try it out ?

--
--------------------------------------------------------------------------
Shrijeet Mukherjee,    			Member of Technical Staff (MTS)
					Advanced Graphics Division 
                     			Silicon Graphics Computer Systems

http://reality.sgi.com/shm_engr     	phone: 650-933-5312
email: shm@engr.sgi.com, shm@sgi.com, shrijeet@hotmail.com
--------------------------------------------------------------------------
The world fears a new experience more than it fears anything. 
	Because a new experience displaces so many old experiences. 
						-- D. H. Lawrence

From tsbogend@alpha.franken.de  Tue Aug 18 00:24:59 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA27504; Tue, 18 Aug 1998 00:24:58 +0200 (MET DST)
Received-Date: Tue, 18 Aug 1998 00:24:58 +0200 (MET DST)
Received: from alpha.franken.de (root@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id AAA23248; Tue, 18 Aug 1998 00:24:55 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id XAA02268;
	Mon, 17 Aug 1998 23:10:22 +0200
Message-ID: <19980817231021.13872@alpha.franken.de>
Date: Mon, 17 Aug 1998 23:10:21 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@fnet.fr
Subject: Re: Magnum 4000 serial console?
References: <35D866C5.9DC77CD7@xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
In-Reply-To: <35D866C5.9DC77CD7@xmission.com>; from Eric Jorgensen on Mon, Aug 17, 1998 at 11:22:13AM -0600
Content-Length: 748
Lines: 16

On Mon, Aug 17, 1998 at 11:22:13AM -0600, Eric Jorgensen wrote:
>     So, since I've never booted my Magnum, know next to nothing about
> it's background, and haven't spent the money on a 13W3 connector to
> complete the cable I'm building, I'm wondering if I can boot this thing
> with a serial console to see if it works. It would be disappointing to

It's possible. I used a serial console some time ago. But I had to
configure this with the arc firmware.  Maybe the arc firmware switches
to serial console, when doesn't find the graphics card.

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From tsbogend@alpha.franken.de  Tue Aug 18 00:25:00 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA27507; Tue, 18 Aug 1998 00:24:59 +0200 (MET DST)
Received-Date: Tue, 18 Aug 1998 00:24:59 +0200 (MET DST)
Received: from alpha.franken.de (root@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id AAA23251; Tue, 18 Aug 1998 00:24:57 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id XAA02275;
	Mon, 17 Aug 1998 23:13:56 +0200
Message-ID: <19980817231356.23255@alpha.franken.de>
Date: Mon, 17 Aug 1998 23:13:56 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@fnet.fr
Subject: Re: shared-memory type ISA boards?
References: <35D8690B.49FD228@xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
In-Reply-To: <35D8690B.49FD228@xmission.com>; from Eric Jorgensen on Mon, Aug 17, 1998 at 11:31:56AM -0600
Content-Length: 861
Lines: 18

On Mon, Aug 17, 1998 at 11:31:56AM -0600, Eric Jorgensen wrote:
>     Just for kicks, I was thinking it might be useful to install the
> board in my Magnum. From what I understand, this is a board that uses a
> range of  memory, an io port, and an irq. I'm also querying the
> Video4Linux mailing list, but, in the opinion of this list, are shared
> memory boards working well with linux/mips at this time?

I haven't tested one, but this will soon change, when I plug in my spare 
ISDN card. In theory memory mapped IO shouldn't make any problems, when the
driver is written properly (if it runs on Alphas, most of the portabilty
problems are already solved).

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From alhaz@xmission.xmission.com  Tue Aug 18 01:25:57 1998
Received: from xmission.xmission.com (alhaz@xmission.xmission.com [198.60.22.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id BAA00640; Tue, 18 Aug 1998 01:25:55 +0200 (MET DST)
Received-Date: Tue, 18 Aug 1998 01:25:55 +0200 (MET DST)
Received: (from alhaz@localhost) by xmission.xmission.com (8.8.8/8.7.5) id RAA09169 for linux-mips@fnet.fr; Mon, 17 Aug 1998 17:25:49 -0600 (MDT)
From: Eric Jorgensen <alhaz@xmission.com>
Message-Id: <199808172325.RAA09169@xmission.xmission.com>
Subject: Re: shared-memory type ISA boards?
To: linux-mips@fnet.fr
Date: Mon, 17 Aug 1998 17:25:49 -0600 (MDT)
In-Reply-To: <19980817231356.23255@alpha.franken.de> from "Thomas Bogendoerfer" at Aug 17, 98 11:13:56 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 909
Lines: 18

> 
> On Mon, Aug 17, 1998 at 11:31:56AM -0600, Eric Jorgensen wrote:
> >     Just for kicks, I was thinking it might be useful to install the
> > board in my Magnum. From what I understand, this is a board that uses a
> > range of  memory, an io port, and an irq. I'm also querying the
> > Video4Linux mailing list, but, in the opinion of this list, are shared
> > memory boards working well with linux/mips at this time?
> 
> I haven't tested one, but this will soon change, when I plug in my spare 
> ISDN card. In theory memory mapped IO shouldn't make any problems, when the
> driver is written properly (if it runs on Alphas, most of the portabilty
> problems are already solved).

	Well, the alan cox told me this board is "sortof" shared memory -
that it uses a range in the ISA memory space as a FIFO. And said that as
long as the MIPS system keeps that range uncached, it should work fine. 

 - Eric

From ralf@uni-koblenz.de  Wed Aug 19 02:43:03 1998
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id CAA19082; Wed, 19 Aug 1998 02:43:02 +0200 (MET DST)
Received-Date: Wed, 19 Aug 1998 02:43:02 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from uni-koblenz.de (pmport-26.uni-koblenz.de [141.26.249.26])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id CAA28350
	for <linux-mips@fnet.fr>; Wed, 19 Aug 1998 02:42:59 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id CAA05741;
	Tue, 18 Aug 1998 02:48:07 +0200
Message-ID: <19980818024807.O3345@uni-koblenz.de>
Date: Tue, 18 Aug 1998 02:48:07 +0200
To: Eric Jorgensen <alhaz@xmission.com>, linux-mips@fnet.fr
Subject: Re: shared-memory type ISA boards?
References: <35D8690B.49FD228@xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <35D8690B.49FD228@xmission.com>; from Eric Jorgensen on Mon, Aug 17, 1998 at 11:31:56AM -0600
Content-Length: 603
Lines: 14

On Mon, Aug 17, 1998 at 11:31:56AM -0600, Eric Jorgensen wrote:

>     I have an excess video capture device, having upgraded my main
> system from a Mediavision ProMovie Studio to a BT848 based board.
> 
>     Just for kicks, I was thinking it might be useful to install the
> board in my Magnum. From what I understand, this is a board that uses a
> range of  memory, an io port, and an irq. I'm also querying the
> Video4Linux mailing list, but, in the opinion of this list, are shared
> memory boards working well with linux/mips at this time?

Well written drivers should not need changes.

  Ralf

From rajko@mech.math.msu.su  Tue Aug 18 13:42:22 1998
Received: from mech.math.msu.su (mech.math.msu.su [158.250.33.65]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id NAA07358; Tue, 18 Aug 1998 13:38:03 +0200 (MET DST)
Received-Date: Tue, 18 Aug 1998 13:38:03 +0200 (MET DST)
Received: (from rajko@localhost) by mech.math.msu.su (8.6.10/8.6.10/sasha.040695) id PAA01295; Tue, 18 Aug 1998 15:37:46 +0400
Date: Tue, 18 Aug 1998 15:37:46 +0400 (MSD)
From: "Gleb O. Rajko" <rajko@mech.math.msu.su>
To: linux-mips@fnet.fr
Subject: RE: Linux 2.1.100 on MIPS R3000 VME box
In-Reply-To: <XFMail.980817182616.harald.koerfgen@netcologne.de>
Message-ID: <Pine.SV4.3.91.980818153015.1184A-100000@mech>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 76
Lines: 5

I've put the patch at 

http://www.math.msu.su/~rajko/baget.patch.gz

Gleb.

From timp@redac.co.uk  Tue Aug 18 17:18:27 1998
Received: from redac.co.uk (mail.redac.co.uk [195.99.246.2]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id RAA10711; Tue, 18 Aug 1998 17:18:26 +0200 (MET DST)
Received-Date: Tue, 18 Aug 1998 17:18:26 +0200 (MET DST)
Received: from redpo by redac.co.uk (5.0/SMI-SVR4)
	id AA15092; Tue, 18 Aug 1998 16:16:18 +0000
Received: from linbar.aztec by redpo (SMI-8.6/Redac-Interior-Gateway-V1.1)
	id QAA11076; Tue, 18 Aug 1998 16:18:59 +0100
Received: by linbar.aztec (SMI-8.6/SMI-SVR4)
	id QAA08248; Tue, 18 Aug 1998 16:13:30 +0100
From: Tim Parker <timp@redac.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 18 Aug 1998 16:13:27 +0100 (BST)
To: linux-mips@fnet.fr
Subject: DECStation memory
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-Id: <13785.36764.245026.525250@linbar>
Organization: Redac Systems Limited
Content-Length: 1242
Lines: 29


Greetings,

Just a (hopefully) quick question. Are the memory modules from the
VAXStation series (think it was a 3100) compatible with the DECStation
5K/200s ? These are 80-pin 16MB SIMM modules I believe, can't say more
at the moment as there aren't here. Looking at some of the archives it
seems there were two 'kit' memory setups (2 piece or 4 piece which I
was presuming was to do with the interleaving ??) and one module
(MS44-AA) setup for the VAXStation model 76 (4MB) but nothing that
quite matches. The pin layout, data path/bit counts seem to be OK but
thats not exactly saying that much. Any ideas / comments ?


TIA Tim
-- 
------------------------------------------------------------------------
Tim Parker,				Leading Software Engineer
Redac Systems Ltd.,			Tel   : +44 (1454) 207800
Zuken-Redac R&D Centre,			Fax   : +44 (1454) 207803
1500 Aztec West, Almondsbury,		Email : timp@redac.co.uk
Bristol, England, BS32 4RF.		Web   : http://www.redac.co.uk
"Any opinions are mine, and mine alone. They do not reflect
 reality let alone this company"
------------------------------------------------------------------------

"In a word -- im-possible!"
"That's two words," said Dibbler.
        -- (Terry Pratchett, Moving Pictures)

From afritz@iname.com  Tue Aug 18 18:58:27 1998
Received: from pop01.globecomm.net (pop01.globecomm.net [206.253.129.185]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA11609; Tue, 18 Aug 1998 18:58:26 +0200 (MET DST)
Received-Date: Tue, 18 Aug 1998 18:58:26 +0200 (MET DST)
Received: from usr01.primenet.com (usr01.primenet.com [206.165.6.201]) by pop01.globecomm.net (8.9.0/8.8.0) with SMTP id MAA25907 for <linux-mips@fnet.fr>; Tue, 18 Aug 1998 12:58:04 -0400 (EDT)
Date: Tue, 18 Aug 1998 09:58:22 -0700 (MST)
From: Adam Fritzler <afritz@iname.com>
X-Sender: afritz@usr01.primenet.com
To: linux-mips@fnet.fr
Subject: Re: DECStation memory
In-Reply-To: <13785.36764.245026.525250@linbar>
Message-ID: <Pine.BSI.3.96.980818095558.6656A-100000@usr01.primenet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 2160
Lines: 53


I've never seen a VS3100 newer than a m38 (which all use custom memory
cards).  But, AFAIK, the DS5k SIMMs were very specific to the DECstation
series.  Judging by the model numbers, I'd say they were not compatible.
But, I'm not an expert at this...  I think the proper numbers are MS01-AA
or something around there.

af

On Tue, 18 Aug 1998, Tim Parker wrote:

> 
> Greetings,
> 
> Just a (hopefully) quick question. Are the memory modules from the
> VAXStation series (think it was a 3100) compatible with the DECStation
> 5K/200s ? These are 80-pin 16MB SIMM modules I believe, can't say more
> at the moment as there aren't here. Looking at some of the archives it
> seems there were two 'kit' memory setups (2 piece or 4 piece which I
> was presuming was to do with the interleaving ??) and one module
> (MS44-AA) setup for the VAXStation model 76 (4MB) but nothing that
> quite matches. The pin layout, data path/bit counts seem to be OK but
> thats not exactly saying that much. Any ideas / comments ?
> 
> 
> TIA Tim
> -- 
> ------------------------------------------------------------------------
> Tim Parker,				Leading Software Engineer
> Redac Systems Ltd.,			Tel   : +44 (1454) 207800
> Zuken-Redac R&D Centre,			Fax   : +44 (1454) 207803
> 1500 Aztec West, Almondsbury,		Email : timp@redac.co.uk
> Bristol, England, BS32 4RF.		Web   : http://www.redac.co.uk
> "Any opinions are mine, and mine alone. They do not reflect
>  reality let alone this company"
> ------------------------------------------------------------------------
> 
> "In a word -- im-possible!"
> "That's two words," said Dibbler.
>         -- (Terry Pratchett, Moving Pictures)
> 
> 




-------------------------------------------------------------------------------
Adam Fritzler                           |
  afritz@delphid.ml.org                 | Animals who are not penguins can   
    afritz@iname.com                    |    can only wish they were.
      http://delphid.ml.org/~afritz/    |        -- Chicago Reader 
        http://www.pst.com/             |               15 Oct 1982
-------------------------------------------------------------------------------

From harald.koerfgen@netcologne.de  Tue Aug 18 20:26:34 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id UAA12460; Tue, 18 Aug 1998 20:26:33 +0200 (MET DST)
Received-Date: Tue, 18 Aug 1998 20:26:33 +0200 (MET DST)
Received: from franz.no.dom (dial6-84.netcologne.de [194.8.196.84])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id UAA22608;
	Tue, 18 Aug 1998 20:26:22 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980818202736.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <199808171657.SAA29305@calypso.saturn>
Date: Tue, 18 Aug 1998 20:27:36 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: RE: R4[04]00SC
Cc: linux@cthulhu.engr.sgi.com
Content-Length: 689
Lines: 22

Hi Ulf,

On 17-Aug-98 Ulf Carlsson wrote:
> Hi,
> 
> I can report that I've a R4000SC running here with Linux. After hard work
> (many long hours, mainly reading MIPS Manual), the VCE exceptions are now
> correctly handled. R4400SC will (probably) also work now. The next step is to
> make this exceptions never happen.

When will your changes be available? They would help the DECstation port a lot
since we have to R4K based DECstations (one R4000SC and one R4400SC) on the
target list. The correct handling of VCE exeptions would help to verify if
certain problems are hardware or CPU related.

> Greetings to Ralf, Alex and last but not least - myself.
> 
> - Ulf

---
Regards,
Harald

From tsbogend@alpha.franken.de  Wed Aug 19 00:48:23 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA16571; Wed, 19 Aug 1998 00:48:22 +0200 (MET DST)
Received-Date: Wed, 19 Aug 1998 00:48:22 +0200 (MET DST)
Received: from alpha.franken.de (root@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id AAA29377; Wed, 19 Aug 1998 00:48:21 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id XAA02749;
	Tue, 18 Aug 1998 23:28:21 +0200
Message-ID: <19980818232821.41234@alpha.franken.de>
Date: Tue, 18 Aug 1998 23:28:21 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@fnet.fr
Subject: Re: shared-memory type ISA boards?
References: <19980817231356.23255@alpha.franken.de> <199808172325.RAA09169@xmission.xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
In-Reply-To: <199808172325.RAA09169@xmission.xmission.com>; from Eric Jorgensen on Mon, Aug 17, 1998 at 05:25:49PM -0600
Content-Length: 525
Lines: 13

On Mon, Aug 17, 1998 at 05:25:49PM -0600, Eric Jorgensen wrote:
> 	Well, the alan cox told me this board is "sortof" shared memory -
> that it uses a range in the ISA memory space as a FIFO. And said that as
> long as the MIPS system keeps that range uncached, it should work fine. 

on Magnum style machines it is uncached.

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From mitch@execpc.com  Wed Aug 19 14:38:42 1998
Received: from mailgw02.execpc.com (mailgw02.execpc.com [169.207.3.78]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id OAA26624; Wed, 19 Aug 1998 14:38:41 +0200 (MET DST)
Received-Date: Wed, 19 Aug 1998 14:38:41 +0200 (MET DST)
Received: from earth.execpc.com (earth.execpc.com [169.207.16.1])
	by mailgw02.execpc.com (8.9.0) id HAA18478
	for <linux-mips@fnet.fr>; Wed, 19 Aug 1998 07:38:37 -0500 (CDT)
Received: (from mitch@localhost) by earth.execpc.com (8.9.0) id HAA28293; Wed, 19 Aug 1998 07:38:36 -0500 (CDT)
Message-ID: <19980819073836.46546@execpc.com>
Date: Wed, 19 Aug 1998 07:38:36 -0500
From: Mitchell Blank Jr <mitch@execpc.com>
To: linux-mips@fnet.fr
Subject: Re: DECStation memory
References: <13785.36764.245026.525250@linbar>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84e-execpc
In-Reply-To: <13785.36764.245026.525250@linbar>; from Tim Parker on Tue, Aug 18, 1998 at 04:13:27PM +0100
Content-Length: 1299
Lines: 29

Tim Parker wrote:
> Just a (hopefully) quick question. Are the memory modules from the
> VAXStation series (think it was a 3100) compatible with the DECStation
> 5K/200s ?

A "Vaxstation 3100" is not a specific model but a whole product line.

> These are 80-pin 16MB SIMM modules I believe, can't say more

It may work.  The 80-pin SIMMs I'm familiar with are the ones that the
PMAX/3MIN/MAXINE machines used (like the DS3100, PD5000/25, DS5000/125,...)
They are available in 2M (common) and 8M (rare) models.  They're always
installed in pairs.  These might also be used in some VS3100s.... I don't
know for sure but it really wouldn't surprise me.

3MAX machines (DS5000/200) were completely differrent IIRC... I'm going
from vague memories here so watch out.  I think their SIMMs were a different
form factor.  They weren't inserted in pairs.  Modules are 8M (common) or
32M (rare).  (actually I've never seen a 32M but Kingston claims that they
have them)  Again, I'm not aware of any VAXen that used this part but
it's possible.

> quite matches. The pin layout, data path/bit counts seem to be OK but
> thats not exactly saying that much. Any ideas / comments ?

Well, I personally would try it out.  Of course, you might cook your
hardware so it's an at-your-own-risk sort of thing.

-Mitch

From jn@del.dk  Wed Aug 19 15:20:17 1998
Received: from mail100.image.dk (root@mail100.image.dk [194.234.58.153]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id PAA27774; Wed, 19 Aug 1998 15:20:16 +0200 (MET DST)
Received-Date: Wed, 19 Aug 1998 15:20:16 +0200 (MET DST)
Received: from note4 (pm24-3.image.dk [194.234.169.195])
	by mail100.image.dk (8.8.7/8.8.7) with SMTP id PAA09476
	for <linux-mips@fnet.fr>; Wed, 19 Aug 1998 15:20:07 +0200
From: "Jan Nielsen" <jn@del.dk>
To: <linux-mips@fnet.fr>
Subject: Scheduler/calender for Linux (MIPS)
Date: Wed, 19 Aug 1998 15:15:24 +0200
Message-ID: <01bdcb73$6d103c20$658244c0@note4>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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: 287
Lines: 14

We are looking for a scheduler/calender which is compiled for MIPS chip.

Technical details for the box:

Linux 2.0 Multitasking operating system
Apache 1.2 Web server, HTTP 1.1 -compliant
CGI Support
Perl 5.0 scripting

Any hints or Tips are appriciated

Thanks in advance

Jan Nielsen

From R.vandenBerg@inter.NL.net  Wed Aug 19 17:16:49 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA29707; Wed, 19 Aug 1998 17:16:47 +0200 (MET DST)
Received-Date: Wed, 19 Aug 1998 17:16:47 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-19.Hoorn.NL.net [193.79.46.183] with ESMTP for <linux-mips@fnet.fr>
	id RAA04444 (8.8.8/3.28); Wed, 19 Aug 1998 17:16:45 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0z99w5-0001ZNC@dutch.mountain>
	for <linux-mips@fnet.fr>; Wed, 19 Aug 1998 17:14:05 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Wed, 19 Aug 1998 17:14:04 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: Re: DECStation memory
In-Reply-To: <19980819073836.46546@execpc.com>
Message-ID: <Pine.LNX.3.95.980819170438.401A-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1121
Lines: 28

On Wed, 19 Aug 1998, Mitchell Blank Jr wrote:

> Tim Parker wrote:
> > Just a (hopefully) quick question. Are the memory modules from the
> > VAXStation series (think it was a 3100) compatible with the DECStation
> > 5K/200s ?
> 
> A "Vaxstation 3100" is not a specific model but a whole product line.

So my machine labeled "VAXstation 3100" (owner thought it was a DECstation
:-( ) could look and thus be completly different than an other VS? (just
out of curiousity)

> > These are 80-pin 16MB SIMM modules I believe, can't say more
> 
> It may work.  The 80-pin SIMMs I'm familiar with are the ones that the
> PMAX/3MIN/MAXINE machines used (like the DS3100, PD5000/25, DS5000/125,...)
> They are available in 2M (common) and 8M (rare) models.  They're always
> installed in pairs.  These might also be used in some VS3100s.... I don't
> know for sure but it really wouldn't surprise me.

What I know is that the 4 Mb extension board of the VS is a bit bigger
then a small isa extension card (i.e. old nc e.g. WD80x3), quite a
different size then the 2 Mb modules of a Personal DECstation 5000/25.

Regards,

Richard

From mitch@execpc.com  Wed Aug 19 17:29:23 1998
Received: from mailgw02.execpc.com (mailgw02.execpc.com [169.207.3.78]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA00413; Wed, 19 Aug 1998 17:29:21 +0200 (MET DST)
Received-Date: Wed, 19 Aug 1998 17:29:21 +0200 (MET DST)
Received: from earth.execpc.com (earth.execpc.com [169.207.16.1])
	by mailgw02.execpc.com (8.9.0) id KAA07248
	for <linux-mips@fnet.fr>; Wed, 19 Aug 1998 10:29:18 -0500 (CDT)
Received: (from mitch@localhost) by earth.execpc.com (8.9.0) id KAA07677; Wed, 19 Aug 1998 10:29:18 -0500 (CDT)
Message-ID: <19980819102918.18575@execpc.com>
Date: Wed, 19 Aug 1998 10:29:18 -0500
From: Mitchell Blank Jr <mitch@execpc.com>
To: linux-mips@fnet.fr
Subject: Re: DECStation memory
References: <19980819073836.46546@execpc.com> <Pine.LNX.3.95.980819170438.401A-100000@whale.dutch.mountain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84e-execpc
In-Reply-To: <Pine.LNX.3.95.980819170438.401A-100000@whale.dutch.mountain>; from Richard van den Berg on Wed, Aug 19, 1998 at 05:14:04PM +0200
Content-Length: 631
Lines: 16

Richard van den Berg wrote:
> > A "Vaxstation 3100" is not a specific model but a whole product line.
> 
> So my machine labeled "VAXstation 3100" (owner thought it was a DECstation
> :-( ) could look and thus be completly different than an other VS? (just
> out of curiousity)

Well there's the /m10, /m20, /m30, /m38, /m40, /m76 (this list from
http://www.netbsd.org/Ports/vax/models.html)  I'm not sure if they used
different memory or not - I'm not VAX expert.

To make it even more complicated, there's also the MicroVAX 3100, of
which there are 13 sub-models.  DEC really liked the ring of the number
"3100" I guess.

-Mitch

From afritz@iname.com  Wed Aug 19 18:01:46 1998
Received: from pop02.globecomm.net (pop02.globecomm.net [206.253.129.186]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA01061; Wed, 19 Aug 1998 18:01:45 +0200 (MET DST)
Received-Date: Wed, 19 Aug 1998 18:01:45 +0200 (MET DST)
Received: from usr01.primenet.com (usr01.primenet.com [206.165.6.201]) by pop02.globecomm.net (8.9.0/8.8.0) with SMTP id MAA05494 for <linux-mips@fnet.fr>; Wed, 19 Aug 1998 12:02:00 -0400 (EDT)
Date: Wed, 19 Aug 1998 09:01:36 -0700 (MST)
From: Adam Fritzler <afritz@iname.com>
X-Sender: afritz@usr01.primenet.com
To: linux-mips@fnet.fr
Subject: Re: DECStation memory
In-Reply-To: <19980819102918.18575@execpc.com>
Message-ID: <Pine.BSI.3.96.980819085634.12631A-100000@usr01.primenet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1498
Lines: 32

On Wed, 19 Aug 1998, Mitchell Blank Jr wrote:

> Well there's the /m10, /m20, /m30, /m38, /m40, /m76 (this list from
> http://www.netbsd.org/Ports/vax/models.html)  I'm not sure if they used
> different memory or not - I'm not VAX expert.
> 
> To make it even more complicated, there's also the MicroVAX 3100, of
> which there are 13 sub-models.  DEC really liked the ring of the number
> "3100" I guess.

Althogh this has nothing to do with MIPS....there was a /m96 as well.

MicroVAX = (VAXstation - color graphics)

Or sometimes the uVAX has no frame buffer at all, but requiures serial
console.  For every uVAX model, there's usually an equivlent VS model,
often suffixed by the frame buffer model name (GPX, SPX, etc)

The only VAX that I could possibly think of that MIGHT use SIMMs are the
VS4000's.  They were quite modern and were released parallel to the
DECstations (FWIR).  Everything before that probably uses "memory cards"
(the ISA-looking ones; stackable to two layers, connections on top).

af

-------------------------------------------------------------------------------
Adam Fritzler                           |
  afritz@delphid.ml.org                 | Animals who are not penguins can   
    afritz@iname.com                    |    can only wish they were.
      http://delphid.ml.org/~afritz/    |        -- Chicago Reader 
        http://www.pst.com/             |               15 Oct 1982
-------------------------------------------------------------------------------

From tsbogend@alpha.franken.de  Wed Aug 19 23:54:29 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA05125; Wed, 19 Aug 1998 23:54:29 +0200 (MET DST)
Received-Date: Wed, 19 Aug 1998 23:54:29 +0200 (MET DST)
Received: from alpha.franken.de (root@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id XAA04545; Wed, 19 Aug 1998 23:54:27 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id XAA02656;
	Wed, 19 Aug 1998 23:51:42 +0200
Message-ID: <19980819235142.36595@alpha.franken.de>
Date: Wed, 19 Aug 1998 23:51:42 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Debugging emacs
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
Content-Length: 788
Lines: 23

Hi,

before I'll ask a bigger audience, I ask here:

As some of you know, emacs dies, when started to open it's own
X window on Linux/MIPS. While trying to debug emacs with gdb,
I found out, that emacs kills it's own .mdebug section when it dumps
(it inserts a new .data section, which kills all references in
the .mdebug section).

Now I'm looking for a way to start a X session with temacs, which has
a working .mdebug section. I'm able to do a temacs -l loadup, which 
will give me a "normal" looking emacs. But I haven't found a way to get 
temacs to create a X session.

Any hints ?

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From Olivier.Galibert@loria.fr  Thu Aug 20 00:04:27 1998
Received: from lorraine.loria.fr (lorraine.loria.fr [152.81.1.17]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA05793; Thu, 20 Aug 1998 00:04:26 +0200 (MET DST)
Received-Date: Thu, 20 Aug 1998 00:04:26 +0200 (MET DST)
Received: from renaissance.loria.fr (renaissance.loria.fr [152.81.4.102])
	by lorraine.loria.fr (8.8.7/8.8.7/8.8.7/JCG) with ESMTP id AAA11724;
	Thu, 20 Aug 1998 00:02:39 +0200 (MET DST)
Received: (from galibert@localhost) by renaissance.loria.fr (8.8.2/8.8.2) id AAA11989; Thu, 20 Aug 1998 00:02:37 +0200 (MET DST)
Message-ID: <19980820000237.A11980@loria.fr>
Date: Thu, 20 Aug 1998 00:02:37 +0200
From: Olivier Galibert <galibert@pobox.com>
To: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
Subject: Re: Debugging emacs
Mail-Followup-To: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr
References: <19980819235142.36595@alpha.franken.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1i
In-Reply-To: <19980819235142.36595@alpha.franken.de>; from Thomas Bogendoerfer on Wed, Aug 19, 1998 at 11:51:42PM +0200
Content-Length: 647
Lines: 15

On Wed, Aug 19, 1998 at 11:51:42PM +0200, Thomas Bogendoerfer wrote:
> Now I'm looking for a way to start a X session with temacs, which has
> a working .mdebug section. I'm able to do a temacs -l loadup, which 
> will give me a "normal" looking emacs. But I haven't found a way to get 
> temacs to create a X session.
> 
> Any hints ?

You're doomed.  At least on XEmacs this hasn't worked for a while, and
I guess FSF Emacs isn't in any better shape  in that area.  Fixing the
undumping code  may  be easier.   Too bad I've   not yet been  able to
install linux on  the indy I  use or I  would probably have fixed that
myself for XEmacs.

  OG.

From pmauriks@ue.com.au  Thu Aug 20 01:20:22 1998
Received: from mail.mel.aone.net.au (mail.mel.aone.net.au [203.12.176.157]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id BAA08465; Thu, 20 Aug 1998 01:20:19 +0200 (MET DST)
Received-Date: Thu, 20 Aug 1998 01:20:19 +0200 (MET DST)
Received: from nemesis.ue.com.au (mail.ue.com.au [203.103.135.130])
	by mail.mel.aone.net.au (8.8.8/8.8.8) with SMTP id JAA27061
	for <linux-mips@fnet.fr>; Thu, 20 Aug 1998 09:20:08 +1000 (EST)
Received: by nemesis.ue.com.au (8.6.12) id JAA29272; Thu, 20 Aug 1998 09:20:04 +1000
Received: from exchange(146.178.74.19) by nemesis.ue.com.au via smap (V1.3)
	id sma028937; Thu Aug 20 09:18:10 1998
Received: by email1 with Internet Mail Service (5.5.1960.3)
	id <RH3ZJMSH>; Thu, 20 Aug 1998 09:18:04 +1000
Message-ID: <8B6C0E727026D2119A590000F8788163CCC6@email1>
From: Paul Mauriks <pmauriks@ue.com.au>
To: "'linux-mips@fnet.fr'" <linux-mips@fnet.fr>
Subject: RE: Scheduler/calender for Linux (MIPS)
Date: Thu, 20 Aug 1998 09:18:03 +1000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain
Content-Length: 1053
Lines: 33

Not compiled for the MIPS chip - but a good calendar program I've found
for Linux is the one at 
http://www.xwind.com - I think it's called synchronize. My experience
with the staff there has 
been almost one of amazement. They are really service oriented.
Syncronize supports most 
UNIX machines as server and client, and it supports Windoze as a client.
It can be run stand alone if required.
Calendars can be accessed as Web pages , anyway take a look. At work we
ended up going with exchange/Outlook instead - I personally think
Synchonize is better.

> -----Original Message-----
> From:	Jan Nielsen [SMTP:jn@del.dk]
> Sent:	Wednesday,19 August 1998 11:15
> To:	linux-mips@fnet.fr
> Subject:	Scheduler/calender for Linux (MIPS)
> 
> We are looking for a scheduler/calender which is compiled for MIPS
> chip.
> 
> Technical details for the box:
> 
> Linux 2.0 Multitasking operating system
> Apache 1.2 Web server, HTTP 1.1 -compliant
> CGI Support
> Perl 5.0 scripting
> 
> Any hints or Tips are appriciated
> 
> Thanks in advance
> 
> Jan Nielsen

From narayh@taec.toshiba.com  Thu Aug 20 03:38:11 1998
Received: from godzilla.taec.com (godzilla.taec.com [204.162.152.130]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id DAA09886; Thu, 20 Aug 1998 03:38:09 +0200 (MET DST)
Received-Date: Thu, 20 Aug 1998 03:38:09 +0200 (MET DST)
Received: from mailint.taec.com by godzilla.taec.com
          via smtpd (for guadalquivir.fnet.fr [193.104.112.133]) with SMTP; 20 Aug 1998 01:37:37 UT
Received: from super.sanjose (super.taec.com [198.232.207.62])
	by mailhost.taec.com (8.8.8/8.8.8) with SMTP id SAA22759
	for <linux-mips@fnet.fr>; Wed, 19 Aug 1998 18:37:37 -0700 (PDT)
Received: by super.sanjose (SMI-8.6/SMI-SVR4)
	id SAA10362; Wed, 19 Aug 1998 18:37:37 -0700
From: narayh@taec.toshiba.com (Hari Narayanan)
Message-Id: <199808200137.SAA10362@super.sanjose>
Subject: Re: Scheduler/calender for Linux (MIPS)
To: linux-mips@fnet.fr
Date: Wed, 19 Aug 1998 18:37:37 -0700 (PDT)
In-Reply-To: <01bdcb73$6d103c20$658244c0@note4> from "Jan Nielsen" at Aug 19, 98 03:15:24 pm
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Content-Length: 123
Lines: 4

Try star division ( www.stardivision.com). They have some
staroffice products. You might find some scheduler there.

Hari.

From harald.koerfgen@netcologne.de  Thu Aug 20 21:52:50 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA17604; Thu, 20 Aug 1998 21:52:44 +0200 (MET DST)
Received-Date: Thu, 20 Aug 1998 21:52:44 +0200 (MET DST)
Received: from franz.no.dom (dial10-1.netcologne.de [195.14.235.1])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id VAA06719
	for <linux-mips@fnet.fr>; Thu, 20 Aug 1998 21:52:40 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980820215355.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <35DBDCAC.95D9FF44@niisi.msk.ru>
Date: Thu, 20 Aug 1998 21:53:55 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: Re: [PATCH]: Linux for Baget/MIPS (r3k & VME box)
Content-Length: 1457
Lines: 40

[I am forwarding this to the list so that someone can correct me, if I am
writing bullsh*t]

Hi Gleb,

On 20-Aug-98 Gleb O. Raiko wrote:

> What we still can't understand is when we must flush I-cache. Well, we
> do understand it in theory - I-cache must be flushed when new mapping
> for a physical page occurs.

Well, this is true for a R4k but not for a R3000. The R4k (and higher) have
virtually indexed caches, the R3000 (and R2000) have physically indexed caches.
If I understand this right, the only need for cacheflushing would be:

o DMA, obviously. Here both caches have to be flushed.

o Copying code. In this case the D-cache would be up to date, but the I-cache
doesn't know that code has changed. Here the I-cache has to be flushed.

The cache operations in arch/mips/mm/r2300.c are still quite R4000 oriented and
I have only implemented cache sizing and cache_flush_all for now. I still have
other problems ;-). If you are interested, I'd be happy to send you a copy.  

> What we would do is to reduce cache
> flushing, e.g. don't flush I-cache if new mapping occurs for data
> segments (data, bss, stack, or whatever) what seems wrong to me because
> user may wish to execute a code which was formed in a data segment. 
> Do you already know the policy ?
> 
> Another issue we're working on is a bug (bugs?) in
> put_user/copy_to_user. It's reproduced fine - ls /lib shows garbage.
> 
> Regards,
> Gleb.

Happy hacking.
---
Regards,
Harald

From R.vandenBerg@inter.NL.net  Fri Aug 21 00:18:34 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA19318; Fri, 21 Aug 1998 00:18:33 +0200 (MET DST)
Received-Date: Fri, 21 Aug 1998 00:18:33 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-2.Hoorn.NL.net [193.79.46.166] with ESMTP for <linux-mips@fnet.fr>
	id AAA25638 (8.8.8/3.28); Fri, 21 Aug 1998 00:18:30 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0z9d25-0001YpC@dutch.mountain>
	for <linux-mips@fnet.fr>; Fri, 21 Aug 1998 00:18:13 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Fri, 21 Aug 1998 00:18:12 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: Z8530 driver output on DS5k/25
Message-ID: <Pine.LNX.3.95.980821001718.401B-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1048
Lines: 46

Hello all,

The Z8530 driver gives following output on my DS5k/25:

...
Starting kswapd v 1.5
DECstation Z8530 serial driver version 0.01
get_zsbaud: 9600
get_zsbaud: 9600
get_zsbaud: 115200
get_zsbaud: 115200
tty00 at 0xbc100001 (irq = 3) is a Z8530 ESCC
tty01 at 0xbc100009 (irq = 3) is a Z8530 ESCC
tty02 at 0xbc180001 (irq = 3) is a Z8530 ESCC
tty03 at 0xbc180009 (irq = 3) is a Z8530 ESCC
Ramdisk driver initialized : 16 ramdisks of 4096K size
declance.c: v0.002 by Linux Mips DECstation task force
eth0: LANCE 08:00:2b:30:8d:2b
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 32k freed
zs_rtsdtr: debug this!
change_speed
zs_rtsdtr: debug this!
debug __wait_on_buffer() in fs/buffer.c, Harald!
debug __wait_on_buffer() in fs/buffer.c, Harald!
zs_rtsdtr: debug this!
rs_write_room
rs_flush_chars
rs_write
transmit_chars
rs_sched_event
rs_write_room
rs_write
rs_write
rs_flush_chars
transmit_chars
rs_sched_event
rs_close

and no output on a connected terminal.

Regards,

Richard


From tsbogend@alpha.franken.de  Fri Aug 21 00:27:50 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA20729; Fri, 21 Aug 1998 00:27:49 +0200 (MET DST)
Received-Date: Fri, 21 Aug 1998 00:27:49 +0200 (MET DST)
Received: from alpha.franken.de (tsbogend@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id AAA10552; Fri, 21 Aug 1998 00:27:45 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id AAA02733;
	Fri, 21 Aug 1998 00:21:11 +0200
Message-ID: <19980821002111.03847@alpha.franken.de>
Date: Fri, 21 Aug 1998 00:21:11 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@fnet.fr
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Debugging emacs
References: <19980819235142.36595@alpha.franken.de> <19980820000237.A11980@loria.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
In-Reply-To: <19980820000237.A11980@loria.fr>; from Olivier Galibert on Thu, Aug 20, 1998 at 12:02:37AM +0200
Content-Length: 690
Lines: 16

On Thu, Aug 20, 1998 at 12:02:37AM +0200, Olivier Galibert wrote:
> You're doomed.  At least on XEmacs this hasn't worked for a while, and
> I guess FSF Emacs isn't in any better shape  in that area.  Fixing the
> undumping code  may  be easier.

Thanks for the tip. It was fairly easy to fix the undumping code, because
everything was already there. It was just ifdef'd out for Linux. Now
I have a dumped emacs with working debugging information and a lot
to learn about XtCreateWidget().

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From dom@algor.co.uk  Fri Aug 21 10:32:33 1998
Received: from embankment.algor.co.uk (0@embankment.algor.co.uk [193.117.190.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id KAA24088; Fri, 21 Aug 1998 10:32:30 +0200 (MET DST)
Received-Date: Fri, 21 Aug 1998 10:32:30 +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.8/8.8.8) with ESMTP id JAA01007
	for <linux-mips@fnet.fr>; Fri, 21 Aug 1998 09:32:26 +0100 (BST)
Received: (from dom@localhost)
	by gladsmuir.algor.co.uk (8.8.5/8.8.5) id JAA00304;
	Fri, 21 Aug 1998 09:32:25 +0100 (GMT/BST)
Date: Fri, 21 Aug 1998 09:32:25 +0100 (GMT/BST)
Message-Id: <199808210832.JAA00304@gladsmuir.algor.co.uk>
From: Dominic Sweetman <dom@algor.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: linux-mips@fnet.fr
Subject: Re: [PATCH]: Linux for Baget/MIPS (r3k & VME box)
In-Reply-To: <XFMail.980820215355.harald.koerfgen@netcologne.de>
References: <35DBDCAC.95D9FF44@niisi.msk.ru>
	<XFMail.980820215355.harald.koerfgen@netcologne.de>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Content-Length: 4326
Lines: 101


> [I am forwarding this to the list so that someone can correct me, if I am
> writing bullsh*t]

It looks more or less right.

> > What we still can't understand is when we must flush
> > I-cache. Well, we do understand it in theory - I-cache must be
> > flushed when new mapping for a physical page occurs.

There are two operations you can need to do on a cache line.  You can
*invalidate* it (so any further access to it will re-fetch it from
memory?); you can do a *writeback* - write it back to memory, if
there's any data the CPU written but which has so far only got stored
in the cache.

The word "flush" is widely used to mean invalidate, and widely used to
mean invalidate and writeback, and probably sometimes used to mean
just writeback.  So I'd recommend you don't use that word at all...

> Well, this is true for a R4k but not for a R3000. The R4k (and
> higher) have virtually indexed caches, the R3000 (and R2000) have
> physically indexed caches.

o R2000/3000 = cache on physical addresses, write-through (you never
  have to do a writeback on this sort of cache).

o R4000+ primary cache - odd arrangement using virtual addresses to
  index the cache, but the physical 'tag' (that's the cache-held field
  which holds the physical address so the CPU can check whether the
  cache holds the data it wants).

  The mix of virtual index and physical tags can lead to the strange
  and feared "cache aliases" mentioned by an earlier correspondent;
  it's possible to get copies of the same memory location stored in
  different cache lines, if that location is being accessed at two
  different virtual addresses.

  [R4000's designers took the risk because it gave them a higher clock
   rate - the cache lookup with the virtual address can now be done
   in parallel with address translation.  Neat.]

  R4000 caches are "write-back" - data written to them does not always
  get immediately forwarded to memory, so you sometimes need to do an
  explicit writeback operation.

  Note that R4000SC secondary caches are physically indexed and
  addressed, and you get no aliases there.

> If I understand this right, the only need for cacheflushing would be:
> 
> o DMA, obviously. Here both caches have to be flushed.

When filling memory with DMA, the corresponding regions in both caches
should be invalidated.  When taking data from memory with DMA, the
corresponding region in the data cache should first be written-back.

> o Copying code. In this case the D-cache would be up to date, but
> the I-cache doesn't know that code has changed. Here the I-cache has
> to be flushed.

You need to do a D-cache writeback, followed by an I-cache invalidate,
of any cache lines containing the code area you've copied to.

BUT you don't normally need to do anything to MIPS caches when you
change page mappings.

You would only need to do something if your OS deliberately maps pages
so as to risk cache aliases; this is possible on the R4000SC and
R4000MC CPUs, because they use their secondary cache tags to watch for
aliases and report (via an exception) when one tries to happen.

Most OS' avoid cache aliases.  This is in fact quite easy.  Because
MIPS memory virtual->physical translation is paged in 4K chunks, 
address bits 0-11 are the same as physical addresses.  An 8K
direct-mapped primary cache only employs address bits up to 12 in its
index; so a particularly *physical* location can only ever appear in
two places in the cache - depending on the value of bit 13 in the
virtual address which currently maps to it.

You can avoid aliases, therefore, by insisting that all the virtual
addresses which map to any particular physical location are the same
modulo 64Kbytes (or any other power of two bigger than the cache 
size).  Generally, OS' only allocate a second virtual address to data
under unusual circumstances, and the address space is big enough to
stick to such rules.

> > ... because user may wish to execute a code which was formed in a
> > data segment.

Any application using self-modifying code must explicitly D-cache
writeback and I-cache invalidate the code which has been modified or
created.  Since cache ops are privileged, that will need a system
call.  Simple self-modifying code just doesn't work on MIPS CPUs.

-- 
Regards,

Dominic Sweetman
Algorithmics Ltd
dom@algor.co.uk

From rajko@mech.math.msu.su  Fri Aug 21 12:00:40 1998
Received: from mech.math.msu.su (mech.math.msu.su [158.250.33.65]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id MAA25377; Fri, 21 Aug 1998 12:00:35 +0200 (MET DST)
Received-Date: Fri, 21 Aug 1998 12:00:35 +0200 (MET DST)
Received: (from rajko@localhost) by mech.math.msu.su (8.6.10/8.6.10/sasha.040695) id OAA09977; Fri, 21 Aug 1998 14:00:24 +0400
Date: Fri, 21 Aug 1998 14:00:23 +0400 (MSD)
From: "Gleb O. Rajko" <rajko@mech.math.msu.su>
To: linux-mips@fnet.fr
Subject: Re: [PATCH]: Linux for Baget/MIPS (r3k & VME box)
In-Reply-To: <199808210832.JAA00304@gladsmuir.algor.co.uk>
Message-ID: <Pine.SV4.3.91.980821132827.9650B-100000@mech>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1533
Lines: 39


On Fri, 21 Aug 1998, Dominic Sweetman wrote:

> > > What we still can't understand is when we must flush
> > > I-cache. Well, we do understand it in theory - I-cache must be
> > > flushed when new mapping for a physical page occurs.
> 
> There are two operations you can need to do on a cache line.  You can
> *invalidate* it (so any further access to it will re-fetch it from
> memory?); you can do a *writeback* - write it back to memory, if
> there's any data the CPU written but which has so far only got stored
> in the cache.

In terms of I-cache writeback is a very interesting operation :-)
> 
> The word "flush" is widely used to mean invalidate, and widely used to
> mean invalidate and writeback, and probably sometimes used to mean
> just writeback.  So I'd recommend you don't use that word at all...
> 

We discuss r3k so word "flush" means just invalidate. 

> > o Copying code. In this case the D-cache would be up to date, but
> > the I-cache doesn't know that code has changed. Here the I-cache has
> > to be flushed.
> 
> You need to do a D-cache writeback, followed by an I-cache invalidate,
> of any cache lines containing the code area you've copied to.
> 
> BUT you don't normally need to do anything to MIPS caches when you
> change page mappings.

Consider the following scenario. A region (physical page) is swapped (on a 
backing store), immediately filled by new data, new virtual page is 
mapped to this region. There is a non-zero probability that old data 
still lives in I-cache...  

Regards,
Gleb.

From dom@mudchute.algor.co.uk  Fri Aug 21 12:10:02 1998
Received: from embankment.algor.co.uk (0@embankment.algor.co.uk [193.117.190.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id MAA25873; Fri, 21 Aug 1998 12:09:57 +0200 (MET DST)
Received-Date: Fri, 21 Aug 1998 12:09:57 +0200 (MET DST)
Received: from mudchute.algor.co.uk (dom@mudchute.algor.co.uk [193.117.190.19])
	by embankment.algor.co.uk (8.8.8/8.8.8) with ESMTP id LAA01365;
	Fri, 21 Aug 1998 11:09:37 +0100 (BST)
Received: (from dom@localhost)
	by mudchute.algor.co.uk (8.8.5/8.8.5) id LAA16297;
	Fri, 21 Aug 1998 11:09:37 +0100 (GMT/BST)
Date: Fri, 21 Aug 1998 11:09:37 +0100 (GMT/BST)
Message-Id: <199808211009.LAA16297@mudchute.algor.co.uk>
From: Dominic Sweetman <dom@algor.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: linux-mips@fnet.fr
Subject: Re: [PATCH]: Linux for Baget/MIPS (r3k & VME box)
In-Reply-To: <Pine.SV4.3.91.980821132827.9650B-100000@mech>
References: <199808210832.JAA00304@gladsmuir.algor.co.uk>
	<Pine.SV4.3.91.980821132827.9650B-100000@mech>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Content-Length: 466
Lines: 11


Gleb O. Rajko (rajko@mech.math.msu.su) writes:

> Consider the following scenario. A region (physical page) is swapped (on a 
> backing store), immediately filled by new data, new virtual page is 
> mapped to this region. There is a non-zero probability that old data 
> still lives in I-cache...  

Cache management is needed when you do DMA or the CPU writes
instructions.  But in this case the need for the invalidation is quite
unconnected with the re-mapping.

From ralf@mailhost.uni-koblenz.de  Sat Aug 22 11:46:31 1998
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id LAA09033; Sat, 22 Aug 1998 11:46:30 +0200 (MET DST)
Received-Date: Sat, 22 Aug 1998 11:46:30 +0200 (MET DST)
Received: from thoma (ralf@thoma.uni-koblenz.de [141.26.4.61])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with SMTP id LAA21254;
	Sat, 22 Aug 1998 11:46:28 +0200 (MEST)
Received: by thoma (SMI-8.6/KO-2.0)
	id LAA04441; Sat, 22 Aug 1998 11:46:27 +0200
Message-ID: <19980822114626.23656@uni-koblenz.de>
Date: Sat, 22 Aug 1998 11:46:26 +0200
From: ralf@uni-koblenz.de
To: Dominic Sweetman <dom@algor.co.uk>
Cc: linux-mips@fnet.fr
Subject: Re: [PATCH]: Linux for Baget/MIPS (r3k & VME box)
References: <35DBDCAC.95D9FF44@niisi.msk.ru> <XFMail.980820215355.harald.koerfgen@netcologne.de> <199808210832.JAA00304@gladsmuir.algor.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84e
In-Reply-To: <199808210832.JAA00304@gladsmuir.algor.co.uk>; from Dominic Sweetman on Fri, Aug 21, 1998 at 09:32:25AM +0100
Content-Length: 2666
Lines: 50

On Fri, Aug 21, 1998 at 09:32:25AM +0100, Dominic Sweetman wrote:

> o R4000+ primary cache - odd arrangement using virtual addresses to
>   index the cache, but the physical 'tag' (that's the cache-held field
>   which holds the physical address so the CPU can check whether the
>   cache holds the data it wants).
> 
>   The mix of virtual index and physical tags can lead to the strange
>   and feared "cache aliases" mentioned by an earlier correspondent;
>   it's possible to get copies of the same memory location stored in
>   different cache lines, if that location is being accessed at two
>   different virtual addresses.
> 
>   [R4000's designers took the risk because it gave them a higher clock
>    rate - the cache lookup with the virtual address can now be done
>    in parallel with address translation.  Neat.]

Most caches today on other architectures are virtual indexed; they're
usually just implemented somewhat more clever such that they feel like
physical indexed caches to the OS.  The Alpha or PPC caches are examples.
I think the Rm7000 is the first 64 bit MIPS CPU where they got it right.

> You would only need to do something if your OS deliberately maps pages
> so as to risk cache aliases; this is possible on the R4000SC and
> R4000MC CPUs, because they use their secondary cache tags to watch for
> aliases and report (via an exception) when one tries to happen.
> 
> Most OS' avoid cache aliases.  This is in fact quite easy.  Because
> MIPS memory virtual->physical translation is paged in 4K chunks, 
> address bits 0-11 are the same as physical addresses.  An 8K
> direct-mapped primary cache only employs address bits up to 12 in its
> index; so a particularly *physical* location can only ever appear in
> two places in the cache - depending on the value of bit 13 in the
> virtual address which currently maps to it.

Unfortunately the R4000SC / R4400SC always verify 3 bits of the virtual
tags in the second level cache.  And there is no provision in the Linux
kernel to allocate physical pages matches a special property like
physical_address[12:13]=2; adding is non-trivial.  As things are virtual
aliases are something that happens very common under Linux.  Linux uses
a single zero filled page like for example in the case when mmap(2)ing
/dev/zero and reading from one of the mapped pages.  Stupid SC/MC CPUs
will send VCE exceptions when accessing these mappings.  (``Stupid''
because VCE exceptions when neither the memory was an access

This was the simple case to fix - on R4000SC / R4400SC we just allocate
8 zero filled pages and match the physical page colour with the virtual
page colour when mmaping.

  Ralf

From R.vandenBerg@inter.NL.net  Sat Aug 22 14:06:36 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id OAA10505; Sat, 22 Aug 1998 14:06:36 +0200 (MET DST)
Received-Date: Sat, 22 Aug 1998 14:06:36 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-38.Hoorn.NL.net [193.79.46.202] with ESMTP for <linux-mips@fnet.fr>
	id OAA19782 (8.8.8/3.28); Sat, 22 Aug 1998 14:06:24 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0zACQr-0001YdC@dutch.mountain>
	for <linux-mips@fnet.fr>; Sat, 22 Aug 1998 14:06:09 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Sat, 22 Aug 1998 14:06:08 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: DECstation related patch
Message-ID: <Pine.LNX.3.95.980822140338.568A-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1036
Lines: 28

Howdy,

At http://www.inter.nl.net/users/schnecke/html/mips/lance.html has a
new patch arrived, from the page:

   These are the changes contained in the patchfile relative to the
   source base directory linux against kernelsource 2.1.100
   (2.1.99pl2 should work too):
     * arch/mips/config.in so that the driver can be choosen
     * in the directory drivers/net:
          + Makefile and Space.c to make network driver list aware
            of declance.c.
          + of course declance.c itself.
     * in the directory drivers/tc:
          + tc.c to make system_base correct on DS5000/xx
          + Config.in for TURBOchannel related drivers

   Except declance.c and Config.in the files mentioned above are
   the same in the 2.1.99pl2 and 2.1.100 kernel source.

I'm interested in your opinion about the configuration stuff and the
little hack in tc.c as I like proposing adding it to the official
kernel-source together with drivers/net/Makefile and Space.c and of course
in time a stable declance.c. 

Regards,

Richard

From dom@algor.co.uk  Sun Aug 23 15:37:32 1998
Received: from embankment.algor.co.uk (0@embankment.algor.co.uk [193.117.190.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id PAA20702; Sun, 23 Aug 1998 15:37:31 +0200 (MET DST)
Received-Date: Sun, 23 Aug 1998 15:37:31 +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.8/8.8.8) with ESMTP id OAA17388;
	Sun, 23 Aug 1998 14:37:24 +0100 (BST)
Received: (from dom@localhost)
	by gladsmuir.algor.co.uk (8.8.5/8.8.5) id OAA00405;
	Sun, 23 Aug 1998 14:37:21 +0100 (GMT/BST)
Date: Sun, 23 Aug 1998 14:37:21 +0100 (GMT/BST)
Message-Id: <199808231337.OAA00405@gladsmuir.algor.co.uk>
From: Dominic Sweetman <dom@algor.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: linux-mips@fnet.fr
Cc: Dominic Sweetman <dom@algor.co.uk>
Subject: Re: [PATCH]: Linux for Baget/MIPS (r3k & VME box)
In-Reply-To: <19980822114626.23656@uni-koblenz.de>
References: <35DBDCAC.95D9FF44@niisi.msk.ru>
	<XFMail.980820215355.harald.koerfgen@netcologne.de>
	<199808210832.JAA00304@gladsmuir.algor.co.uk>
	<19980822114626.23656@uni-koblenz.de>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Content-Length: 955
Lines: 24


Ralf writes:

> Most caches today on other architectures are virtual indexed;
> they're usually just implemented somewhat more clever such that they
> feel like physical indexed caches to the OS.

It's common practice to restrict the cache set size to match the
memory translation page size, so that only in-page addresses are used
in the cache index - so from the index point of view virtual and
physical addresses are the same.  Is that what you meant?  I can't see
any other way of avoiding aliases in a virtually-indexed
physically-addressed cache.

The RM7000 has no aliases because it's 16Kbyte caches are 4-way set
associative - 4Kbyte sets, equal to the page size.  However, that's
only possible with the RM7000's relatively small primary cache, which
in turn is practicable because it also has an onchip secondary cache.

I recall the first SuperSPARC chip had a 5-way set-associative 20Kbyte
cache for the same reason.

Dominic
dom@algor.co.uk

From tsbogend@alpha.franken.de  Sun Aug 23 22:40:04 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id WAA23669; Sun, 23 Aug 1998 22:40:03 +0200 (MET DST)
Received-Date: Sun, 23 Aug 1998 22:40:03 +0200 (MET DST)
Received: from alpha.franken.de (tsbogend@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id WAA20701; Sun, 23 Aug 1998 22:39:57 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id WAA00378;
	Sun, 23 Aug 1998 22:36:48 +0200
Message-ID: <19980823223647.12724@alpha.franken.de>
Date: Sun, 23 Aug 1998 22:36:47 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Emacs problem
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
Content-Length: 903
Lines: 18

I've found the cause for the emacs X11 problems. The unexec code of Emacs
doesn't handle relocations in the .rel.dyn section, because Mips seems to
be the only platform, which uses such section (sgi and sni, are using
a different implementation of unexec). This mishandling leads to an emacs
binary, which has double resolved dynamic relocations (once when dumped,
twice when executed), which leads to a seg fault. It happens only with
X11, because the relocations are only for X11 stuff.

I'll try to fix that, but it would be good to have some documentation about
the .rel.dyn section, which looks a little bit different than the i386
.rel.data section). Any pointers other than the bfd source code ?

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From ralf@mailhost.uni-koblenz.de  Mon Aug 24 12:19:58 1998
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id MAA29706; Mon, 24 Aug 1998 12:19:56 +0200 (MET DST)
Received-Date: Mon, 24 Aug 1998 12:19:56 +0200 (MET DST)
Received: from zaphod (ralf@zaphod.uni-koblenz.de [141.26.4.13])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with SMTP id MAA07743;
	Mon, 24 Aug 1998 12:19:32 +0200 (MEST)
Received: by zaphod (SMI-8.6/KO-2.0)
	id MAA28887; Mon, 24 Aug 1998 12:19:30 +0200
Message-ID: <19980824121930.00186@uni-koblenz.de>
Date: Mon, 24 Aug 1998 12:19:30 +0200
From: ralf@uni-koblenz.de
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: Emacs problem
References: <19980823223647.12724@alpha.franken.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84e
In-Reply-To: <19980823223647.12724@alpha.franken.de>; from Thomas Bogendoerfer on Sun, Aug 23, 1998 at 10:36:47PM +0200
Content-Length: 953
Lines: 19

On Sun, Aug 23, 1998 at 10:36:47PM +0200, Thomas Bogendoerfer wrote:

> I've found the cause for the emacs X11 problems. The unexec code of Emacs
> doesn't handle relocations in the .rel.dyn section, because Mips seems to
> be the only platform, which uses such section (sgi and sni, are using
> a different implementation of unexec). This mishandling leads to an emacs
> binary, which has double resolved dynamic relocations (once when dumped,
> twice when executed), which leads to a seg fault. It happens only with
> X11, because the relocations are only for X11 stuff.
> 
> I'll try to fix that, but it would be good to have some documentation about
> the .rel.dyn section, which looks a little bit different than the i386
> .rel.data section). Any pointers other than the bfd source code ?

I think you can find the related ABI documentation on www.mipsabi.org.
What details exactly are you interested in?  I've got a printed copy at
home.

  Ralf

From ralf@uni-koblenz.de  Mon Aug 24 14:57:39 1998
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id OAA02125; Mon, 24 Aug 1998 14:57:37 +0200 (MET DST)
Received-Date: Mon, 24 Aug 1998 14:57:37 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from uni-koblenz.de (dali.uni-koblenz.de [141.26.5.1])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id OAA26287
	for <linux-mips@fnet.fr>; Mon, 24 Aug 1998 14:57:28 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id OAA01223;
	Mon, 24 Aug 1998 14:55:01 +0200
Message-ID: <19980824145501.A400@uni-koblenz.de>
Date: Mon, 24 Aug 1998 14:55:01 +0200
To: Jan Nielsen <jn@del.dk>, linux-mips@fnet.fr
Subject: Re: Scheduler/calender for Linux (MIPS)
References: <01bdcb73$6d103c20$658244c0@note4>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <01bdcb73$6d103c20$658244c0@note4>; from Jan Nielsen on Wed, Aug 19, 1998 at 03:15:24PM +0200
Content-Length: 436
Lines: 15

On Wed, Aug 19, 1998 at 03:15:24PM +0200, Jan Nielsen wrote:

> We are looking for a scheduler/calender which is compiled for MIPS chip.
> 
> Technical details for the box:
> 
> Linux 2.0 Multitasking operating system
> Apache 1.2 Web server, HTTP 1.1 -compliant
> CGI Support
> Perl 5.0 scripting

Sounds like a Cobalt Qube.  Iff you have X libraries etc. installed on the
thing then you could try to build the Gnome calendar.

  Ralf

From ralf@uni-koblenz.de  Mon Aug 24 15:31:04 1998
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id PAA03171; Mon, 24 Aug 1998 15:31:01 +0200 (MET DST)
Received-Date: Mon, 24 Aug 1998 15:31:01 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from uni-koblenz.de (dali.uni-koblenz.de [141.26.5.1])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id PAA01488
	for <linux-mips@fnet.fr>; Mon, 24 Aug 1998 15:30:57 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id PAA07311;
	Mon, 24 Aug 1998 15:30:51 +0200
Message-ID: <19980824153051.C400@uni-koblenz.de>
Date: Mon, 24 Aug 1998 15:30:51 +0200
To: Dominic Sweetman <dom@algor.co.uk>, linux-mips@fnet.fr
Subject: Re: [PATCH]: Linux for Baget/MIPS (r3k & VME box)
References: <35DBDCAC.95D9FF44@niisi.msk.ru> <XFMail.980820215355.harald.koerfgen@netcologne.de> <199808210832.JAA00304@gladsmuir.algor.co.uk> <19980822114626.23656@uni-koblenz.de> <199808231337.OAA00405@gladsmuir.algor.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <199808231337.OAA00405@gladsmuir.algor.co.uk>; from Dominic Sweetman on Sun, Aug 23, 1998 at 02:37:21PM +0100
Content-Length: 1430
Lines: 31

On Sun, Aug 23, 1998 at 02:37:21PM +0100, Dominic Sweetman wrote:

> > Most caches today on other architectures are virtual indexed;
> > they're usually just implemented somewhat more clever such that they
> > feel like physical indexed caches to the OS.
> 
> It's common practice to restrict the cache set size to match the
> memory translation page size, so that only in-page addresses are used
> in the cache index - so from the index point of view virtual and
> physical addresses are the same.  Is that what you meant?  I can't see
> any other way of avoiding aliases in a virtually-indexed
> physically-addressed cache.

Yes, it's what I mean and in fact I don't see any other way either except
the R10000 style solution.  They seem to have some solution to cleanup
virtual aliases by automatically writing back / invalidating the affected
cache lines.

> The RM7000 has no aliases because it's 16Kbyte caches are 4-way set
> associative - 4Kbyte sets, equal to the page size.  However, that's
> only possible with the RM7000's relatively small primary cache, which
> in turn is practicable because it also has an onchip secondary cache.
> 
> I recall the first SuperSPARC chip had a 5-way set-associative 20Kbyte
> cache for the same reason.

Some PowerPC chips have 8-way associative caches for this reason.  I
just cannot imagine that going beyond 4-way associative caches will
still improve cache hits for them.

  Ralf

From dbaker@illuminetss7.com  Tue Aug 25 00:21:23 1998
Received: from usin.com (rainier.illuminetss7.com [192.246.48.20] (may be forged)) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA07059; Tue, 25 Aug 1998 00:21:21 +0200 (MET DST)
Received-Date: Tue, 25 Aug 1998 00:21:21 +0200 (MET DST)
Received: from venus (illuminetss7.com [198.202.216.4]) by usin.com (8.8.8/8.8.8) with SMTP id PAA04797 for <linux-mips@fnet.fr>; Mon, 24 Aug 1998 15:21:14 -0700 (PDT)
Sender: dbaker@illuminetSS7.com
Message-ID: <35E1E75A.57DC@illuminetss7.com>
Date: Mon, 24 Aug 1998 15:21:14 -0700
From: Dan Baker <dbaker@illuminetSS7.com>
X-Mailer: Mozilla 3.01 (X11; I; HP-UX A.09.05 9000/712)
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: 616
Lines: 14

You asked for e-mail if I have a MIPS box I would be interested in
running Linux on. I am buying an SGI Iris Indigo (R3000) that has Irix
5.1 installed. I looked at SGI to see what an upgrade to 5.3 would cost.
it would cost more than I'm paying for the computer, and wouldn't even
include a compiler! 

I'm not a programmer, but I am a UNIX support person. I have been using
and supporting (fixing) UNIX systems for years. I currently work for a
telecomm company supporting software on HP 9000 systems. The extent of
my programming experience is building new kernels for BSD and Solaris
systems.

Thanks,
Dan Baker

From alhaz@xmission.xmission.com  Tue Aug 25 00:53:20 1998
Received: from xmission.xmission.com (alhaz@xmission.xmission.com [198.60.22.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA08076; Tue, 25 Aug 1998 00:53:17 +0200 (MET DST)
Received-Date: Tue, 25 Aug 1998 00:53:17 +0200 (MET DST)
Received: (from alhaz@localhost) by xmission.xmission.com (8.8.8/8.7.5) id QAA07139 for linux-mips@fnet.fr; Mon, 24 Aug 1998 16:53:05 -0600 (MDT)
From: Eric Jorgensen <alhaz@xmission.com>
Message-Id: <199808242253.QAA07139@xmission.xmission.com>
Subject: Re: Mips Linux
To: linux-mips@fnet.fr
Date: Mon, 24 Aug 1998 16:53:04 -0600 (MDT)
In-Reply-To: <35E1E75A.57DC@illuminetss7.com> from "Dan Baker" at Aug 24, 98 03:21:14 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1434
Lines: 31

> 
> You asked for e-mail if I have a MIPS box I would be interested in
> running Linux on. I am buying an SGI Iris Indigo (R3000) that has Irix
> 5.1 installed. I looked at SGI to see what an upgrade to 5.3 would cost.
> it would cost more than I'm paying for the computer, and wouldn't even
> include a compiler! 
> 
> I'm not a programmer, but I am a UNIX support person. I have been using
> and supporting (fixing) UNIX systems for years. I currently work for a
> telecomm company supporting software on HP 9000 systems. The extent of
> my programming experience is building new kernels for BSD and Solaris
> systems.


	Wow! That was, like, almost two years ago.

	There is actually an SGI-Linux project well underway. You can read
about the linux-MIPS project at http://www.fnet.fr/linux-mips/ and
SGI/Linux at www.linux.sgi.com. I'm not sure if the old Iris Indigo is
among their target machines, but I know that there's some working R3k
Linux-MIPS kernels. The port to ARC compliant hardware is more or less
done. Thus, I'm soon to install Linux on my Magnum 4000. Support for my
RC3240 should show up before long, and I'm not sure if I care about the
RS2030. 16Mhz R2000 can't be fast enough to worry about. If I find a copy
of RISC/os for it I'll be happy. 

	You might want to join the Linux-MIPS mailing list and see if
anyone out there is already working on Iris support. The web page can be
somewhat outdated. 

 - Eric

From alhaz@xmission.xmission.com  Tue Aug 25 01:04:34 1998
Received: from xmission.xmission.com (alhaz@xmission.xmission.com [198.60.22.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id BAA08183; Tue, 25 Aug 1998 01:04:33 +0200 (MET DST)
Received-Date: Tue, 25 Aug 1998 01:04:33 +0200 (MET DST)
Received: (from alhaz@localhost) by xmission.xmission.com (8.8.8/8.7.5) id RAA10040 for linux-mips@fnet.fr; Mon, 24 Aug 1998 17:04:29 -0600 (MDT)
From: Eric Jorgensen <alhaz@xmission.com>
Message-Id: <199808242304.RAA10040@xmission.xmission.com>
Subject: Re: Mips Linux
To: linux-mips@fnet.fr
Date: Mon, 24 Aug 1998 17:04:28 -0600 (MDT)
In-Reply-To: <199808242253.QAA07139@xmission.xmission.com> from "Eric Jorgensen" at Aug 24, 98 04:53:04 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 134
Lines: 5


	I'm sorry about the weird posting, thought it was in response to
something I posted to usenet back in january of 97 . . . 

 - Eric

From mitch@execpc.com  Tue Aug 25 01:13:44 1998
Received: from mailgw01.execpc.com (mailgw01.execpc.com [169.207.2.78]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id BAA08255; Tue, 25 Aug 1998 01:13:43 +0200 (MET DST)
Received-Date: Tue, 25 Aug 1998 01:13:43 +0200 (MET DST)
Received: from earth.execpc.com (earth.execpc.com [169.207.16.1])
	by mailgw01.execpc.com (8.9.0) id SAA25825
	for <linux-mips@fnet.fr>; Mon, 24 Aug 1998 18:13:40 -0500 (CDT)
Received: (from mitch@localhost) by earth.execpc.com (8.9.0) id SAA28460; Mon, 24 Aug 1998 18:13:40 -0500 (CDT)
Message-ID: <19980824181340.27221@execpc.com>
Date: Mon, 24 Aug 1998 18:13:40 -0500
From: Mitchell Blank Jr <mitch@execpc.com>
To: linux-mips@fnet.fr
Subject: Re: Mips Linux
References: <35E1E75A.57DC@illuminetss7.com> <199808242253.QAA07139@xmission.xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84e-execpc
In-Reply-To: <199808242253.QAA07139@xmission.xmission.com>; from Eric Jorgensen on Mon, Aug 24, 1998 at 04:53:04PM -0600
Content-Length: 643
Lines: 15

Eric Jorgensen wrote:
> done. Thus, I'm soon to install Linux on my Magnum 4000. Support for my
> RC3240 should show up before long, and I'm not sure if I care about the
> RS2030. 16Mhz R2000 can't be fast enough to worry about. If I find a copy

The R2000 is a fairly important target -- there are lots of DECstation
[23]100's floating around.  They're not fast, but they can still find some
utility.

IIRC, once R3000 support is all smoothed out R2000 will essentially be
done too.  I think R2000 and R3000 are fairly similar from the kernel
level.  (MIPS wizards... any comments?)  I don't know anything about
the RC3240 or RS2030.

-Mitch

From lahaye@ripault.cea.fr  Tue Aug 25 10:50:19 1998
Received: from nenuphar.saclay.cea.fr (nenuphar.saclay.cea.fr [132.166.192.7]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id KAA11081; Tue, 25 Aug 1998 10:50:17 +0200 (MET DST)
Received-Date: Tue, 25 Aug 1998 10:50:17 +0200 (MET DST)
Received: from muguet.saclay.cea.fr (muguet.saclay.cea.fr [132.166.192.6]) 
	by nenuphar.saclay.cea.fr (8.8.8/CEAnet-relay-4.1.1) with ESMTP id KAA10981
	for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 10:50:14 +0200 (MET DST)
Received: from cerbere.limeil.cea.fr  (cerbere.bruyeres.cea.fr [132.165.76.1]) by muguet.saclay.cea.fr
       (8.8.8/CEAnet-relay-4.1.1) with SMTP id KAA08305
        for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 10:49:17 +0200 (MET DST)
Received: by cerbere.limeil.cea.fr (CEANET-1.1+)
	id AA23728; Tue, 25 Aug 1998 10:50:12 +0200
Received: from indre.ripault.cea.fr(132.165.32.1) by cerbere via smap 
	id sma023726; Tue Aug 25 10:50:00 1998
Received: from ripault.cea.fr (cher.ripault.cea.fr [132.165.32.3]) by ripault.cea.fr. (8.8.7/8.7.3) with ESMTP id KAA11003 for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 10:48:15 +0200
Received: from ripault.cea.fr (localhost [127.0.0.1])
	by ripault.cea.fr (8.8.7/8.8.7) with ESMTP id KAA00438
	for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 10:49:23 +0200
Sender: lahaye@ripault.cea.fr
Message-Id: <35E27A8F.9F7E7DCA@ripault.cea.fr>
Date: Tue, 25 Aug 1998 08:49:19 +0000
From: Olivier LAHAYE <lahaye@ripault.cea.fr>
Reply-To: lahaye@ripault.cea.fr
Organization: CEA-DAM, Le Ripault
X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.32 i586)
Mime-Version: 1.0
To: linux-mips@fnet.fr
Subject: Is this project still alive ?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 363
Lines: 16

    Hello,

Is the Linux/MIPS project still alive?

I own a MIPS Magnum R3000 (RC3330) 8MB RAM and 640MB Disk.
It is networked to my linux PII 266.
I don't have time to program, but I'd enjoy testing.

Thanks for any answer.
            Olivier LAHAYE

    PS: reply befor September 4th 1998. (My email will then be:
olivier.lahaye@cea.fr)

--
    Olivier LAHAYE

From ralf@uni-koblenz.de  Tue Aug 25 11:09:53 1998
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id LAA11290; Tue, 25 Aug 1998 11:09:50 +0200 (MET DST)
Received-Date: Tue, 25 Aug 1998 11:09:50 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from uni-koblenz.de (dali.uni-koblenz.de [141.26.5.1])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id LAA22639
	for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 11:09:46 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id LAA01757;
	Tue, 25 Aug 1998 11:09:27 +0200
Message-ID: <19980825110927.C397@uni-koblenz.de>
Date: Tue, 25 Aug 1998 11:09:27 +0200
To: Mitchell Blank Jr <mitch@execpc.com>, linux-mips@fnet.fr
Subject: Re: Mips Linux
References: <35E1E75A.57DC@illuminetss7.com> <199808242253.QAA07139@xmission.xmission.com> <19980824181340.27221@execpc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <19980824181340.27221@execpc.com>; from Mitchell Blank Jr on Mon, Aug 24, 1998 at 06:13:40PM -0500
Content-Length: 479
Lines: 12

On Mon, Aug 24, 1998 at 06:13:40PM -0500, Mitchell Blank Jr wrote:

> IIRC, once R3000 support is all smoothed out R2000 will essentially be
> done too.  I think R2000 and R3000 are fairly similar from the kernel
> level.  (MIPS wizards... any comments?)  I don't know anything about
> the RC3240 or RS2030.

R2000 and R3000 are identical modulo bugs and the content of the c0_prid
register.  Anybody still got the errata documentss for old R2000 / R3000
silicon around?

  Ralf

From engel@numerik.math.uni-siegen.de  Tue Aug 25 11:15:33 1998
Received: from fourier.numerik.math.uni-siegen.de (fourier.numerik.math.uni-siegen.de [141.99.2.230]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id LAA11359; Tue, 25 Aug 1998 11:15:30 +0200 (MET DST)
Received-Date: Tue, 25 Aug 1998 11:15:30 +0200 (MET DST)
Received: (from engel@localhost) by fourier.numerik.math.uni-siegen.de (Mailhost) id LAA27762 for linux-mips@fnet.fr; Tue, 25 Aug 1998 11:15:35 +0200 (MET DST)
From: Michael Engel <engel@numerik.math.uni-siegen.de>
Message-Id: <199808250915.LAA27762@fourier.numerik.math.uni-siegen.de>
Subject: ARC Specification (fwd)
To: linux-mips@fnet.fr
Date: Tue, 25 Aug 1998 11:15:34 +0200 (MET DST)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1015
Lines: 31


Hi,

just found this on the AXP Linux mailing list.

I just converted it to Postscript - if anyone's interested in the PS
version, please drop me a note.

regards,
	Michael Engel	(engel@unix-ag.uni-siegen.de)

--
Forwarded message:
> Message-Id: <m0zB9wT-0000aVC@songdog>
> From: roman@songdog.eskimo.com (Bill Roman)
> Subject: ARC Specification
> To: axp-list@redhat.com
> Date: Mon, 24 Aug 1998 20:38:43 -0700 (PDT)
> 
> The Advanced RISC Computing (ARC) Specification is a useful and
> interesting document for anyone running Linux on an Alpha using
> ARC firmware or AlphaBIOS (not SRM console).  You can find it at
> http://www.microsoft.com/hwdev/specs/default.htm
> 
> Unfortunately, it's a Microsoft Word document :-(  I haven't had
> a chance to try any of the variety of tools available under Linux
> that might be able to view it.  If anyone finds a way to display
> and/or print it, perhaps you could let us know?
> 
> -- 
> Bill Roman  (roman@songdog.eskimo.com / roman@songdog.uucp)   running linux

From tor@spacetec.no  Tue Aug 25 14:03:47 1998
Received: from pallas.spacetec.no (pallas.spacetec.no [192.51.5.92]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id OAA12017; Tue, 25 Aug 1998 14:03:44 +0200 (MET DST)
Received-Date: Tue, 25 Aug 1998 14:03:44 +0200 (MET DST)
Received: (from tor@localhost)
	by pallas.spacetec.no (8.8.5/8.8.5) id OAA26149
	for linux-mips@fnet.fr; Tue, 25 Aug 1998 14:03:10 +0200
Message-Id: <199808251203.OAA26149@pallas.spacetec.no>
From: tor@spacetec.no (Tor Arntsen)
Date: Tue, 25 Aug 1998 14:03:09 +0200
In-Reply-To: Michael Engel <engel@numerik.math.uni-siegen.de>
       "ARC Specification (fwd)" (Aug 25, 10:17)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: linux-mips@fnet.fr
Subject: Re: ARC Specification (fwd)
Content-Length: 584
Lines: 17

On Aug 25, 10:17, Michael Engel wrote:
>just found this on the AXP Linux mailing list.
>
>I just converted it to Postscript - if anyone's interested in the PS
>version, please drop me a note.
>
>regards,
>	Michael Engel	(engel@unix-ag.uni-siegen.de)

I would like to see it -- can you make it available somewhere?
Sounds like it could be something for www.fnet.fr/linux-mips too..

Regards,
Tor
(I have an Olli M710 which I haven't been able to touch for one and a half
year, being on the road all the time.. another four months to go and then 
I hope to start some hacking again :-)

From tsbogend@alpha.franken.de  Tue Aug 25 22:58:21 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id WAA15368; Tue, 25 Aug 1998 22:58:20 +0200 (MET DST)
Received-Date: Tue, 25 Aug 1998 22:58:20 +0200 (MET DST)
Received: from alpha.franken.de (tsbogend@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id WAA06225; Tue, 25 Aug 1998 22:58:18 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id WAA02630;
	Tue, 25 Aug 1998 22:56:03 +0200
Message-ID: <19980825225603.43888@alpha.franken.de>
Date: Tue, 25 Aug 1998 22:56:03 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: ralf@uni-koblenz.de
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: Emacs problem
References: <19980823223647.12724@alpha.franken.de> <19980824121930.00186@uni-koblenz.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
In-Reply-To: <19980824121930.00186@uni-koblenz.de>; from ralf@uni-koblenz.de on Mon, Aug 24, 1998 at 12:19:30PM +0200
Content-Length: 827
Lines: 22

On Mon, Aug 24, 1998 at 12:19:30PM +0200, ralf@uni-koblenz.de wrote:
> I think you can find the related ABI documentation on www.mipsabi.org.

ok, I've found what I was looking for.

> What details exactly are you interested in?  I've got a printed copy at
> home.

On other ELF platforms .rel section reference the section for which the
relocations are for in the sh_info section header. This field is 0 for
.rel.dyn sections. The ABI document states that the relocations for
.data and .sdata sections, so I know what I wanted to know:-)

Another questione does gcc/egcs produce .sdata, .lit4 or .li8 sections
on Linux/MIPS ?

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From tsbogend@alpha.franken.de  Tue Aug 25 22:59:42 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id WAA15394; Tue, 25 Aug 1998 22:59:41 +0200 (MET DST)
Received-Date: Tue, 25 Aug 1998 22:59:41 +0200 (MET DST)
Received: from alpha.franken.de (tsbogend@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id WAA06244; Tue, 25 Aug 1998 22:59:39 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id WAA02639;
	Tue, 25 Aug 1998 22:57:27 +0200
Message-ID: <19980825225727.34112@alpha.franken.de>
Date: Tue, 25 Aug 1998 22:57:27 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@fnet.fr
Subject: Re: ARC Specification (fwd)
References: <engel@numerik.math.uni-siegen.de> <199808251203.OAA26149@pallas.spacetec.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
In-Reply-To: <199808251203.OAA26149@pallas.spacetec.no>; from Tor Arntsen on Tue, Aug 25, 1998 at 02:03:09PM +0200
Content-Length: 544
Lines: 14

On Tue, Aug 25, 1998 at 02:03:09PM +0200, Tor Arntsen wrote:
> (I have an Olli M710 which I haven't been able to touch for one and a half
> year, being on the road all the time.. another four months to go and then 
> I hope to start some hacking again :-)

M710 or do you mean M700 ? If M700, do you know the difference between
M700 and M710 ?

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From tor@spacetec.no  Wed Aug 26 00:15:36 1998
Received: from pallas.spacetec.no (pallas.spacetec.no [192.51.5.92]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA15919; Wed, 26 Aug 1998 00:15:34 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 00:15:34 +0200 (MET DST)
Received: (from tor@localhost)
	by pallas.spacetec.no (8.8.5/8.8.5) id AAA26973
	for linux-mips@fnet.fr; Wed, 26 Aug 1998 00:15:09 +0200
Message-Id: <199808252215.AAA26973@pallas.spacetec.no>
From: tor@spacetec.no (Tor Arntsen)
Date: Wed, 26 Aug 1998 00:15:08 +0200
In-Reply-To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
       "Re: ARC Specification (fwd)" (Aug 25, 22:01)
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: linux-mips@fnet.fr
Subject: Re: ARC Specification (fwd)
Content-Length: 219
Lines: 9

On Aug 25, 22:01, Thomas Bogendoerfer wrote:
>M710 or do you mean M700 ? If M700, do you know the difference between
>M700 and M710 ?

Oops, sorry about that, it was just a typo.  It's M700-10, not M710.

>Thomas.

Tor

From triemer@apt4g.a3nyc.com  Wed Aug 26 03:59:17 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id DAA18128; Wed, 26 Aug 1998 03:59:16 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 03:59:16 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id VAA06113
	for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 21:18:12 -0400
Date: Tue, 25 Aug 1998 21:18:10 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: TurboChannel
Message-ID: <Pine.LNX.3.96.980825211556.6111A-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 29
Lines: 3

What's a TurboChannel?

-Tom

From triemer@apt4g.a3nyc.com  Wed Aug 26 04:21:15 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id EAA18424; Wed, 26 Aug 1998 04:21:14 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 04:21:14 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id VAA06140
	for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 21:40:09 -0400
Date: Tue, 25 Aug 1998 21:40:09 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: Turning of CONFIG_TC
Message-ID: <Pine.LNX.3.96.980825213726.6111D-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 330
Lines: 13

Turning off option CONFIG_TC generates a no link error.

drivers/char/tty_io.c has a call to rs_init which is defined
in drivers/tc/tc.c

tc.c is logically not included when CONFIG_TC is turned off.

I would guess that rs_init should be protected with #ifdef CONFIG_TC
but I don't know the whole story about the code yet.

-Tom



From triemer@apt4g.a3nyc.com  Wed Aug 26 04:30:19 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id EAA18518; Wed, 26 Aug 1998 04:30:18 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 04:30:18 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id VAA06149
	for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 21:49:13 -0400
Date: Tue, 25 Aug 1998 21:49:13 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: tc.c
Message-ID: <Pine.LNX.3.96.980825214451.6111E-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 425
Lines: 17

After several iterations of testing I've narrowed down why 
the kernel that I have is dying.  

I've built the vanilla dist 2.1.100 with TurboChannel turned on.

drivers/tc/tc.c line 102 is causing a kernel paging request.
I'd guess a division by zero error is occuring.

tc_clock = 10000 / info->clk_period

FYI  - running on a decstation 2100 (I don't yet know how
to tell if it has a TurboChannel or not.)

-Tom Riemer




From mitch@execpc.com  Wed Aug 26 04:06:05 1998
Received: from mailgw02.execpc.com (mailgw02.execpc.com [169.207.3.78]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id EAA18200; Wed, 26 Aug 1998 04:06:01 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 04:06:01 +0200 (MET DST)
Received: from earth.execpc.com (earth.execpc.com [169.207.16.1])
	by mailgw02.execpc.com (8.9.0) id VAA00577
	for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 21:05:58 -0500 (CDT)
Received: (from mitch@localhost) by earth.execpc.com (8.9.0) id VAA20445; Tue, 25 Aug 1998 21:05:58 -0500 (CDT)
Message-ID: <19980825210558.43932@execpc.com>
Date: Tue, 25 Aug 1998 21:05:58 -0500
From: Mitchell Blank Jr <mitch@execpc.com>
To: linux-mips@fnet.fr
Subject: Re: TurboChannel
References: <Pine.LNX.3.96.980825211556.6111A-100000@apt4g.a3nyc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84e-execpc
In-Reply-To: <Pine.LNX.3.96.980825211556.6111A-100000@apt4g.a3nyc.com>; from Thomas Riemer on Tue, Aug 25, 1998 at 09:18:10PM -0400
Content-Length: 299
Lines: 9

Thomas Riemer wrote:
> What's a TurboChannel?

It's the expansion bus used in many DECstations.  Also used in early Alpha
machines.  The form factor looks like a larger version of Sun's SBUS.
It's 12.5Mhz(?), 32 bit.  Commonly used for framebuffers, extra ethernets,
extra SCSI chains, etc.

-Mitch

From afritz@iname.com  Wed Aug 26 04:16:42 1998
Received: from pop03.globecomm.net (pop03.globecomm.net [206.253.130.65]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id EAA18300; Wed, 26 Aug 1998 04:16:41 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 04:16:41 +0200 (MET DST)
Received: from usr01.primenet.com (usr01.primenet.com [206.165.6.201]) by pop03.globecomm.net (8.9.0/8.8.0) with SMTP id WAA11383 for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 22:16:32 -0400 (EDT)
Date: Tue, 25 Aug 1998 19:16:14 -0700 (MST)
From: Adam Fritzler <afritz@iname.com>
X-Sender: afritz@usr01.primenet.com
To: linux-mips@fnet.fr
Subject: Re: TurboChannel
In-Reply-To: <Pine.LNX.3.96.980825211556.6111A-100000@apt4g.a3nyc.com>
Message-ID: <Pine.BSI.3.96.980825191509.1141B-100000@usr01.primenet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 695
Lines: 24


It's the expansion bus used on several of the DECstation's.  There's docs
on it somewhere on gatekeeper.dec.com.  

af

On Tue, 25 Aug 1998, Thomas Riemer wrote:

> What's a TurboChannel?
> 
> -Tom
> 
> 




-------------------------------------------------------------------------------
Adam Fritzler                           |
  afritz@delphid.ml.org                 | Animals who are not penguins can   
    afritz@iname.com                    |    can only wish they were.
      http://delphid.ml.org/~afritz/    |        -- Chicago Reader 
        http://www.pst.com/             |               15 Oct 1982
-------------------------------------------------------------------------------

From afritz@iname.com  Wed Aug 26 04:17:34 1998
Received: from pop01.globecomm.net (pop01.globecomm.net [206.253.129.185]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id EAA18355; Wed, 26 Aug 1998 04:17:33 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 04:17:33 +0200 (MET DST)
Received: from usr01.primenet.com (usr01.primenet.com [206.165.6.201]) by pop01.globecomm.net (8.9.0/8.8.0) with SMTP id WAA05015 for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 22:17:07 -0400 (EDT)
Date: Tue, 25 Aug 1998 19:17:28 -0700 (MST)
From: Adam Fritzler <afritz@iname.com>
X-Sender: afritz@usr01.primenet.com
To: linux-mips@fnet.fr
Subject: Re: TurboChannel
In-Reply-To: <19980825210558.43932@execpc.com>
Message-ID: <Pine.BSI.3.96.980825191649.1141C-100000@usr01.primenet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 933
Lines: 29


I'ts 12.5MHz on the DS5k/xx's (ioasic?), 25MHz on everything else.

af

On Tue, 25 Aug 1998, Mitchell Blank Jr wrote:

> Thomas Riemer wrote:
> > What's a TurboChannel?
> 
> It's the expansion bus used in many DECstations.  Also used in early Alpha
> machines.  The form factor looks like a larger version of Sun's SBUS.
> It's 12.5Mhz(?), 32 bit.  Commonly used for framebuffers, extra ethernets,
> extra SCSI chains, etc.
> 
> -Mitch
> 
> 




-------------------------------------------------------------------------------
Adam Fritzler                           |
  afritz@delphid.ml.org                 | Animals who are not penguins can   
    afritz@iname.com                    |    can only wish they were.
      http://delphid.ml.org/~afritz/    |        -- Chicago Reader 
        http://www.pst.com/             |               15 Oct 1982
-------------------------------------------------------------------------------

From triemer@apt4g.a3nyc.com  Wed Aug 26 04:59:54 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id EAA18744; Wed, 26 Aug 1998 04:59:53 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 04:59:53 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id WAA06201
	for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 22:18:50 -0400
Date: Tue, 25 Aug 1998 22:18:50 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: Diff for fix for drivers/tc/tc.c
Message-ID: <Pine.LNX.3.96.980825221537.6111F-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 433
Lines: 16

Here are diffs for drivers/tc/tc.c - this fixes the kernel paging
fault that I saw earlier today.

-Tom Riemer
------------------------------------------------------------------------
102c102,103
< 	tc_clock = 10000 / info->clk_period;
---
> 	if (info)
>         	tc_clock = 10000 / info->clk_period;
104c105
< 	if (TURBOCHANNEL && info->slot_size && slot0addr) {
---
> 	if (TURBOCHANNEL && info && info->slot_size && slot0addr) {



From triemer@apt4g.a3nyc.com  Wed Aug 26 05:11:38 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id FAA18858; Wed, 26 Aug 1998 05:11:37 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 05:11:37 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id WAA06211
	for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 22:30:34 -0400
Date: Tue, 25 Aug 1998 22:30:33 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: dependency on rs_init
Message-ID: <Pine.LNX.3.96.980825222712.6111G-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 278
Lines: 10

The dependency on rs_init is slightly more complicated than 
first glance.

drivers/Makefile has an ifdef CONFIG_TC to include the /drivers/tc
subdirectory.  

drivers/tc/decserial.c contains the function rs_init required
if CONFIG_SERIAL is set in drivers/char/tty_io.c.

-Tom

From mitch@execpc.com  Wed Aug 26 04:46:51 1998
Received: from mailgw01.execpc.com (mailgw01.execpc.com [169.207.2.78]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id EAA18641; Wed, 26 Aug 1998 04:46:49 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 04:46:49 +0200 (MET DST)
Received: from earth.execpc.com (earth.execpc.com [169.207.16.1])
	by mailgw01.execpc.com (8.9.0) id VAA05549
	for <linux-mips@fnet.fr>; Tue, 25 Aug 1998 21:46:45 -0500 (CDT)
Received: (from mitch@localhost) by earth.execpc.com (8.9.0) id VAA00270; Tue, 25 Aug 1998 21:46:45 -0500 (CDT)
Message-ID: <19980825214644.49048@execpc.com>
Date: Tue, 25 Aug 1998 21:46:44 -0500
From: Mitchell Blank Jr <mitch@execpc.com>
To: linux-mips@fnet.fr
Subject: Re: tc.c
References: <Pine.LNX.3.96.980825214451.6111E-100000@apt4g.a3nyc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84e-execpc
In-Reply-To: <Pine.LNX.3.96.980825214451.6111E-100000@apt4g.a3nyc.com>; from Thomas Riemer on Tue, Aug 25, 1998 at 09:49:13PM -0400
Content-Length: 430
Lines: 15

Thomas Riemer wrote:
> tc_clock = 10000 / info->clk_period

That should probably be fixed.

> FYI  - running on a decstation 2100 (I don't yet know how
> to tell if it has a TurboChannel or not.)

The [23]100's didn't have and TC slots.  They might have used some sort of
TC bug internally, but I don't think so.

A good summary of the various DECstations is available at NetBSD's site:
	http://www.netbsd.org/Ports/pmax/

-Mitch

From R.vandenBerg@inter.NL.net  Wed Aug 26 10:47:14 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id KAA20213; Wed, 26 Aug 1998 10:47:13 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 10:47:13 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-6.Hoorn.NL.net [193.79.46.170] with ESMTP for <linux-mips@fnet.fr>
	id KAA06469 (8.8.8/3.28); Wed, 26 Aug 1998 10:47:11 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0zBbBe-0001YpC@dutch.mountain>
	for <linux-mips@fnet.fr>; Wed, 26 Aug 1998 10:44:14 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Wed, 26 Aug 1998 10:44:13 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: Re: dependency on rs_init
In-Reply-To: <Pine.LNX.3.96.980825222712.6111G-100000@apt4g.a3nyc.com>
Message-ID: <Pine.LNX.3.95.980826104401.529C-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 630
Lines: 22

On Tue, 25 Aug 1998, Thomas Riemer wrote:

> The dependency on rs_init is slightly more complicated than 
> first glance.

Just edit the Makefile in drivers/tc

> drivers/Makefile has an ifdef CONFIG_TC to include the /drivers/tc
> subdirectory.  

That's set with the ordinary configuration tools (make config or
menuconfig or xconfig) see arch/mips/config.in for details.

> drivers/tc/decserial.c contains the function rs_init required
> if CONFIG_SERIAL is set in drivers/char/tty_io.c.

This serial driver is a start of getting a serial driver for the Z8530
chip that's in most 5k's, not in the [23]100's.

Regards,

Richard

From harald.koerfgen@netcologne.de  Wed Aug 26 19:59:01 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA23043; Wed, 26 Aug 1998 19:59:00 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 19:59:00 +0200 (MET DST)
Received: from franz.no.dom (dial5-96.netcologne.de [194.8.195.96])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id TAA23627
	for <linux-mips@fnet.fr>; Wed, 26 Aug 1998 19:58:52 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980826200009.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.LNX.3.96.980825222712.6111G-100000@apt4g.a3nyc.com>
Date: Wed, 26 Aug 1998 20:00:09 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: RE: dependency on rs_init
Content-Length: 1709
Lines: 53

Hi all,

On 26-Aug-98 Thomas Riemer wrote:
> The dependency on rs_init is slightly more complicated than 
> first glance.

Yes, Tom, the situation is actually somewhat confusing, due to lack of device
drivers. There are two possibilities to get output from a DECstation at the
moment.

One is the real(tm) SERIAL_CONSOLE in drivers/tc/decserial.c. This works only
on DS5K/1xx and DS5k/2x0 and would, with a little hack, on DS5k/xx (all have
Z85C30 based serial ports). (If you're interested: replace 0xbc18000? with
0xbc10000? in serial_putc(...) for your maxine, but I don't know if that will
work).

The other one is using the PROM routines (works on all DECstations). This is
what promcon.c in arch/mips/dec is for and is intended as a temporary
solution until we have charakter device drivers to use as console devices for
all DECstations. From the kernels point of view, this is a SERIAL_CONSOLE too,
even if the PROM directs the output to your framebuffer.

To make a long story short, at the beginning of arch/mips/promcon.c you'll
find:

#if 0
__initfunc(int rs_init(void))
{
        return 0;
}
#endif

Replace the #if 0 with #if 1 and disable CONFIG_TC. Your DS 2100 doesn't have a
TURBOchannel anyway. I didn't want to make all this configurable, because
promcon.c will go away as soon as we have at least serial console code for DZ
based DECstations.

Olivier, what do you think about this? 
 
> drivers/Makefile has an ifdef CONFIG_TC to include the /drivers/tc
> subdirectory.  
> 
> drivers/tc/decserial.c contains the function rs_init required
> if CONFIG_SERIAL is set in drivers/char/tty_io.c.
> 
> -Tom

I apologize for the confusion and hope this helps.

Keep hacking.
---
Regards,
Harald

From jjacocks@helix.nih.gov  Wed Aug 26 21:56:26 1998
Received: from helix.nih.gov (helix.nih.gov [128.231.2.3]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA23871; Wed, 26 Aug 1998 21:56:25 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 21:56:25 +0200 (MET DST)
Received: (from jjacocks@localhost)
	by helix.nih.gov (8.8.5/8.8.5) id PAA05676;
	Wed, 26 Aug 1998 15:56:22 -0400 (EDT)
Date: Wed, 26 Aug 1998 15:56:22 -0400 (EDT)
From: "James A. Jacocks" <jjacocks@helix.nih.gov>
To: linux-mips@fnet.fr
Subject: Serial Console on DECStation 5000/120
Message-ID: <Pine.SGI.3.96.980826155327.4778A-100000@helix.nih.gov>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 552
Lines: 13

I have a DS5000/120 with a PMAGB-BA, a Wyse 30 terminal, and a null modem
cable connecting the two (plugged into the DS's 3 serial port).  However,
I am completely unable to make the DS use the terminal as its console.  I
have tried removing the framebuffer, setenving the console to s, and many
other things.  Any ideas?

BTW, my serial parms are 9600,n,8,1,hardware.  However, I think I've also
tried XON/XOFF.

Thanks!

(BTW, the reason that I post this to a Linux list is that this is a prereq
for me loading Linux, as Icurrently have no monitor.)

From harald.koerfgen@netcologne.de  Wed Aug 26 22:03:42 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id WAA23936; Wed, 26 Aug 1998 22:03:37 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 22:03:37 +0200 (MET DST)
Received: from franz.no.dom (dial9-211.netcologne.de [194.8.195.211])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id WAA27840
	for <linux-mips@fnet.fr>; Wed, 26 Aug 1998 22:03:16 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980826220432.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Wed, 26 Aug 1998 22:04:32 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: Hello World!
Content-Length: 436
Lines: 14

Hi all!

Well, the subject says it all... with one difference. This message was printed
on a DECstation 5000/133 running linux-2.1.100 from within a user space program
via /dev/ttyS0.

No tricks, no polling or blocking. Purely interrupt driven with
copy_from_user() and everything. Looks like my serial device driver shows first
 signs of life and we're not too far away from a single user shell :-).

Keep hacking.
---
Regards,
Harald

From mitch@execpc.com  Wed Aug 26 22:05:12 1998
Received: from mailgw00.execpc.com (mailgw00.execpc.com [169.207.1.78]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id WAA23972; Wed, 26 Aug 1998 22:05:05 +0200 (MET DST)
Received-Date: Wed, 26 Aug 1998 22:05:05 +0200 (MET DST)
Received: from earth.execpc.com (earth.execpc.com [169.207.16.1])
	by mailgw00.execpc.com (8.9.0) id PAA05790
	for <linux-mips@fnet.fr>; Wed, 26 Aug 1998 15:04:51 -0500 (CDT)
Received: (from mitch@localhost) by earth.execpc.com (8.9.0) id PAA02133; Wed, 26 Aug 1998 15:04:51 -0500 (CDT)
Message-ID: <19980826150451.59934@execpc.com>
Date: Wed, 26 Aug 1998 15:04:51 -0500
From: Mitchell Blank Jr <mitch@execpc.com>
To: linux-mips@fnet.fr
Subject: Re: Serial Console on DECStation 5000/120
References: <Pine.SGI.3.96.980826155327.4778A-100000@helix.nih.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84e-execpc
In-Reply-To: <Pine.SGI.3.96.980826155327.4778A-100000@helix.nih.gov>; from James A. Jacocks on Wed, Aug 26, 1998 at 03:56:22PM -0400
Content-Length: 652
Lines: 15

James A. Jacocks wrote:
> I have a DS5000/120 with a PMAGB-BA, a Wyse 30 terminal, and a null modem
> cable connecting the two (plugged into the DS's 3 serial port).  However,

Maybe someone can give you the exact details of which serial port to use...
I think on my 5k/125 it's the one labeled '2' but maybe it's the one labeled
'3'... it's been a long time since I've booted it headless.

> I am completely unable to make the DS use the terminal as its console.  I
> have tried removing the framebuffer, setenving the console to s, and many
> other things.  Any ideas?

The only thing you need to do is unplug the keyboard.  Just like a Sun.

-Mitch

From lembark@wrkhors.com  Thu Aug 27 02:16:46 1998
Received: from bird.wrkhors.com (root@[206.180.156.161]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id CAA27601; Thu, 27 Aug 1998 02:16:42 +0200 (MET DST)
Received-Date: Thu, 27 Aug 1998 02:16:42 +0200 (MET DST)
Received: from wrkhors.com (poolf2-017.wwa.com [207.241.63.82])
	by bird.wrkhors.com (8.8.5/8.8.5) with ESMTP id TAA04553
	for <linux-mips@fnet.fr>; Wed, 26 Aug 1998 19:16:33 -0500
Sender: lembark@wrkhors.com
Message-ID: <35E4A560.908E1332@wrkhors.com>
Date: Wed, 26 Aug 1998 19:16:32 -0500
From: Steven Lembark <lembark@wrkhors.com>
Organization: Workhorse Computing
X-Mailer: Mozilla 4.05 [en] (X11; U; Linux 2.0.34 i586)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: Re: Hello World!
References: <XFMail.980826220432.harald.koerfgen@netcologne.de>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msB7C22BE20A65E8D6ACB82DD8"
Content-Length: 4653
Lines: 76

This is a cryptographically signed message in MIME format.

--------------msB7C22BE20A65E8D6ACB82DD8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

>  signs of life and we're not too far away from a single user shell :-).

:-) :-)

-- 
 Steven Lembark                                   2930 W. Palmer St.
 Workhorse Computing                             Chicago, IL  60647
 lembark@wrkhors.com                                   800-762-1582
---------------------------------------------------------------------
  The opinions expressed here are those of this company.
  I am the company.
---------------------------------------------------------------------
--------------msB7C22BE20A65E8D6ACB82DD8
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIKnQYJKoZIhvcNAQcCoIIKjjCCCooCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CNYwggQgMIIDiaADAgECAhBVDFTJrYx0lb7N/7Wcab/6MA0GCSqGSIb3DQEBBAUAMGIxETAP
BgNVBAcTCEludGVybmV0MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE0MDIGA1UECxMrVmVy
aVNpZ24gQ2xhc3MgMSBDQSAtIEluZGl2aWR1YWwgU3Vic2NyaWJlcjAeFw05ODAyMTMwMDAw
MDBaFw05OTAyMTMyMzU5NTlaMIIBHDERMA8GA1UEBxMISW50ZXJuZXQxFzAVBgNVBAoTDlZl
cmlTaWduLCBJbmMuMTQwMgYDVQQLEytWZXJpU2lnbiBDbGFzcyAxIENBIC0gSW5kaXZpZHVh
bCBTdWJzY3JpYmVyMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvQ1BT
IEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk2MTMwMQYDVQQLEypEaWdpdGFsIElEIENs
YXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxFzAVBgNVBAMTDlN0ZXZlbiBMZW1iYXJr
MSIwIAYJKoZIhvcNAQkBFhNsZW1iYXJrQHdya2hvcnMuY29tMFwwDQYJKoZIhvcNAQEBBQAD
SwAwSAJBALIZkLcDVrYlAXaMuzHZgRNl8sXENgQpWOY1y/qQ3zr28bz2wx58G6nAUE8Ua9ua
3jSATooRSELXWxt+wyguwwECAwEAAaOCAV0wggFZMAkGA1UdEwQCMAAwga8GA1UdIASBpzCA
MIAGC2CGSAGG+EUBBwEBMIAwKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNv
bS9DUFMwYgYIKwYBBQUHAgIwVjAVFg5WZXJpU2lnbiwgSW5jLjADAgEBGj1WZXJpU2lnbidz
IENQUyBpbmNvcnAuIGJ5IHJlZmVyZW5jZSBsaWFiLiBsdGQuIChjKTk3IFZlcmlTaWduAAAA
AAAAMBEGCWCGSAGG+EIBAQQEAwIHgDCBhgYKYIZIAYb4RQEGAwR4FnZkNDY1MmJkNjNmMjA0
NzAyOTI5ODc2M2M5ZDJmMjc1MDY5YzczNTliZWQxYjA1OWRhNzViYzRiYzk3MDE3NDdkYTVk
M2YyMTQxYmVhZGIyYmQyZTg5MjE1YWE2OWYxZDQxMTQ5OTdhMWIzNDNmNGU1OTc2NTQxMA0G
CSqGSIb3DQEBBAUAA4GBAEWNZJ2oEw1sqpCyiYNc0DCoG3ytfJcWz/yvDSNWIdVcau0WkIq3
xTTyml4GUxR8/nqbPwy/Ye9q24Lf9az3DVMTVaaw0dgnSrExrfzSuEYuFPyMi4cYr1NAbfyu
ZRHx5ckbJUU9UyPQPjuTF8NjdrggAAPlTz8vK1NBhUJ/Xm9pMIICeTCCAeKgAwIBAgIQUh81
HfJwfgArvspZhwTVOTANBgkqhkiG9w0BAQIFADBfMQswCQYDVQQGEwJVUzEXMBUGA1UEChMO
VmVyaVNpZ24sIEluYy4xNzA1BgNVBAsTLkNsYXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlm
aWNhdGlvbiBBdXRob3JpdHkwHhcNOTYwNjI3MDAwMDAwWhcNOTkwNjI3MjM1OTU5WjBiMREw
DwYDVQQHEwhJbnRlcm5ldDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNDAyBgNVBAsTK1Zl
cmlTaWduIENsYXNzIDEgQ0EgLSBJbmRpdmlkdWFsIFN1YnNjcmliZXIwgZ8wDQYJKoZIhvcN
AQEBBQADgY0AMIGJAoGBALYUps9N0AUN2Moj0G+qtCmSY44s+G+W1y6ddksRsTaNV8nD/RzG
uv4eCLozypXqvuNbzQaot3kdRCrtc/KxUoNoEHBkkdc+a/n3XZ0UQ5tul0WYgUfRLcvdu3LX
TD9xquJA8lQ5vBbuz3zsuts/bCqzFrGGEp2ukzTVuNXQ9z6pAgMBAAGjMzAxMA8GA1UdEwQI
MAYBAf8CAQEwCwYDVR0PBAQDAgEGMBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIF
AAOBgQDB+vcC51fKEXXGnAz6K3dPh0UXO+PSwdoPWDmOrpWZA6GooTj+eZqTFwuXhjnHymg0
ZrvHiEX2yAwF7r6XJe/g1G7kf512XM59uhSirguf+2dbSKVnJa8ZZIj2ctgpJ6o3EmqxKK8n
gxhlbI3tQJ5NxHiohuzpLFC/pvkN27CmSjCCAjEwggGaAgUCpAAAATANBgkqhkiG9w0BAQIF
ADBfMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNzA1BgNVBAsTLkNs
YXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNOTYwMTI5
MDAwMDAwWhcNOTkxMjMxMjM1OTU5WjBfMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNp
Z24sIEluYy4xNzA1BgNVBAsTLkNsYXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAOUZv22jVmEtmUhx9mfe
uY3rt56GgAqRDvo4Ja9GiILlc6igmyRdDR/MZW4MsNBWhBiHmgabEKFz37RYOWtuwfYV1aio
P6oSBo0xrH+wNNePNGeICc0UEeJORVZpH3gCgNrcR5EpuzbJY1zF4Ncth3uhtzKwezC6Ki8x
qu6jZ9rbAgMBAAEwDQYJKoZIhvcNAQECBQADgYEAUnO6mlXc3D+CfbCQmGIqgkx2AG4lPdXC
CXBXAQwPdx8YofscYA6gdTtJIUH+p1wtTEJJ0/8o2Izqnf7JB+J3glMj3lXzzkST+vpMvco2
81tmsp7I8gxeXtShtCEJM8o7WfySwjj8rdmWJOAt+qMp9TNoeE60vJ9pNeKomJRzO8QxggGP
MIIBiwIBATB2MGIxETAPBgNVBAcTCEludGVybmV0MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5j
LjE0MDIGA1UECxMrVmVyaVNpZ24gQ2xhc3MgMSBDQSAtIEluZGl2aWR1YWwgU3Vic2NyaWJl
cgIQVQxUya2MdJW+zf+1nGm/+jAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkqhkiG
9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTk4MDgyNzAwMTYzMlowIwYJKoZIhvcNAQkEMRYEFHnx
r60iFt9SzsWXa5eEMtQ5eVp/MFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZI
hvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0GCSqG
SIb3DQEBAQUABEBAt1ksyZ5C9114P3Wrcd4AaN0U4IuQ5Psq5gpIu1dXBP73HAy4W6tRmBj3
KcKRJb1xyCCl5htPtY2jW8+lLO9z
--------------msB7C22BE20A65E8D6ACB82DD8--

From rajko@mech.math.msu.su  Thu Aug 27 11:38:47 1998
Received: from mech.math.msu.su (mech.math.msu.su [158.250.33.65]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id LAA00879; Thu, 27 Aug 1998 11:38:43 +0200 (MET DST)
Received-Date: Thu, 27 Aug 1998 11:38:43 +0200 (MET DST)
Received: (from rajko@localhost) by mech.math.msu.su (8.6.10/8.6.10/sasha.040695) id NAA09557; Thu, 27 Aug 1998 13:38:32 +0400
Date: Thu, 27 Aug 1998 13:38:31 +0400 (MSD)
From: "Gleb O. Rajko" <rajko@mech.math.msu.su>
To: linux-mips@fnet.fr
Subject: RE: dependency on rs_init
In-Reply-To: <XFMail.980826200009.harald.koerfgen@netcologne.de>
Message-ID: <Pine.SV4.3.91.980827132232.9499A-100000@mech>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 939
Lines: 21



On Wed, 26 Aug 1998, Harald Koerfgen wrote:

> The other one is using the PROM routines (works on all DECstations). This is
> what promcon.c in arch/mips/dec is for and is intended as a temporary
> solution until we have charakter device drivers to use as console devices for
> all DECstations. 

Why temporary solution ? My experience shows prom console is good 
enough to have it permanently. It's bug free, the code is small, higher 
console code allows to emulate linux-like terminal on top of prom console.
I would recommend to look at SPARC/Linux code beginning from 2.1.109 
(according to vger cvs tree, I don't know what is Linus' version that 
corresponds to). Around this version console stuff was rewritten and became 
more clear. Now, SPARC/Linux allows to have several consoles: prom, 
sbus and ATI Mach (available only on UltraSparc). There are also
run-time options to select, something like console=prom.

Regards,
Gleb.

From R.vandenBerg@inter.NL.net  Thu Aug 27 12:45:11 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id MAA01236; Thu, 27 Aug 1998 12:45:10 +0200 (MET DST)
Received-Date: Thu, 27 Aug 1998 12:45:10 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-50.Hoorn.NL.net [193.79.46.214] with ESMTP for <linux-mips@fnet.fr>
	id MAA09753 (8.8.8/3.28); Thu, 27 Aug 1998 12:45:05 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0zBzIv-0001YpC@dutch.mountain>
	for <linux-mips@fnet.fr>; Thu, 27 Aug 1998 12:29:21 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Thu, 27 Aug 1998 12:29:21 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
Reply-To: Richard van den Berg <R.vandenBerg@inter.NL.net>
To: linux-mips@fnet.fr
Subject: Re: Hello World!
In-Reply-To: <XFMail.980826220432.harald.koerfgen@netcologne.de>
Message-ID: <Pine.LNX.3.95.980827122504.430B-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 613
Lines: 20

Hi Harald,

On Wed, 26 Aug 1998, Harald Koerfgen wrote:

> Well, the subject says it all... with one difference. This message was printed
> on a DECstation 5000/133 running linux-2.1.100 from within a user space program
> via /dev/ttyS0.

Way to go Harald!
 
> No tricks, no polling or blocking. Purely interrupt driven with
> copy_from_user() and everything. Looks like my serial device driver shows first
>  signs of life and we're not too far away from a single user shell :-).

Can a program be compiled with the available cross-compiler tools and
libs or is there anything special needed?

Regards,

Richard

From triemer@apt4g.a3nyc.com  Thu Aug 27 16:09:43 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id QAA03631; Thu, 27 Aug 1998 16:09:41 +0200 (MET DST)
Received-Date: Thu, 27 Aug 1998 16:09:41 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id KAA08449
	for <linux-mips@fnet.fr>; Thu, 27 Aug 1998 10:09:18 -0400
Date: Thu, 27 Aug 1998 10:09:13 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: Re: Hello World!
In-Reply-To: <XFMail.980826220432.harald.koerfgen@netcologne.de>
Message-ID: <Pine.LNX.3.96.980827100823.8447A-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 684
Lines: 30

Way cool... 

when do patches pop out?  :)

-Tom





-----------------------------------------------------------------------
Given enough eyeballs all bugs seem shallow.

On Wed, 26 Aug 1998, Harald Koerfgen wrote:

> Hi all!
> 
> Well, the subject says it all... with one difference. This message was printed
> on a DECstation 5000/133 running linux-2.1.100 from within a user space program
> via /dev/ttyS0.
> 
> No tricks, no polling or blocking. Purely interrupt driven with
> copy_from_user() and everything. Looks like my serial device driver shows first
>  signs of life and we're not too far away from a single user shell :-).
> 
> Keep hacking.
> ---
> Regards,
> Harald
> 

From R.vandenBerg@inter.NL.net  Thu Aug 27 19:18:41 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA05139; Thu, 27 Aug 1998 19:18:40 +0200 (MET DST)
Received-Date: Thu, 27 Aug 1998 19:18:40 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-7.Hoorn.NL.net [193.79.46.171] with ESMTP for <linux-mips@fnet.fr>
	id TAA07888 (8.8.8/3.28); Thu, 27 Aug 1998 19:18:39 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0zC5gN-0001YpC@dutch.mountain>
	for <linux-mips@fnet.fr>; Thu, 27 Aug 1998 19:17:59 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Thu, 27 Aug 1998 19:17:58 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
Reply-To: Richard van den Berg <R.vandenBerg@inter.NL.net>
To: linux-mips@fnet.fr
Subject: RE: dependency on rs_init
In-Reply-To: <Pine.SV4.3.91.980827132232.9499A-100000@mech>
Message-ID: <Pine.LNX.3.95.980827190314.430F-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1342
Lines: 29

On Thu, 27 Aug 1998, Gleb O. Rajko wrote:

> > The other one is using the PROM routines (works on all DECstations). This is
> > what promcon.c in arch/mips/dec is for and is intended as a temporary
> > solution until we have charakter device drivers to use as console devices for
> > all DECstations. 
> 
> Why temporary solution ? My experience shows prom console is good 
> enough to have it permanently. It's bug free, the code is small, higher 
> console code allows to emulate linux-like terminal on top of prom console.

I prefer a serial console for a prom console, the prom console on a
DS5k/25 is slower than a terminal connected at 9600 bps.

> I would recommend to look at SPARC/Linux code beginning from 2.1.109 
> (according to vger cvs tree, I don't know what is Linus' version that 
> corresponds to). Around this version console stuff was rewritten and became 
> more clear. Now, SPARC/Linux allows to have several consoles: prom, 
> sbus and ATI Mach (available only on UltraSparc). There are also
> run-time options to select, something like console=prom.

DECstations in the 5k series allow several TURBOchannel Option Modules,
I doubt if you have a framebuffer that one wants the use the promconsole,
perhaps in single user mode in an emergency case. As of Linus' version
2.1.107 framebuffers are used.

Regards,

Richard

From harald.koerfgen@netcologne.de  Thu Aug 27 19:18:33 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA05115; Thu, 27 Aug 1998 19:18:20 +0200 (MET DST)
Received-Date: Thu, 27 Aug 1998 19:18:20 +0200 (MET DST)
Received: from franz.no.dom (dial9-231.netcologne.de [194.8.195.231])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id TAA26995
	for <linux-mips@fnet.fr>; Thu, 27 Aug 1998 19:18:07 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980827191925.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.LNX.3.96.980827100823.8447A-100000@apt4g.a3nyc.com>
Date: Thu, 27 Aug 1998 19:19:25 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: Re: Hello World!
Content-Length: 309
Lines: 16

Fellow DECstation hackers,

On 27-Aug-98 Thomas Riemer wrote:
> Way cool... 
> 
> when do patches pop out?  :)
> 
> -Tom

This may take a few days. At first, I'd like to clean up the stuff a little bit
and then merge the DECstation changes with linux/MIPS-2.1.116.

Please be patient :-).
---
Regards,
Harald

From harald.koerfgen@netcologne.de  Thu Aug 27 19:18:15 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA05093; Thu, 27 Aug 1998 19:18:13 +0200 (MET DST)
Received-Date: Thu, 27 Aug 1998 19:18:13 +0200 (MET DST)
Received: from franz.no.dom (dial9-231.netcologne.de [194.8.195.231])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id TAA26999
	for <linux-mips@fnet.fr>; Thu, 27 Aug 1998 19:18:10 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980827191928.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.SV4.3.91.980827132232.9499A-100000@mech>
Date: Thu, 27 Aug 1998 19:19:28 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: RE: dependency on rs_init
Content-Length: 1685
Lines: 45

Hi,

On 27-Aug-98 Gleb O. Rajko wrote:
> 
> 
> On Wed, 26 Aug 1998, Harald Koerfgen wrote:
> 
>> The other one is using the PROM routines (works on all DECstations). This is
>> what promcon.c in arch/mips/dec is for and is intended as a temporary
>> solution until we have charakter device drivers to use as console devices
>> for
>> all DECstations. 
> 
> Why temporary solution ? My experience shows prom console is good 
> enough to have it permanently. It's bug free, the code is small, higher 
> console code allows to emulate linux-like terminal on top of prom console.
> I would recommend to look at SPARC/Linux code beginning from 2.1.109 
> (according to vger cvs tree, I don't know what is Linus' version that 
> corresponds to). Around this version console stuff was rewritten and became 
> more clear. Now, SPARC/Linux allows to have several consoles: prom, 
> sbus and ATI Mach (available only on UltraSparc). There are also
> run-time options to select, something like console=prom.
> 
> Regards,
> Gleb.

I'd like to see this as a temporary solution because of different reasons:

o The DECstation PROM routines are slow like hell. I don't have exact
measurements at hand, but using the native serial console code seems to be 2-3
times faster.

o The DECstation PROM routines aren't very stable. Printing debugging messages
in exception routines is a no go.

o The DECstation PROM routines are blocking.

o The memory range from 0x80000000 to 0x80030000 is reserved for PROM routines
on DECstations. When the kernel itself doesn't use any PROM routines, the
kernel can be moved to 0x80000000 after loading. This gives us 192KB memory for
free :-).
 
---
Regards,
Harald

From R.vandenBerg@inter.NL.net  Thu Aug 27 21:03:24 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA05981; Thu, 27 Aug 1998 21:03:16 +0200 (MET DST)
Received-Date: Thu, 27 Aug 1998 21:03:16 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-56.Hoorn.NL.net [193.79.46.220] with ESMTP for <linux-mips@fnet.fr>
	id VAA21662 (8.8.8/3.28); Thu, 27 Aug 1998 21:02:59 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0zC6Z4-0001YpC@dutch.mountain>
	for <linux-mips@fnet.fr>; Thu, 27 Aug 1998 20:14:30 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Thu, 27 Aug 1998 21:02:29 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
Reply-To: Richard van den Berg <R.vandenBerg@inter.NL.net>
To: linux-mips@fnet.fr
Subject: Re: Hello World!
In-Reply-To: <XFMail.980827191925.harald.koerfgen@netcologne.de>
Message-ID: <Pine.LNX.3.95.980827195907.430G-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 661
Lines: 21

Hello Harald,

On Thu, 27 Aug 1998, Harald Koerfgen wrote:

> This may take a few days. At first, I'd like to clean up the stuff a little bit
> and then merge the DECstation changes with linux/MIPS-2.1.116.

Yes! Well, I've downloaded 2.1.118 and found out that the MIPS DECstation
related code was outdated and to make a long story short: I didn't get
compiling any further then init... I still can look at the framebuffer
code that's officially included since 2.1.107.

> Please be patient :-).

Should I mail you my little patch - < 10k? How about a TURBOchannel
configuration entry? Well, I still have some bedtime reading stuff
too. :-)

Regards,

Richard

From ralf@uni-koblenz.de  Sat Aug 29 00:20:13 1998
Received: from informatik.uni-koblenz.de ([141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA19693; Sat, 29 Aug 1998 00:20:09 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 00:20:09 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from uni-koblenz.de (pmport-12.uni-koblenz.de [141.26.249.12])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id AAA06324
	for <linux-mips@fnet.fr>; Sat, 29 Aug 1998 00:19:26 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id BAA01444;
	Fri, 28 Aug 1998 01:54:54 +0200
Message-ID: <19980828015454.E1381@uni-koblenz.de>
Date: Fri, 28 Aug 1998 01:54:54 +0200
To: "Gleb O. Rajko" <rajko@mech.math.msu.su>, linux-mips@fnet.fr
Subject: Re: dependency on rs_init
References: <XFMail.980826200009.harald.koerfgen@netcologne.de> <Pine.SV4.3.91.980827132232.9499A-100000@mech>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <Pine.SV4.3.91.980827132232.9499A-100000@mech>; from Gleb O. Rajko on Thu, Aug 27, 1998 at 01:38:31PM +0400
Content-Length: 1216
Lines: 24

On Thu, Aug 27, 1998 at 01:38:31PM +0400, Gleb O. Rajko wrote:

> > The other one is using the PROM routines (works on all DECstations). This is
> > what promcon.c in arch/mips/dec is for and is intended as a temporary
> > solution until we have charakter device drivers to use as console devices for
> > all DECstations. 
> 
> Why temporary solution ? My experience shows prom console is good 
> enough to have it permanently. It's bug free, the code is small, higher 
> console code allows to emulate linux-like terminal on top of prom console.
> I would recommend to look at SPARC/Linux code beginning from 2.1.109 
> (according to vger cvs tree, I don't know what is Linus' version that 
> corresponds to). Around this version console stuff was rewritten and became 
> more clear. Now, SPARC/Linux allows to have several consoles: prom, 
> sbus and ATI Mach (available only on UltraSparc). There are also
> run-time options to select, something like console=prom.

I've just this Tuesday commited a patch of > 13mb which upgrades the kernel
to 2.1.117 to sgi-cvs, so the DECstation people probably haven't yet merged
their kernels with that code.

Having a prom console looks worthwile for MIPS as well.

  Ralf

From R.vandenBerg@inter.NL.net  Fri Aug 28 11:36:52 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id LAA13488; Fri, 28 Aug 1998 11:36:51 +0200 (MET DST)
Received-Date: Fri, 28 Aug 1998 11:36:51 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-50.Hoorn.NL.net [193.79.46.214] with ESMTP for <linux-mips@fnet.fr>
	id LAA14942 (8.8.8/3.28); Fri, 28 Aug 1998 11:36:38 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0zCKsI-0001YpC@dutch.mountain>
	for <linux-mips@fnet.fr>; Fri, 28 Aug 1998 11:31:18 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Fri, 28 Aug 1998 11:31:18 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: Re: Hello World!
In-Reply-To: <199808280622.CAA04453@mailfw2.ford.com>
Message-ID: <Pine.LNX.3.95.980828112409.1830B-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 708
Lines: 21

Hello everybody,

On Fri, 28 Aug 1998, Harald Koerfgen wrote:

> The DECstation related code isn't in the official source tree and it's
> even not commited to main Linux/MIPS CVS repository. In my opinion it
> makes sense to wait until the R3000 specific code is merged with Gleb's
> and Vladimirs R3000 patches. What do you think? Gleb, Vladimir, any
> opinions?

Of course, another person, another ideas. In the future I'll keep my
eyes pointed at decstation.unix-ag.org for MIPS code.

> Do you mean the Lance driver skeleton? I have already downloaded that
> and put it in the DECstation source tree :-) :-).

If you have pl1 I keep my mouth shut and thank you for the compliment! :-)

Regards,

Richard

From rajko@mech.math.msu.su  Fri Aug 28 11:54:04 1998
Received: from mech.math.msu.su (mech.math.msu.su [158.250.33.65]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id LAA13607; Fri, 28 Aug 1998 11:53:56 +0200 (MET DST)
Received-Date: Fri, 28 Aug 1998 11:53:56 +0200 (MET DST)
Received: (from rajko@localhost) by mech.math.msu.su (8.6.10/8.6.10/sasha.040695) id NAA14025; Fri, 28 Aug 1998 13:53:30 +0400
Date: Fri, 28 Aug 1998 13:53:29 +0400 (MSD)
From: "Gleb O. Rajko" <rajko@mech.math.msu.su>
To: linux-mips@fnet.fr
Subject: Re: Hello World!
In-Reply-To: <199808280622.CAA04453@mailfw2.ford.com>
Message-ID: <Pine.SV4.3.91.980828133538.13854B-100000@mech>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 878
Lines: 25


On Fri, 28 Aug 1998, Harald Koerfgen wrote:

> 
> The DECstation related code isn't in the official source tree and it's
> even not commited to main Linux/MIPS CVS repository. In my opinion it
> makes sense to wait until the R3000 specific code is merged with Gleb's
> and Vladimirs R3000 patches. What do you think? Gleb, Vladimir, any
> opinions?
> 

We've already (almost) merged DS 2.1.100 and Baget. There are two files 
I'd like to rewrite (pgtable.h and scall_o32.c) and I think I'll complete 
work at next Monday.

What I'd like to have is a latest changes to "public" DS 2.1.100 in 
arch/mips/kernel, arch/mips/mm, and include/asm-mips. I'll merge them too 
and put my patch on the net.

I'm very interested to sync with latest MIPS kernel because I'd like to 
have a single binary kernel with SGI/Linux (and use standard RH 
distribution after that).

Regards,
Gleb.

From ralf@uni-koblenz.de  Sat Aug 29 00:20:14 1998
Received: from informatik.uni-koblenz.de ([141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA19691; Sat, 29 Aug 1998 00:20:06 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 00:20:06 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from uni-koblenz.de (pmport-12.uni-koblenz.de [141.26.249.12])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id AAA06284
	for <linux-mips@fnet.fr>; Sat, 29 Aug 1998 00:19:08 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id MAA05167;
	Fri, 28 Aug 1998 12:31:55 +0200
Message-ID: <19980828123154.B358@uni-koblenz.de>
Date: Fri, 28 Aug 1998 12:31:54 +0200
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: Emacs problem
References: <19980823223647.12724@alpha.franken.de> <19980824121930.00186@uni-koblenz.de> <19980825225603.43888@alpha.franken.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <19980825225603.43888@alpha.franken.de>; from Thomas Bogendoerfer on Tue, Aug 25, 1998 at 10:56:03PM +0200
Content-Length: 490
Lines: 14

On Tue, Aug 25, 1998 at 10:56:03PM +0200, Thomas Bogendoerfer wrote:

> Another questione does gcc/egcs produce .sdata, .lit4 or .li8 sections
> on Linux/MIPS ?

These sections are mostly being used for code using global pointer
optimization.  .lit8 is also being used for fp code when assembling li.d
macros.

For kernel code global pointer optimization is incompatible
with our current use of $gp as the current pointer; in userland gp
optimization is incompatible with PIC code.

  Ralf

From hkoerfg1@ford.com  Fri Aug 28 08:22:42 1998
Received: from mailfw2.ford.com (mailfw2.ford.com [136.1.1.27]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id IAA12692; Fri, 28 Aug 1998 08:22:41 +0200 (MET DST)
Received-Date: Fri, 28 Aug 1998 08:22:41 +0200 (MET DST)
Received: by mailfw2.ford.com id CAA04453
  (InterLock SMTP Gateway 3.0 for linux-mips@fnet.fr);
  Fri, 28 Aug 1998 02:22:38 -0400
Message-Id: <199808280622.CAA04453@mailfw2.ford.com>
Received: by mailfw2.ford.com (Internal Mail Agent-1);
  Fri, 28 Aug 1998 02:22:38 -0400
Date: Fri, 28 Aug 1998 08:22:36 -0400
From: Harald Koerfgen <hkoerfg1@ford.com>
Reply-To: hkoerfg1@ford.com
Organization: Ford Motor Company
X-Mailer: Mozilla 3.01C (Win95; I)
Mime-Version: 1.0
To: linux-mips@fnet.fr
Subject: Re: Hello World!
References: <Pine.LNX.3.95.980827195907.430G-100000@whale.dutch.mountain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 892
Lines: 24

Hi all, 

Richard van den Berg wrote:
 
> Yes! Well, I've downloaded 2.1.118 and found out that the MIPS DECstation
> related code was outdated and to make a long story short: I didn't get
> compiling any further then init... I still can look at the framebuffer
> code that's officially included since 2.1.107.

The DECstation related code isn't in the official source tree and it's
even not commited to main Linux/MIPS CVS repository. In my opinion it
makes sense to wait until the R3000 specific code is merged with Gleb's
and Vladimirs R3000 patches. What do you think? Gleb, Vladimir, any
opinions?

> Should I mail you my little patch - < 10k? How about a TURBOchannel
> configuration entry? Well, I still have some bedtime reading stuff
> too. :-)

Do you mean the Lance driver skeleton? I have already downloaded that
and put it in the DECstation source tree :-) :-).

Regards,
Harald

From bjs@crc.com  Fri Aug 28 19:38:00 1998
Received: from hobbes.crc.com (hobbes.crc.com [192.251.235.201]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id TAA16466; Fri, 28 Aug 1998 19:37:58 +0200 (MET DST)
Received-Date: Fri, 28 Aug 1998 19:37:58 +0200 (MET DST)
Received: from mail.lsg.crc.com(really [192.251.232.221]) by hobbes.crc.com
	via sendmail with esmtp
	id <m0zCSTC-000L9rC@hobbes.crc.com>
	for <linux-mips@fnet.fr>; Fri, 28 Aug 1998 13:37:54 -0400 (EDT)
	(Smail-3.2 1996-Jul-4 #4 built 1997-Mar-21)
Received: from crc.com (blackbird.lsgsys.crc.com [205.149.42.95]) by mail.lsg.crc.com (8.7.5/8.7.3) with ESMTP id NAA28637; Fri, 28 Aug 1998 13:37:51 -0400
Message-ID: <35E6EAEF.EDF3C61C@crc.com>
Date: Fri, 28 Aug 1998 13:37:51 -0400
From: "Bryan J. Smith" <bjs@crc.com>
Reply-To: bjs@crc.com, b.j.smith@ieee.org
Organization: CRC, IEEE
X-Mailer: Mozilla 4.06 [en] (WinNT; U)
MIME-Version: 1.0
To: linux-mips@fnet.fr
Subject: [English]  I have an old DECstation 5000 and want to run Linux/MIPS ...
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 1464
Lines: 31

[English]  I have an old DECstation 5000 and want to run Linux/MIPS ...

Interested in any help you can give me in finding out if I can run
Linux/MIPS on this system.  It is a U.S. government owned system that
has outlived its usefulness.  But we hope it would make a great
X-terminal (if supported) or basic terminal.  Otherwise, it goes in the
U.S. government surplus bin.

-- Bryan J. Smith
    Software Engineer
    Coleman Aerospace
    Orlando, FL

--
***************************************************************
BRYAN J. SMITH                                         ENGINEER
===============================================================
mailto:bjs@crc.com                    mailto:b.j.smith@ieee.org
===============================================================
DISCLAIMER:  Any statements, opinions, comments, etc... are
not designed to harm anyone or anything in any way.  You cannot
hold my employer, educator, colleagues, relatives, society
(well maybe) or anyone directly or indirectly associated with
me responsbile for those statements, opinions, comments, etc...
I make directly or indirectly (unless otherwise noted).  I will
not be held responsible for any of the above unless a law has
been literally broken by me in such an event (and I shall be
made fully aware of such violations prior to any legal action
so I may try to "correct" it).  <-- Sorry for the mess ... ;^(
***************************************************************


From R.vandenBerg@inter.NL.net  Fri Aug 28 23:52:47 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA18815; Fri, 28 Aug 1998 23:52:47 +0200 (MET DST)
Received-Date: Fri, 28 Aug 1998 23:52:47 +0200 (MET DST)
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id XAA05934; Fri, 28 Aug 1998 23:52:45 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-2.Hoorn.NL.net [193.79.46.166] with ESMTP
	id XAA20800 (8.8.8/3.28); Fri, 28 Aug 1998 23:49:25 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0zCWNN-0001YpC@dutch.mountain>
	for <bjs@crc.com>; Fri, 28 Aug 1998 23:48:09 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Fri, 28 Aug 1998 23:48:09 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: "Bryan J. Smith" <bjs@crc.com>
cc: linux-mips@fnet.fr
Subject: Re: [English]  I have an old DECstation 5000 and want to run Linux/MIPS ...
In-Reply-To: <35E6EAEF.EDF3C61C@crc.com>
Message-ID: <Pine.LNX.3.95.980828234735.3407C-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 722
Lines: 20

On Fri, 28 Aug 1998, Bryan J. Smith wrote:

> Interested in any help you can give me in finding out if I can run
> Linux/MIPS on this system.  It is a U.S. government owned system that

At the moment Linux MIPS is only able to boot, have a look at
http://decstation.unix-ag.org/ and
http://www.inter.nl.net/users/schnecke/html/mips/ for details. 

> has outlived its usefulness.  But we hope it would make a great
> X-terminal (if supported) or basic terminal.  Otherwise, it goes in the
> U.S. government surplus bin.

NetBSD runs on DECstations and I used my 5000/25 as a X terminal using
NetBSD, nowadays I reboot it with Linux test kernels so often that I'll
wait till Linux runs useful on it. :-) 

Regards,

Richard

From R.vandenBerg@inter.NL.net  Fri Aug 28 23:52:49 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA18819; Fri, 28 Aug 1998 23:52:48 +0200 (MET DST)
Received-Date: Fri, 28 Aug 1998 23:52:48 +0200 (MET DST)
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id XAA05937; Fri, 28 Aug 1998 23:52:47 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-2.Hoorn.NL.net [193.79.46.166] with ESMTP for <linux-mips@fnet.fr>
	id XAA20804 (8.8.8/3.28); Fri, 28 Aug 1998 23:49:26 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0zCWO1-0001ZXC@dutch.mountain>
	for <linux-mips@fnet.fr>; Fri, 28 Aug 1998 23:48:49 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Fri, 28 Aug 1998 23:48:49 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: DECstation boot sequence
Message-ID: <Pine.LNX.3.95.980828234812.3407D-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 443
Lines: 13

Hi all,

It came to mind that if we want to use either a framebuffer or a serial
console as the console that it might be conveniant to run the TURBOchannel
detection / initialization earlier as address detection and calculation
is done at the same time and our drivers like to have an address.

I've put tc_init() after the delay loop calibration and that worked fine
on a DS5k/25. Liked to share this, have a nice weekend.

Regards,

Richard

From tsbogend@alpha.franken.de  Sat Aug 29 02:03:41 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id CAA20873; Sat, 29 Aug 1998 02:03:40 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 02:03:40 +0200 (MET DST)
Received: from alpha.franken.de (tsbogend@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id CAA06904; Sat, 29 Aug 1998 02:03:38 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id CAA05988;
	Sat, 29 Aug 1998 02:01:23 +0200
Message-ID: <19980829020123.18903@alpha.franken.de>
Date: Sat, 29 Aug 1998 02:01:23 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Magnum 4000/M700 kernel working again
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
Content-Length: 375
Lines: 12

Hi,

after reinstalling all the work I've done during the last months into
CVS, I'm proud to announce, that the current CVS tree compiles and works
on my Olivetti M700 again.

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From tsbogend@alpha.franken.de  Sat Aug 29 02:10:34 1998
Received: from louis-blanc.univ-evry.fr (louis-blanc.univ-evry.fr [194.199.90.2]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id CAA21083; Sat, 29 Aug 1998 02:10:33 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 02:10:33 +0200 (MET DST)
Received: from alpha.franken.de (tsbogend@alpha.franken.de [193.175.24.68]) by louis-blanc.univ-evry.fr with ESMTP (8.8.8/980318/louis-blanc); id CAA06953; Sat, 29 Aug 1998 02:10:31 +0200 (MET DST)
Received: (from tsbogend@localhost)
	by alpha.franken.de (8.8.7/8.8.5) id CAA06005;
	Sat, 29 Aug 1998 02:08:18 +0200
Message-ID: <19980829020818.25410@alpha.franken.de>
Date: Sat, 29 Aug 1998 02:08:18 +0200
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: ralf@uni-koblenz.de
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: Emacs problem
References: <19980823223647.12724@alpha.franken.de> <19980824121930.00186@uni-koblenz.de> <19980825225603.43888@alpha.franken.de> <19980828123154.B358@uni-koblenz.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.85
In-Reply-To: <19980828123154.B358@uni-koblenz.de>; from ralf@uni-koblenz.de on Fri, Aug 28, 1998 at 12:31:54PM +0200
Content-Length: 892
Lines: 22

On Fri, Aug 28, 1998 at 12:31:54PM +0200, ralf@uni-koblenz.de wrote:
> On Tue, Aug 25, 1998 at 10:56:03PM +0200, Thomas Bogendoerfer wrote:
> 
> > Another questione does gcc/egcs produce .sdata, .lit4 or .li8 sections
> > on Linux/MIPS ?
> 
> These sections are mostly being used for code using global pointer
> optimization.  .lit8 is also being used for fp code when assembling li.d
> macros.

as they don't show up in the temacs binary, I'll ignore them for unexec().

With a crude hack in unexec(), I now have a emcas binary, which will show up
an empty X window. Looking with strace and tcpdump it looks like emacs
tries to do more X work, but doesn't succeed. Stuff for the weekend ...

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

From mitch@execpc.com  Sat Aug 29 03:16:46 1998
Received: from mailgw02.execpc.com (mailgw02.execpc.com [169.207.3.78]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id DAA21394; Sat, 29 Aug 1998 03:16:45 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 03:16:45 +0200 (MET DST)
Received: from earth.execpc.com (earth.execpc.com [169.207.16.1])
	by mailgw02.execpc.com (8.9.0) id UAA00085;
	Fri, 28 Aug 1998 20:15:49 -0500 (CDT)
Received: (from mitch@localhost) by earth.execpc.com (8.9.0) id UAA08621; Fri, 28 Aug 1998 20:15:49 -0500 (CDT)
Message-ID: <19980828201549.21972@execpc.com>
Date: Fri, 28 Aug 1998 20:15:49 -0500
From: Mitchell Blank Jr <mitch@execpc.com>
To: linux-mips@fnet.fr
Cc: bjs@crc.com
Subject: Re: [English]  I have an old DECstation 5000 and want to run Linux/MIPS ...
References: <35E6EAEF.EDF3C61C@crc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84e-execpc
In-Reply-To: <35E6EAEF.EDF3C61C@crc.com>; from Bryan J. Smith on Fri, Aug 28, 1998 at 01:37:51PM -0400
Content-Length: 751
Lines: 17

Bryan J. Smith wrote:
> [English]  I have an old DECstation 5000 and want to run Linux/MIPS ...

First, which 5000?  There's many many models of 5000, all the way from the
lowly Personal Decstation 5000/20 all the way to the mighty 5000/260.

As the other poster pointed out, the *BSDs are quite a bit farther along
in their DECstation support.  You can use either NetBSD (see
http://www.netbsd.org/Ports/pmax/) or OpenBSD (see
http://www.openbsd.org/pmax.html).  I've run OpenBSD on my PD5000/25 and
my 5000/125 with good results.  The only snag I've run accross is that some
of the more esoteric color framebuffer cards aren't supported.

Personally, I'll be happer with Linux on my boxen, but for the time being
I'd suggest grabbing a BSD.

-Mitch

From triemer@apt4g.a3nyc.com  Sat Aug 29 09:38:26 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id JAA01451; Sat, 29 Aug 1998 09:38:25 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 09:38:25 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id DAA10804
	for <linux-mips@fnet.fr>; Sat, 29 Aug 1998 03:38:15 -0400
Date: Sat, 29 Aug 1998 03:38:13 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: DC7085
Message-ID: <Pine.LNX.3.96.980829033523.10141A-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 558
Lines: 14

Anyone have any idea where to get documentation on the DC7085 serial
board.  Or possibly the DZ-11?

I've checked the likely places that I can think of - with little luck.

Also the documentation for the AMD C-LANCE driver posted on the 
web site - will that documentation serve adequately for the AMD LANCE
driver?  It looks like it would - but before I spend time reading dry
documentation - maybe someone could give a yeah or nay.

-Tom

-----------------------------------------------------------------------
Given enough eyeballs all bugs seem shallow.

From engel@numerik.math.uni-siegen.de  Sat Aug 29 10:20:58 1998
Received: from fourier.numerik.math.uni-siegen.de (fourier.numerik.math.uni-siegen.de [141.99.2.230]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id KAA02587; Sat, 29 Aug 1998 10:20:57 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 10:20:57 +0200 (MET DST)
Received: (from engel@localhost) by fourier.numerik.math.uni-siegen.de (Mailhost) id KAA07970 for linux-mips@fnet.fr; Sat, 29 Aug 1998 10:20:46 +0200 (MET DST)
From: Michael Engel <engel@numerik.math.uni-siegen.de>
Message-Id: <199808290820.KAA07970@fourier.numerik.math.uni-siegen.de>
Subject: Re: DC7085
To: linux-mips@fnet.fr
Date: Sat, 29 Aug 1998 10:20:45 +0200 (MET DST)
In-Reply-To: <Pine.LNX.3.96.980829033523.10141A-100000@apt4g.a3nyc.com> from "Thomas Riemer" at Aug 29, 98 03:38:13 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 696
Lines: 21


Hi,

> Anyone have any idea where to get documentation on the DC7085 serial
> board.  Or possibly the DZ-11?
> 
> I've checked the likely places that I can think of - with little luck.

The DS2100/3100 (http://decstation.unix-ag.org/docs/dec_docs/DS3100.ps.gz)
contains information on the DZ-11.

> Also the documentation for the AMD C-LANCE driver posted on the 
> web site - will that documentation serve adequately for the AMD LANCE
> driver?  It looks like it would - but before I spend time reading dry
> documentation - maybe someone could give a yeah or nay.

It should be sufficiently similar, perhaps modulo some bugs (I was told
the original LANCE was quite buggy).

regards,
	Michael

From triemer@apt4g.a3nyc.com  Sat Aug 29 11:13:37 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id LAA02809; Sat, 29 Aug 1998 11:13:36 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 11:13:36 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id FAA11007
	for <linux-mips@fnet.fr>; Sat, 29 Aug 1998 05:13:38 -0400
Date: Sat, 29 Aug 1998 05:13:38 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: Re: DC7085
In-Reply-To: <199808290820.KAA07970@fourier.numerik.math.uni-siegen.de>
Message-ID: <Pine.LNX.3.96.980829051251.10141B-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 473
Lines: 16



> The DS2100/3100 (http://decstation.unix-ag.org/docs/dec_docs/DS3100.ps.gz)
> contains information on the DZ-11.

This address punts with a "no such document found" error.

> 
> > Also the documentation for the AMD C-LANCE driver posted on the 
> > web site - will that documentation serve adequately for the AMD LANCE
> > driver?  It looks like it would - but before I spend time reading dry
> > documentation - maybe someone could give a yeah or nay.
> 
Thanks.

-Tom

From R.vandenBerg@inter.NL.net  Sat Aug 29 11:23:11 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id LAA03336; Sat, 29 Aug 1998 11:23:10 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 11:23:10 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-38.Hoorn.NL.net [193.79.46.202] with ESMTP for <linux-mips@fnet.fr>
	id LAA29379 (8.8.8/3.28); Sat, 29 Aug 1998 11:23:09 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0zChDU-0001YpC@dutch.mountain>
	for <linux-mips@fnet.fr>; Sat, 29 Aug 1998 11:22:40 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Sat, 29 Aug 1998 11:22:39 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: Re: DC7085
In-Reply-To: <Pine.LNX.3.96.980829033523.10141A-100000@apt4g.a3nyc.com>
Message-ID: <Pine.LNX.3.95.980829112228.411B-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 698
Lines: 20

Hi Thomas,

On Sat, 29 Aug 1998, Thomas Riemer wrote:

> Also the documentation for the AMD C-LANCE driver posted on the 
> web site - will that documentation serve adequately for the AMD LANCE
> driver?  It looks like it would - but before I spend time reading dry
> documentation - maybe someone could give a yeah or nay.

Short answer: yeah. :-)

Well, Miguel doesn't mention the book in his sunlance.c, but he
might as well had it beside him writing the driver. After reading the
AMD book I doubt you have any questions regarding the Am79C90 chip,
aka C-LANCE. C-LANCE is an enhanced LANCE (Am7990 chip) pin-for-pin
equivalent. A table and 4 pages describe the enhancements.

Regards,

Richard

From engel@numerik.math.uni-siegen.de  Sat Aug 29 12:20:58 1998
Received: from fourier.numerik.math.uni-siegen.de (fourier.numerik.math.uni-siegen.de [141.99.2.230]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id MAA03601; Sat, 29 Aug 1998 12:20:57 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 12:20:57 +0200 (MET DST)
Received: (from engel@localhost) by fourier.numerik.math.uni-siegen.de (Mailhost) id MAA08120 for linux-mips@fnet.fr; Sat, 29 Aug 1998 12:21:07 +0200 (MET DST)
From: Michael Engel <engel@numerik.math.uni-siegen.de>
Message-Id: <199808291021.MAA08120@fourier.numerik.math.uni-siegen.de>
Subject: Re: DC7085
To: linux-mips@fnet.fr
Date: Sat, 29 Aug 1998 12:21:06 +0200 (MET DST)
In-Reply-To: <Pine.LNX.3.96.980829051251.10141B-100000@apt4g.a3nyc.com> from "Thomas Riemer" at Aug 29, 98 05:13:38 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 333
Lines: 13


> > The DS2100/3100 (http://decstation.unix-ag.org/docs/dec_docs/DS3100.ps.gz)
> > contains information on the DZ-11.
> 
> This address punts with a "no such document found" error.

Aargh, sorry!

http://decstation.unix-ag.org/docs/dec_docs/DS3100.ps.Z
is the correct address ... (also corrected on the web page)

regards,
	Michael

From ralf@uni-koblenz.de  Sun Aug 30 01:14:58 1998
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id BAA16190; Sun, 30 Aug 1998 01:14:57 +0200 (MET DST)
Received-Date: Sun, 30 Aug 1998 01:14:57 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from uni-koblenz.de (pmport-17.uni-koblenz.de [141.26.249.17])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id BAA28248
	for <linux-mips@fnet.fr>; Sun, 30 Aug 1998 01:14:54 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id RAA08689;
	Sat, 29 Aug 1998 17:54:17 +0200
Message-ID: <19980829175417.D7153@uni-koblenz.de>
Date: Sat, 29 Aug 1998 17:54:17 +0200
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, ketil@ii.uib.no
Cc: linux-kernel@vger.rutgers.edu,
        Harald Koerfgen <harald.koerfgen@netcologne.de>, linux-mips@fnet.fr
Subject: Re: Microchanel Alphas?
References: <KETIL-87g1ei6gn7.fsf@tosca.infotek.no> <m0zC5KT-000aPKC@the-village.bc.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <m0zC5KT-000aPKC@the-village.bc.nu>; from Alan Cox on Thu, Aug 27, 1998 at 05:55:20PM +0100
Content-Length: 603
Lines: 14

On Thu, Aug 27, 1998 at 05:55:20PM +0100, Alan Cox wrote:

> > Last time I looked, Linux didn't support TC, and unless you're willing 
> > to do the coding yourself, it probably never will.  One of the *BSDs
> > supported the bus, but at the cost of something else, graphics, I
> > think.  You might want to check it out.
> 
> For any turbochannel work it is probably worth talking to the MIPS hackers
> first too. Most bigger MIPS Dec boxes were turbo channel except the 5400

Harald Koerfgen <harald.koerfgen@netcologne.de> is currently coordinating
the effort for the MIPS based DECstations.

  Ralf

From triemer@apt4g.a3nyc.com  Sat Aug 29 18:13:08 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA09932; Sat, 29 Aug 1998 18:13:05 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 18:13:05 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id MAA11326
	for <linux-mips@fnet.fr>; Sat, 29 Aug 1998 12:13:11 -0400
Date: Sat, 29 Aug 1998 12:13:07 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: Re: DC7085
In-Reply-To: <Pine.LNX.3.95.980829112228.411B-100000@whale.dutch.mountain>
Message-ID: <Pine.LNX.3.96.980829121243.10141C-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1001
Lines: 31

I'll take this as a strong hint that I should begin with sunlance.c
as the skeleton.

-Tom

-----------------------------------------------------------------------
Given enough eyeballs all bugs seem shallow.

On Sat, 29 Aug 1998, Richard van den Berg wrote:

> Hi Thomas,
> 
> On Sat, 29 Aug 1998, Thomas Riemer wrote:
> 
> > Also the documentation for the AMD C-LANCE driver posted on the 
> > web site - will that documentation serve adequately for the AMD LANCE
> > driver?  It looks like it would - but before I spend time reading dry
> > documentation - maybe someone could give a yeah or nay.
> 
> Short answer: yeah. :-)
> 
> Well, Miguel doesn't mention the book in his sunlance.c, but he
> might as well had it beside him writing the driver. After reading the
> AMD book I doubt you have any questions regarding the Am79C90 chip,
> aka C-LANCE. C-LANCE is an enhanced LANCE (Am7990 chip) pin-for-pin
> equivalent. A table and 4 pages describe the enhancements.
> 
> Regards,
> 
> Richard
> 

From R.vandenBerg@inter.NL.net  Sat Aug 29 19:02:38 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA10177; Sat, 29 Aug 1998 19:02:37 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 19:02:37 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-5.Hoorn.NL.net [193.79.46.169] with ESMTP for <linux-mips@fnet.fr>
	id TAA03013 (8.8.8/3.28); Sat, 29 Aug 1998 19:02:35 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0zCo0V-0001YpC@dutch.mountain>
	for <linux-mips@fnet.fr>; Sat, 29 Aug 1998 18:37:43 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Sat, 29 Aug 1998 18:37:42 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: Re: DC7085
In-Reply-To: <Pine.LNX.3.96.980829121243.10141C-100000@apt4g.a3nyc.com>
Message-ID: <Pine.LNX.3.95.980829182812.1921C-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 452
Lines: 14

On Sat, 29 Aug 1998, Thomas Riemer wrote:

> I'll take this as a strong hint that I should begin with sunlance.c
> as the skeleton.

If it's for your 2100 I'll give you the strongest possible hint: at
http://www.inter.nl.net/users/schnecke/html/mips/lance.html there is a
patch available that contains a declance.c which is sunlance.c with most
of the sparc specific code stripped off and on a 5000/25 it shows the
hardware address.

Regards,

Richard

From triemer@apt4g.a3nyc.com  Sat Aug 29 19:35:26 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id TAA10324; Sat, 29 Aug 1998 19:35:24 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 19:35:24 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id NAA11384
	for <linux-mips@fnet.fr>; Sat, 29 Aug 1998 13:35:34 -0400
Date: Sat, 29 Aug 1998 13:35:32 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: Re: DC7085
In-Reply-To: <Pine.LNX.3.95.980829182812.1921C-100000@whale.dutch.mountain>
Message-ID: <Pine.LNX.3.96.980829133341.10141D-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 866
Lines: 27

Ok - htat URL sounds like a quite reasonable hint .... gladly accepted.

Any hints as to where to start with the DC7085 serial driver - i.e
does anyone know what's the "closest" serial driver code out there?

-Tom

-----------------------------------------------------------------------
Given enough eyeballs all bugs seem shallow.

On Sat, 29 Aug 1998, Richard van den Berg wrote:

> On Sat, 29 Aug 1998, Thomas Riemer wrote:
> 
> > I'll take this as a strong hint that I should begin with sunlance.c
> > as the skeleton.
> 
> If it's for your 2100 I'll give you the strongest possible hint: at
> http://www.inter.nl.net/users/schnecke/html/mips/lance.html there is a
> patch available that contains a declance.c which is sunlance.c with most
> of the sparc specific code stripped off and on a 5000/25 it shows the
> hardware address.
> 
> Regards,
> 
> Richard
> 

From engel@numerik.math.uni-siegen.de  Sat Aug 29 20:09:11 1998
Received: from fourier.numerik.math.uni-siegen.de (fourier.numerik.math.uni-siegen.de [141.99.2.230]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id UAA10505; Sat, 29 Aug 1998 20:09:10 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 20:09:10 +0200 (MET DST)
Received: (from engel@localhost) by fourier.numerik.math.uni-siegen.de (Mailhost) id UAA08601 for linux-mips@fnet.fr; Sat, 29 Aug 1998 20:09:20 +0200 (MET DST)
From: Michael Engel <engel@numerik.math.uni-siegen.de>
Message-Id: <199808291809.UAA08601@fourier.numerik.math.uni-siegen.de>
Subject: Re: DC7085
To: linux-mips@fnet.fr
Date: Sat, 29 Aug 1998 20:09:19 +0200 (MET DST)
In-Reply-To: <Pine.LNX.3.96.980829133341.10141D-100000@apt4g.a3nyc.com> from "Thomas Riemer" at Aug 29, 98 01:35:32 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 488
Lines: 15


> Ok - htat URL sounds like a quite reasonable hint .... gladly accepted.
> 
> Any hints as to where to start with the DC7085 serial driver - i.e
> does anyone know what's the "closest" serial driver code out there?

I have some code that handles the keyboard, but that is rather a hack and
not interrupt-driven at all. But it works ... I'll have to dig it out
of my source tree later.

The DC7085 is a rather primitive chip compared to the 16550 or (yuck!) the
8530.

regards,
	Michael

From triemer@apt4g.a3nyc.com  Sat Aug 29 23:31:29 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA12491; Sat, 29 Aug 1998 23:31:27 +0200 (MET DST)
Received-Date: Sat, 29 Aug 1998 23:31:27 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id RAA11544
	for <linux-mips@fnet.fr>; Sat, 29 Aug 1998 17:31:41 -0400
Date: Sat, 29 Aug 1998 17:31:41 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: Re: DC7085
In-Reply-To: <Pine.LNX.3.95.980829182812.1921C-100000@whale.dutch.mountain>
Message-ID: <Pine.LNX.3.96.980829172851.10141G-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 2111
Lines: 82

Here are patches give the vanilla
2.1.100 from the web site +
the patch at http://www.inter.nl.net/users/schnecke/html/mips/lance.html

It prints out correctly eth0: LANCE 08:00:2b:15:44:45 
(hardware address is actually correct)

-Tom Riemer

-----------------------------------------------------
--------------  Patches below here ------------------
-----------------------------------------------------
*** linux-1.2.100_pl1/drivers/net/declance.c	Sat Aug 29 17:17:31 1998
--- linux/drivers/net/declance.c	Sat Aug 29 17:06:14 1998
***************
*** 51,56 ****
--- 51,67 ----
  #include <linux/netdevice.h>
  #include <linux/etherdevice.h>
  
+ /* On decstation 2/3100s without tc.c included system_base
+    is not defined  - triemer */ 
+ #ifndef CONFIG_TC
+ 
+ /* Base address on decstation 2100/3100 of LANCE ethernet board */
+ static unsigned long system_base = 0xb8000000;
+ 
+ /* Base Address of RTC address space + 1 */
+ #define RTC_OFFSET (0xBD000001)
+ #endif
+ 
  /* Define: 2^4 Tx buffers and 2^4 Rx buffers */
  #ifndef LANCE_LOG_TX_BUFFERS
  #define LANCE_LOG_TX_BUFFERS 4
***************
*** 896,902 ****
--- 907,917 ----
  	 * chunk
  	 */
  
+ #ifdef CONFIG_TC
  	dev->base_addr = system_base + 0xc0000;
+ #else
+ 	dev->base_addr = system_base;
+ #endif
  
  	dev->irq = 5;
  
***************
*** 905,922 ****
  	 * initialization block.
  	 */
  
- 	/* these values are correct for my (ravdberg@inter.nl.net) Personal
- 	 * DECstation 5000/25
- 	dev->dev_addr[0] = 0x08;
- 	dev->dev_addr[1] = 0x00;
- 	dev->dev_addr[2] = 0x2b;
- 	dev->dev_addr[3] = 0x30;
- 	dev->dev_addr[4] = 0x8d;
- 	dev->dev_addr[5] = 0x2b;
- 	*/
- 
  	for (i = 0; i < 6; i++){
  		dev->dev_addr[i] = esar_base[system_base + 0x80002 + i * 4];
  		printk("%2.2x%c", dev->dev_addr[i], i == 5 ? ' ': ':');
  	}
  
--- 920,931 ----
  	 * initialization block.
  	 */
  
  	for (i = 0; i < 6; i++){
+ #ifdef CONFIG_TC
  		dev->dev_addr[i] = esar_base[system_base + 0x80002 + i * 4];
+ #else
+ 		dev->dev_addr[i] = esar_base[RTC_OFFSET + i *4];
+ #endif
  		printk("%2.2x%c", dev->dev_addr[i], i == 5 ? ' ': ':');
  	}
  


From R.vandenBerg@inter.NL.net  Sun Aug 30 10:56:35 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id KAA20912; Sun, 30 Aug 1998 10:56:35 +0200 (MET DST)
Received-Date: Sun, 30 Aug 1998 10:56:35 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-34.Hoorn.NL.net [193.79.46.198] with ESMTP for <linux-mips@fnet.fr>
	id KAA21419 (8.8.8/3.28); Sun, 30 Aug 1998 10:56:33 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0zD38z-0001YpC@dutch.mountain>
	for <linux-mips@fnet.fr>; Sun, 30 Aug 1998 10:47:29 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Sun, 30 Aug 1998 10:47:28 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: Re: DC7085
In-Reply-To: <Pine.LNX.3.96.980829172851.10141G-100000@apt4g.a3nyc.com>
Message-ID: <Pine.LNX.3.95.980830104659.1921F-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 397
Lines: 20

On Sat, 29 Aug 1998, Thomas Riemer wrote:

> Here are patches give the vanilla
> 2.1.100 from the web site +
> the patch at http://www.inter.nl.net/users/schnecke/html/mips/lance.html
> 
> It prints out correctly eth0: LANCE 08:00:2b:15:44:45 
> (hardware address is actually correct)

Of course. :-)
 
> -Tom Riemer

Thanks!

BTW, what video controller chip does your DS have?

Regards,

Richard

From harald.koerfgen@netcologne.de  Sun Aug 30 16:29:39 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id QAA24528; Sun, 30 Aug 1998 16:29:38 +0200 (MET DST)
Received-Date: Sun, 30 Aug 1998 16:29:38 +0200 (MET DST)
Received: from franz.no.dom (dial5-108.netcologne.de [194.8.195.108])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id QAA20579
	for <linux-mips@fnet.fr>; Sun, 30 Aug 1998 16:29:34 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980830163052.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.LNX.3.96.980829172851.10141G-100000@apt4g.a3nyc.com>
Date: Sun, 30 Aug 1998 16:30:52 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: Re: DC7085
Content-Length: 2119
Lines: 77

Hi all,

On 29-Aug-98 Thomas Riemer wrote:
> Here are patches give the vanilla
> 2.1.100 from the web site +
> the patch at http://www.inter.nl.net/users/schnecke/html/mips/lance.html
> 
> It prints out correctly eth0: LANCE 08:00:2b:15:44:45 
> (hardware address is actually correct)
> 
> -Tom Riemer
> 

[some snippage]

> + /* On decstation 2/3100s without tc.c included system_base
> +    is not defined  - triemer */ 
> + #ifndef CONFIG_TC
> + 
> + /* Base address on decstation 2100/3100 of LANCE ethernet board */
> + static unsigned long system_base = 0xb8000000;
> + 
> + /* Base Address of RTC address space + 1 */
> + #define RTC_OFFSET (0xBD000001)
> + #endif

[...]

> + #ifdef CONFIG_TC
>       dev->base_addr = system_base + 0xc0000;
> + #else
> +     dev->base_addr = system_base;
> + #endif
>   
>       dev->irq = 5;

[...]

>       for (i = 0; i < 6; i++){
> + #ifdef CONFIG_TC
>               dev->dev_addr[i] = esar_base[system_base + 0x80002 + i * 4];
> + #else
> +             dev->dev_addr[i] = esar_base[RTC_OFFSET + i *4];
> + #endif
>               printk("%2.2x%c", dev->dev_addr[i], i == 5 ? ' ': ':');
>       }
>   

A maybe better way to achieve this, could be:

[TURBOCHANNEL and IOASIC are defined in asm/dec/tc.h]

        if (TURBOCHANNEL) {
                if (IOASIC) {
                        esar_base = (char *)(system_base + 0x80000);
                        dev->base_addr = system_base + 0xc0000;
                }
        } else {                /* dunno if that works on DS5100 */
                esar_base = (char *)0xbd000001;
                dev->base_addr = 0xb8000000;
        }

        [...]

        for (i = 0; i < 6; i++) {
                dev->dev_addr[i] = esar_base[i * 4];
                printk("%2.2x%c", dev->dev_addr[i], i == 5 ? ' ': ':');
        }

This should work on all DECstations and such the kernel would work regardless
if a particular DECstation has a TURBOchannel or not. On the other hand,
consider this as a temporary fix, because this code isn't aware of TURBOchannel
option modules and thus will not work on DS5k/200.

---
Regards,
Harald

From harald.koerfgen@netcologne.de  Sun Aug 30 16:29:41 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id QAA24534; Sun, 30 Aug 1998 16:29:40 +0200 (MET DST)
Received-Date: Sun, 30 Aug 1998 16:29:40 +0200 (MET DST)
Received: from franz.no.dom (dial5-108.netcologne.de [194.8.195.108])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id QAA20583;
	Sun, 30 Aug 1998 16:29:36 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980830163055.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.LNX.3.96.980829133341.10141D-100000@apt4g.a3nyc.com>
Date: Sun, 30 Aug 1998 16:30:55 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: Re: DC7085
Cc: olivier.lebaillif@ifrsys.com
Content-Length: 1032
Lines: 36

Hi all,

On 29-Aug-98 Thomas Riemer wrote:
> Any hints as to where to start with the DC7085 serial driver - i.e
> does anyone know what's the "closest" serial driver code out there?
> 
> -Tom

Olivier Lebaillif <olivier.lebaillif@ifrsys.com> has done some work on a DZ
serial device driver:

On 03-Jul-98 Olivier A. D. Lebaillif wrote on linux-mips@fnet.fr:

[...]
> I started to work on a device driver for DECStations to support the DZ
> chipset not too long ago. I reached a point in the development where I
> have a "working" base for my device driver but I would like to get
> inputs from other developers on what direction to take for the support
> of the DZ chipset.
[...]

And here is a part of a message, Olivier mailed to me (hope you don't mind,
Olivier):

On 08-Jul-98 Olivier A. D. Lebaillif wrote:

[...]
> My driver seems fairely stable (as much as I can tell...) we might try
> to use it.
[...]

Unfortunately Olivier seems to be very busy, because I haven't heard anything
from him since then. 
---
Regards,
Harald

From triemer@apt4g.a3nyc.com  Sun Aug 30 17:33:47 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id RAA24949; Sun, 30 Aug 1998 17:33:46 +0200 (MET DST)
Received-Date: Sun, 30 Aug 1998 17:33:46 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id LAA12625
	for <linux-mips@fnet.fr>; Sun, 30 Aug 1998 11:33:49 -0400
Date: Sun, 30 Aug 1998 11:33:48 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: Re: DC7085
In-Reply-To: <Pine.LNX.3.95.980830104659.1921F-100000@whale.dutch.mountain>
Message-ID: <Pine.LNX.3.96.980830112947.12618C-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 252
Lines: 15

> 
> Thanks!
> 
> BTW, what video controller chip does your DS have?

Its got the VFB01 according to the docs - the monitor I have is 
monochrome - so I'm guessing that the controller chip is the
monochrome version.

-Tom
> 
> Regards,
> 
> Richard
> 

From triemer@apt4g.a3nyc.com  Sun Aug 30 21:04:59 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA26925; Sun, 30 Aug 1998 21:04:58 +0200 (MET DST)
Received-Date: Sun, 30 Aug 1998 21:04:58 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id PAA12808
	for <linux-mips@fnet.fr>; Sun, 30 Aug 1998 15:05:10 -0400
Date: Sun, 30 Aug 1998 15:05:08 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: Irqs
Message-ID: <Pine.LNX.3.96.980830150351.12618F-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 310
Lines: 12

I noticed the line

dev->irq = 5 

in declance.c....

How does the linux stuff prevent clashes on interrupt numbers?  Is
there a list somewhere that is used to prevent interrupt clashes?

-Tom
-----------------------------------------------------------------------
Given enough eyeballs all bugs seem shallow.

From engel@numerik.math.uni-siegen.de  Sun Aug 30 21:50:50 1998
Received: from fourier.numerik.math.uni-siegen.de (fourier.numerik.math.uni-siegen.de [141.99.2.230]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA28588; Sun, 30 Aug 1998 21:50:49 +0200 (MET DST)
Received-Date: Sun, 30 Aug 1998 21:50:49 +0200 (MET DST)
Received: (from engel@localhost) by fourier.numerik.math.uni-siegen.de (Mailhost) id VAA09710 for linux-mips@fnet.fr; Sun, 30 Aug 1998 21:50:59 +0200 (MET DST)
From: Michael Engel <engel@numerik.math.uni-siegen.de>
Message-Id: <199808301950.VAA09710@fourier.numerik.math.uni-siegen.de>
Subject: Re: Irqs
To: linux-mips@fnet.fr
Date: Sun, 30 Aug 1998 21:50:59 +0200 (MET DST)
In-Reply-To: <Pine.LNX.3.96.980830150351.12618F-100000@apt4g.a3nyc.com> from "Thomas Riemer" at Aug 30, 98 03:05:08 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 393
Lines: 16


> I noticed the line
> 
> dev->irq = 5 
> 
> in declance.c....
> 
> How does the linux stuff prevent clashes on interrupt numbers?  Is
> there a list somewhere that is used to prevent interrupt clashes?

The IRQs for the onboard peripherals are fixed, so there isn't a chance
of a clash. The code above will not work for a TurboChannel Lance option 
module, I'm afraid ...

regards,
	Michael

From harald.koerfgen@netcologne.de  Sun Aug 30 21:51:06 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id VAA28611; Sun, 30 Aug 1998 21:51:03 +0200 (MET DST)
Received-Date: Sun, 30 Aug 1998 21:51:03 +0200 (MET DST)
Received: from franz.no.dom (dial1-10.netcologne.de [194.8.196.10])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id VAA28912
	for <linux-mips@fnet.fr>; Sun, 30 Aug 1998 21:50:52 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980830215210.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.LNX.3.96.980830150351.12618F-100000@apt4g.a3nyc.com>
Date: Sun, 30 Aug 1998 21:52:10 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: RE: Irqs
Content-Length: 1200
Lines: 40

Fellow DECstation hackers,

On 30-Aug-98 Thomas Riemer wrote:
> I noticed the line
> 
> dev->irq = 5 
> 
> in declance.c....
> 
> How does the linux stuff prevent clashes on interrupt numbers?  Is
> there a list somewhere that is used to prevent interrupt clashes?

Yes, indeed, there is. When it comes to interrupts, the situation becomes
uhmmm... interesting ;-). The DECstation engineers, in their infinite wisdom,
decided that the interrupts on the different DS models have to be completely
different.

I have been trying to hide those differences in the interrupt handler itself
(you may want to have look at int-handler.S and setup.c in arch/mips/dec and
ioasic.h in include/asm-mips/dec).

To make things easier to read (and to write code, of course) I have written
include/asm-mips/dec/interrupts.h. The code in declance.c should be:

[...]

#include <asm/dec/interrupts.h>

[...]

        dev->irq = ETHER; 

This works only for onboard devices. PMAD-AA option modules need
different treatment, but that would make declance.c unneccesary complicated
right now. I suggest we concentrate on bringing device drivers to work, and see
 later if it makes sense to merge them.

---
Regards,
Harald

From triemer@apt4g.a3nyc.com  Sun Aug 30 22:17:39 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id WAA29238; Sun, 30 Aug 1998 22:17:33 +0200 (MET DST)
Received-Date: Sun, 30 Aug 1998 22:17:33 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id QAA12864
	for <linux-mips@fnet.fr>; Sun, 30 Aug 1998 16:17:46 -0400
Date: Sun, 30 Aug 1998 16:17:46 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: RE: Irqs
In-Reply-To: <XFMail.980830215210.harald.koerfgen@netcologne.de>
Message-ID: <Pine.LNX.3.96.980830161630.12618H-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 473
Lines: 15



-----------------------------------------------------------------------
Given enough eyeballs all bugs seem shallow.

On Sun, 30 Aug 1998, Harald Koerfgen wrote:

> This works only for onboard devices. PMAD-AA option modules need
> different treatment, but that would make declance.c unneccesary complicated
> right now. I suggest we concentrate on bringing device drivers to work, and see
>  later if it makes sense to merge them.

What's a PMAD-AA option module?

-Tom

From triemer@apt4g.a3nyc.com  Sun Aug 30 22:40:09 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id WAA29357; Sun, 30 Aug 1998 22:40:08 +0200 (MET DST)
Received-Date: Sun, 30 Aug 1998 22:40:08 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id QAA12874
	for <linux-mips@fnet.fr>; Sun, 30 Aug 1998 16:40:21 -0400
Date: Sun, 30 Aug 1998 16:40:20 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: RE: Irqs
In-Reply-To: <Pine.LNX.3.96.980830161630.12618H-100000@apt4g.a3nyc.com>
Message-ID: <Pine.LNX.3.96.980830163542.12618I-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1218
Lines: 37


Here's my suggestion - just like you have dec_rtc_base defined 
in setup.c - how about adding dec_lance_base to setup.c 
We set it with default values there
We make sure the TurboChannel stuff kicks in before the declance
driver kicks in ....

That means that the lance driver would simply use dec_rtc_base
and dec_lance_base and would not have to know about what
kind of machine it was running on at all.

The TurboChannel stuff would be responsible for changing dec_lance_base
to the appropriate slot number address for the ethernet device.

-Tom

-----------------------------------------------------------------------
Given enough eyeballs all bugs seem shallow.

On Sun, 30 Aug 1998, Thomas Riemer wrote:

> 
> 
> -----------------------------------------------------------------------
> Given enough eyeballs all bugs seem shallow.
> 
> On Sun, 30 Aug 1998, Harald Koerfgen wrote:
> 
> > This works only for onboard devices. PMAD-AA option modules need
> > different treatment, but that would make declance.c unneccesary complicated
> > right now. I suggest we concentrate on bringing device drivers to work, and see
> >  later if it makes sense to merge them.
> 
> What's a PMAD-AA option module?
> 
> -Tom
> 

From R.vandenBerg@inter.NL.net  Sun Aug 30 23:43:56 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA29629; Sun, 30 Aug 1998 23:43:56 +0200 (MET DST)
Received-Date: Sun, 30 Aug 1998 23:43:56 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-51.Hoorn.NL.net [193.79.46.215] with ESMTP for <linux-mips@fnet.fr>
	id XAA23735 (8.8.8/3.28); Sun, 30 Aug 1998 23:43:54 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0zDFFj-0001YdC@dutch.mountain>
	for <linux-mips@fnet.fr>; Sun, 30 Aug 1998 23:43:15 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Sun, 30 Aug 1998 23:43:14 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: RE: Irqs
In-Reply-To: <XFMail.980830215210.harald.koerfgen@netcologne.de>
Message-ID: <Pine.LNX.3.95.980830234240.1921M-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 642
Lines: 19

Hello,

Harald, thanks for the little irq explanation.

On Sun, 30 Aug 1998, Harald Koerfgen wrote:

> This works only for onboard devices. PMAD-AA option modules need
> different treatment, but that would make declance.c unneccesary complicated
> right now. I suggest we concentrate on bringing device drivers to work, and see
>  later if it makes sense to merge them.

Indeed, I almost can't wait for 2.1.116. Hope that drivers/char is
identical to Linus' 2.1.16 because that would make life easier for a
framebuffer console. There's quite a difference between the console and
framebuffer code in 2.1.100 and in 2.1.116.

Regards,

Richard

From triemer@apt4g.a3nyc.com  Mon Aug 31 00:25:43 1998
Received: from apt4g.a3nyc.com (triemer@apt4g.a3nyc.com [166.84.184.179]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id AAA00643; Mon, 31 Aug 1998 00:25:41 +0200 (MET DST)
Received-Date: Mon, 31 Aug 1998 00:25:41 +0200 (MET DST)
Received: from localhost (triemer@localhost)
	by apt4g.a3nyc.com (8.8.7/8.8.7) with SMTP id SAA12956
	for <linux-mips@fnet.fr>; Sun, 30 Aug 1998 18:25:56 -0400
Date: Sun, 30 Aug 1998 18:25:51 -0400 (EDT)
From: Thomas Riemer <triemer@apt4g.a3nyc.com>
To: linux-mips@fnet.fr
Subject: RE: Irqs
In-Reply-To: <Pine.LNX.3.95.980830234240.1921M-100000@whale.dutch.mountain>
Message-ID: <Pine.LNX.3.96.980830182423.12618J-100000@apt4g.a3nyc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 890
Lines: 29

Patience...patience...patience.

-Tom

-----------------------------------------------------------------------
Given enough eyeballs all bugs seem shallow.

On Sun, 30 Aug 1998, Richard van den Berg wrote:

> Hello,
> 
> Harald, thanks for the little irq explanation.
> 
> On Sun, 30 Aug 1998, Harald Koerfgen wrote:
> 
> > This works only for onboard devices. PMAD-AA option modules need
> > different treatment, but that would make declance.c unneccesary complicated
> > right now. I suggest we concentrate on bringing device drivers to work, and see
> >  later if it makes sense to merge them.
> 
> Indeed, I almost can't wait for 2.1.116. Hope that drivers/char is
> identical to Linus' 2.1.16 because that would make life easier for a
> framebuffer console. There's quite a difference between the console and
> framebuffer code in 2.1.100 and in 2.1.116.
> 
> Regards,
> 
> Richard
> 

From ralf@uni-koblenz.de  Mon Aug 31 23:15:15 1998
Received: from informatik.uni-koblenz.de (mailhost.uni-koblenz.de [141.26.4.1]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id XAA22109; Mon, 31 Aug 1998 23:15:14 +0200 (MET DST)
Received-Date: Mon, 31 Aug 1998 23:15:14 +0200 (MET DST)
From: ralf@uni-koblenz.de
Received: from uni-koblenz.de (pmport-11.uni-koblenz.de [141.26.249.11])
	by informatik.uni-koblenz.de (8.8.8/8.8.8) with ESMTP id XAA12044
	for <linux-mips@fnet.fr>; Mon, 31 Aug 1998 23:15:10 +0200 (MEST)
Received: (from ralf@localhost)
	by uni-koblenz.de (8.8.7/8.8.7) id BAA21289;
	Mon, 31 Aug 1998 01:59:53 +0200
Message-ID: <19980831015953.A21285@uni-koblenz.de>
Date: Mon, 31 Aug 1998 01:59:53 +0200
To: Richard van den Berg <R.vandenBerg@inter.NL.net>, linux-mips@fnet.fr
Subject: Re: Irqs
References: <XFMail.980830215210.harald.koerfgen@netcologne.de> <Pine.LNX.3.95.980830234240.1921M-100000@whale.dutch.mountain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.91.1
In-Reply-To: <Pine.LNX.3.95.980830234240.1921M-100000@whale.dutch.mountain>; from Richard van den Berg on Sun, Aug 30, 1998 at 11:43:14PM +0200
Content-Length: 394
Lines: 10

On Sun, Aug 30, 1998 at 11:43:14PM +0200, Richard van den Berg wrote:

> Indeed, I almost can't wait for 2.1.116. Hope that drivers/char is
> identical to Linus' 2.1.16 because that would make life easier for a
> framebuffer console. There's quite a difference between the console and
> framebuffer code in 2.1.100 and in 2.1.116.

2.1.116 as in sgi-cvs is very similar to Linus' code.

  Ralf

From bjs@crc.com  Mon Aug 31 11:13:39 1998
Received: from hobbes.crc.com (hobbes.crc.com [192.251.235.201]) by guadalquivir.fnet.fr with SMTP (8.8.8/97.02.12/Guadalquivir); id LAA14571; Mon, 31 Aug 1998 11:13:37 +0200 (MET DST)
Received-Date: Mon, 31 Aug 1998 11:13:37 +0200 (MET DST)
Received: from mail.lsg.crc.com(really [192.251.232.221]) by hobbes.crc.com
	via sendmail with esmtp
	id <m0zDQ1k-000LAZC@hobbes.crc.com>
	for <linux-mips@fnet.fr>; Mon, 31 Aug 1998 05:13:32 -0400 (EDT)
	(Smail-3.2 1996-Jul-4 #4 built 1997-Mar-21)
Received: from delenn (delenn.lsgsys.crc.com [205.149.42.9]) by mail.lsg.crc.com (8.7.5/8.7.3) with SMTP id FAA27060; Mon, 31 Aug 1998 05:13:30 -0400
Message-Id: <199808310913.FAA27060@mail.lsg.crc.com>
From: "Bryan J. Smith" <bjs@crc.com>
To: "'Mitchell Blank Jr'" <mitch@execpc.com>, <linux-mips@fnet.fr>
Cc: <bjs@crc.com>
Subject: RE: [English]  I have an old DECstation 5000 and want to run Linux/MIPS ...
Date: Mon, 31 Aug 1998 05:13:28 -0400
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26
In-Reply-To: <19980828201549.21972@execpc.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Content-Length: 2188
Lines: 60

All --

Sorry, I have a 5000/240.  I have heard that NetBSD/OpenBSD is a better
solution since Linux/MIPS really only boots on those systems (and does
little else).

So, which is better NetBSD or OpenBSD?  Also, what is the history with all
the different BSD OSes (NetBSD, OpenBSD, FreeBSD, 386BSD, etc...)?  I am
assuming they are all based on the BSDLite 4.4 code, but how are they
different from each other?

Also, how do I find out which video controller I have and if it is
compatible with X?  If I cannot use this thing for X, I probably have little
use for it.

Any other comments on how I can load the OS exactly (it only has a DLT
drive)?  I have Ultrix currently running on the system and I believe I can
kill a partition I am no longer using (freeing up a couple hundred MB).

Any other comments?

Thanx in advance (for putting up with a newbie) ...

-- Bryan J. Smith
   Software Engineer
   Coleman Aerospace

P.S.  I called DEC to see if the 60MHz R4400 upgrade was still available for
the 240 (which makes it into a 260), and they referred me to a whole slew of
3rd party vendors who carry discontinued products.  No one had the upgrade.
Oh well, a 40MHz R3400 is still not bad.


-----Original Message-----
From: Mitchell Blank Jr [mailto:mitch@execpc.com]
Sent: Friday, August 28, 1998 9:16 PM
To: linux-mips@fnet.fr
Cc: bjs@crc.com
Subject: Re: [English] I have an old DECstation 5000 and want to run
Linux/MIPS ...


Bryan J. Smith wrote:
> [English]  I have an old DECstation 5000 and want to run Linux/MIPS ...

First, which 5000?  There's many many models of 5000, all the way from the
lowly Personal Decstation 5000/20 all the way to the mighty 5000/260.

As the other poster pointed out, the *BSDs are quite a bit farther along
in their DECstation support.  You can use either NetBSD (see
http://www.netbsd.org/Ports/pmax/) or OpenBSD (see
http://www.openbsd.org/pmax.html).  I've run OpenBSD on my PD5000/25 and
my 5000/125 with good results.  The only snag I've run accross is that some
of the more esoteric color framebuffer cards aren't supported.

Personally, I'll be happer with Linux on my boxen, but for the time being
I'd suggest grabbing a BSD.

-Mitch


From mitch@execpc.com  Mon Aug 31 12:40:14 1998
Received: from mailgw01.execpc.com (mailgw01.execpc.com [169.207.2.78]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id MAA14953; Mon, 31 Aug 1998 12:40:12 +0200 (MET DST)
Received-Date: Mon, 31 Aug 1998 12:40:12 +0200 (MET DST)
Received: from earth.execpc.com (earth.execpc.com [169.207.16.1])
	by mailgw01.execpc.com (8.9.0) id FAA05461;
	Mon, 31 Aug 1998 05:40:09 -0500 (CDT)
Received: (from mitch@localhost) by earth.execpc.com (8.9.0) id FAA00466; Mon, 31 Aug 1998 05:40:09 -0500 (CDT)
Message-ID: <19980831054009.05359@execpc.com>
Date: Mon, 31 Aug 1998 05:40:09 -0500
From: Mitchell Blank Jr <mitch@execpc.com>
To: "Bryan J. Smith" <bjs@crc.com>
Cc: linux-mips@fnet.fr
Subject: Re: [English]  I have an old DECstation 5000 and want to run Linux/MIPS ...
References: <19980828201549.21972@execpc.com> <199808310913.FAA27060@mail.lsg.crc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84e-execpc
In-Reply-To: <199808310913.FAA27060@mail.lsg.crc.com>; from Bryan J. Smith on Mon, Aug 31, 1998 at 05:13:28AM -0400
Content-Length: 4543
Lines: 96

Bryan J. Smith wrote:
> Sorry, I have a 5000/240.

nice..

> I have heard that NetBSD/OpenBSD is a better
> solution since Linux/MIPS really only boots on those systems (and does
> little else).

Yep.  From the looks of it, Harald and others are doing some fabulous work
on the decstation port, so maybe it won't be too long until we can all run
Linux on these machines.  Still, if you're looking for something now, a
BSD is the way to go.  (and the BSD's are quite good OSes in their own
right... it's just that many of us would prefer Linux :-)

[Note: this may be a bit off topic for linux-mips, but why not... I'm sure
there's some folks who are just setting up decstations now and will be
running BSD while testing linux kernels.  I hope to be in that boat soon
myself - I now have nothing critical on my decs, so once I find time (ha!)
to get a build environment going, I'll be doing the same thing... so some
cursory discussion of the various BSDs might be helpful for people starting
out with their DECstations, eh?]

> So, which is better NetBSD or OpenBSD?

Purely a matter of preference.  I think OpenBSD is a bit better on the
technical merits.  Others have the opposite opinion.

> Also, what is the history with all
> the different BSD OSes (NetBSD, OpenBSD, FreeBSD, 386BSD, etc...)?  I am
> assuming they are all based on the BSDLite 4.4 code, but how are they
> different from each other?

Yes, they all decend from bsd-lite2.  I might be a bit fuzzy on the details,
but here goes.  I think I'm at least approximately correct on this.

386BSD was basically a straight port of 4.4 to the 386 hardware with a small
amount of hardware support.  There was a series of accompnying articles in
Doctor Dobbs detailing the work as it progressed.  It's essentially "dead"
now, although the code lives on in...

FreeBSD - this project took the 386BSD code and refined it to the point its
at today.  Emphasis is on speed and stability on Intel platform.  Apparently
they're also working on a sparc port.  No decstation support, obviously.

NetBSD - this project started by combining the 386BSD work with all the other
stuff in 4.4BSD and maintaining it.  It runs on almost all the arcitectures
that were supported in BSD 4.[34] and several more have been added.  Emphasis
is on portability.

OpenBSD - several years ago some of there was a large fight in the NetBSD
ranks.  The exact issues involved and who said what seems to be a rather
contenious issue, so I won't go into that.  The end result was that some
NetBSD folks left to form a new project lead by Theo DeRaadt.  The emphasis
is on security.  Since it started from the NetBSD code base it still includes
support for a relatively large number of platforms.

Again, either NetBSD or OpenBSD will probably work fine.  Like I mentioned,
I'm currently running OpenBSD.  The only caveat about using OpenBSD over
NetBSD is that OpenBSD is very into crypto and security.  So things like
password crypting is substatially beefed up which makes logging in >slow<
on these old MIPS machines.  You can tune that with /etc/passwd.conf.  It
also has a bunch of security-audit cron jobs that run every night... if you're
near the machine (and its old loud SCSI drive) when these things tend to run
I'd advise just commenting them out... the sound of an old RZ drive running
all those md5sum's is quite maddening, especially when you're trying to
sleep :-)

> Also, how do I find out which video controller I have

At the prom console you should be able to get a dump of the hardware in the
box by issuing a "cnfg 3" command.  That is what I use on my PD5000/25 and
my 5000/125... I'm guessing the /240 will be the same.

> and if it is compatible with X?

They both support the common PMAG-AA, PMAG-BA, and PMAGB-BA cards.  They don't
support the PMAG-C, -D, -E, -F, -J, or -JA cards.  For these cards you're
currently stuck with Ultrix. :-(

> Any other comments on how I can load the OS exactly (it only has a DLT
> drive)?

The installations come with readme files.  Basically, you load the .tar.gz
files onto another machine and tftp boot an image.  All DECstations can
be network booted.  You can also dd an image onto a different SCSI disk and
boot from that if its more convinient.  Again, check the various readme
files for detailed instructions:

    ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-1.3.2/pmax/INSTALL
    ftp://ftp.openbsd.org/pub/OpenBSD/2.3/pmax/INSTALL.pmax

Enjoy your DECstation... they're really neat machines once you rid them of
their Ultrix affliction ;-)

-Mitch

From kristoff.bonne@belbone.net  Mon Aug 31 13:34:03 1998
Received: from mail.belbone.be (mail.belbone.be [195.13.1.3]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id NAA15195; Mon, 31 Aug 1998 13:33:58 +0200 (MET DST)
Received-Date: Mon, 31 Aug 1998 13:33:58 +0200 (MET DST)
Received: from jupiler.belbone.be (unknown-1-182.belbone.be [195.13.1.182])
	by mail.belbone.be (8.8.8/8.8.8) with ESMTP id NAA14947
	for <linux-mips@fnet.fr>; Mon, 31 Aug 1998 13:33:29 +0200 (MET DST)
Received: from jupiler.belbone.be (jupiler.belbone.be [192.168.1.182])
	by jupiler.belbone.be (8.8.5/8.8.5) with SMTP id NAA18740
	for <linux-mips@fnet.fr>; Mon, 31 Aug 1998 13:33:48 +0200 (MET DST)
Message-Id: <199808311133.NAA18740@jupiler.belbone.be>
Date: Mon, 31 Aug 1998 13:33:48 +0200 (MET DST)
From: Kristoff Bonne <kristoff.bonne@belbone.net>
Reply-To: Kristoff Bonne <kristoff.bonne@belbone.net>
Subject: RE: [English]  I have an old DECstation 5000 and want to run Linux/MIPS ...
To: linux-mips@fnet.fr
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: iEgqPPZltdpRXUal2ndMOg==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4m sparc 
Content-Length: 3109
Lines: 76

Greetings,

> From: "Bryan J. Smith" <bjs@crc.com>
> To: "'Mitchell Blank Jr'" <mitch@execpc.com>, <linux-mips@fnet.fr>
> Cc: <bjs@crc.com>
> Subject: RE: [English]  I have an old DECstation 5000 and want to run 
Linux/MIPS ...
> Date: Mon, 31 Aug 1998 05:13:28 -0400

> Sorry, I have a 5000/240.  I have heard that NetBSD/OpenBSD is a better
> solution since Linux/MIPS really only boots on those systems (and does
> little else).

> So, which is better NetBSD or OpenBSD?  Also, what is the history with all
> the different BSD OSes (NetBSD, OpenBSD, FreeBSD, 386BSD, etc...)?  I am
> assuming they are all based on the BSDLite 4.4 code, but how are they
> different from each other?

I don't know the history of the different BSD's, but -currently- there are three 
'shipping' *BSD variants: NetBSD, FreeBSD and OpenBSD.

NetBSD is the 'mother'BSD. It runs on more platforms then the others, and 
'stable' releases for new platforms seams to appear for NetBSD first.

The difference between NetBSD and OpenBSD seams to be more political and 
religious then technical.

IMHO, OpenBSD has two advantages over NetBSD:
- It's main FTP-site is located in Canada (and not in the US). Certain 
USA-export-controlled software (like kerberos and others) can only be found in 
OpenBSD and not in NetBSD.
- The latest stable-release for OpenBSD has a very user-friendly 'ports' tree; 
which makes it very easy to retrieve, patch, compile and install 
'standard-software'. (just type 'make')
I don't know if NetBSD has this too.


Both NetBSD and OpenBSD support the pmax.

Two things that can help you choose:
- What *BSD has the most-recent 'stable-'release?
- Support for certain particular hardware? (check out www.netbsd.org and 
www.openbsd.org)


- FreeBSD only supports i386-based architectures. (with a sparc and alpha-port 
coming up).
It differs from (especially) NetBSD that FreeBSD tries to implement a FAST 
PRODUCTION Operating-system designed for the 'international' market; while 
NetBSDs is more designed as 'a clean design unix'.

I haven't said that NetBSD isn't fast; nor that FreeBSD isn't well designed.
I'm just trying to point out a difference in 'design-goal' between them. It's a 
bit like the 'micro-kernel vs. monolytical kernel' discussion between Linus and 
A. Tanenbaum in the early linux-history.

Anycase, NetBSD probably would be ported to as-many platforms if it had other 
design-goals. FreeBSD probably wouldn't have such a great international support 
(like for other langauges other then english) for the same reason.

A brief history of FreeBSD can be found at 
'http://www.uk.freebsd.org/handbook/handbook3.html#3'.



> Also, how do I find out which video controller I have and if it is
> compatible with X?  If I cannot use this thing for X, I probably have little
> use for it.
Check out their web-sites: www.{net,free,open}bsd.org; or one of their mirrors.


Cheerio! Kr. Bonne.
--
Bonne Kristoff                              belgacom multimedia
(C=BE,A=RTT,P=RTTIPC,S=BONNE,G=Kristoff)    operations belbone
Kristoff.bonne@belbone.net                  fax: +32 2 2024123

From R.vandenBerg@inter.NL.net  Mon Aug 31 14:07:51 1998
Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id OAA15366; Mon, 31 Aug 1998 14:07:50 +0200 (MET DST)
Received-Date: Mon, 31 Aug 1998 14:07:50 +0200 (MET DST)
Received: from dutch.mountain by altrade.nijmegen.inter.nl.net
	via hn51-43.Hoorn.NL.net [193.79.46.207] with ESMTP for <linux-mips@fnet.fr>
	id OAA28129 (8.8.8/3.28); Mon, 31 Aug 1998 14:07:49 +0200 (MET DST)
Received: from whale.dutch.mountain(really [192.168.1.1]) by dutch.mountain
	via in.smtpd with smtp
	id <m0zDSb7-0001YdC@dutch.mountain>
	for <linux-mips@fnet.fr>; Mon, 31 Aug 1998 13:58:13 +0200 (MET DST)
	(Smail-3.2 1996-Jul-4 #2 built 1996-Nov-26)
Date: Mon, 31 Aug 1998 13:58:12 +0200 (MET DST)
From: Richard van den Berg <R.vandenBerg@inter.NL.net>
X-Sender: ravdberg@whale.dutch.mountain
To: linux-mips@fnet.fr
Subject: declance coding blues
Message-ID: <Pine.LNX.3.95.980831135630.521A-100000@whale.dutch.mountain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Length: 1541
Lines: 53

Hello,

I worked out Haralds proposal a bit further:

#include <asm/bootinfo.h>

...

        if (TURBOCHANNEL) {
                if (IOASIC && dev->name == 0x8010a1dc){
                        /* first device is on IOASIC, for some reason "eth0"
                         * doesn't work
                         */
                        esar_base = (char *)(system_base + 0x80002);
                        dev->base_addr = system_base + 0xc0000;
                } else {
                        /* check if there's a PMAD-AA present and calculate
                         * it's addresses
                         */
                }
        }

        /* dunno if that works on DS5100 */
        switch (mips_machtype) {
        case MACH_DS23100 || MACH_DS5100:
                esar_base = (char *)0xbd000001;
                dev->base_addr = 0xb8000000;
                break;
        }

        if(!esar_base){
                printk("Don't know where to find the LANCE!");
                exit;
        }

and works fine, the only thing that bothers me is the comparison of
dev->name. Like the comment says putting "eth0" instead of 0x8010a1dc
doesn't work. This is the story of dev: it is from the device structure
in include/linux/netdevice.h and the first initializition in it is

char *name;

In drivers/net/Space.c "eth0" is assigned to name and dev->name shows
up as eth0 it only is not equal to eth0, why?!
I got the value 0x8010a1dc from

printk("%x\n", dev->name);

Any light on this is very appriciated.

Regards,

Richard

From harald.koerfgen@netcologne.de  Mon Aug 31 18:03:11 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA19666; Mon, 31 Aug 1998 18:03:10 +0200 (MET DST)
Received-Date: Mon, 31 Aug 1998 18:03:10 +0200 (MET DST)
Received: from franz.no.dom (dial5-71.netcologne.de [194.8.195.71])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id SAA25576
	for <linux-mips@fnet.fr>; Mon, 31 Aug 1998 18:03:04 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980831180423.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.LNX.3.96.980830161630.12618H-100000@apt4g.a3nyc.com>
Date: Mon, 31 Aug 1998 18:04:23 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: RE: Irqs
Content-Length: 261
Lines: 15


On 30-Aug-98 Thomas Riemer wrote:

[...]
> What's a PMAD-AA option module?
> 
> -Tom

PMAD-AA: TURBOchannel Ethernet Module.

Also LANCE based with an 128KB SRAM buffer on board. Documentation is available
at http://decstation.unix-ag.org.
---
Regards,
Harald

From harald.koerfgen@netcologne.de  Mon Aug 31 18:03:13 1998
Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by guadalquivir.fnet.fr with ESMTP (8.8.8/97.02.12/Guadalquivir); id SAA19670; Mon, 31 Aug 1998 18:03:11 +0200 (MET DST)
Received-Date: Mon, 31 Aug 1998 18:03:11 +0200 (MET DST)
Received: from franz.no.dom (dial5-71.netcologne.de [194.8.195.71])
	by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id SAA25580
	for <linux-mips@fnet.fr>; Mon, 31 Aug 1998 18:03:08 +0200 (MET DST)
X-Ncc-Regid: de.netcologne
Message-ID: <XFMail.980831180428.harald.koerfgen@netcologne.de>
X-Mailer: XFMail 1.2 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.LNX.3.95.980830234240.1921M-100000@whale.dutch.mountain>
Date: Mon, 31 Aug 1998 18:04:28 +0200 (MEST)
Reply-To: "Harald Koerfgen" <harald.koerfgen@netcologne.de>
Organization: none
Sender: harry@franz.no.dom
From: Harald Koerfgen <harald.koerfgen@netcologne.de>
To: linux-mips@fnet.fr
Subject: RE: Irqs
Content-Length: 631
Lines: 19

Hi,

On 30-Aug-98 Richard van den Berg wrote:
[...]
> Indeed, I almost can't wait for 2.1.116. Hope that drivers/char is
> identical to Linus' 2.1.16 because that would make life easier for a
> framebuffer console. There's quite a difference between the console and
> framebuffer code in 2.1.100 and in 2.1.116.

Well, I don't know if drivers/char is identical to Linus' source tree, but
looking at the differences between 2.1.100 and 2.1.116 I assume it is.

FYI, Richard, there's even online documentation for the framebuffer console
stuff available at http://www.cs.kuleuven.ac.be/~geert/Console/

Have fun,
---
Regards,
Harald

