From mackinla@cs.curtin.edu.au Tue Jun 22 17:45:24 1993
Return-Path: <mackinla@cs.curtin.edu.au>
Received: from gossip.pyramid.com by dutecai.et.tudelft.nl (4.1/1.34JP)
          id AA03701; Tue, 22 Jun 93 17:45:17 +0200
Received: from sword.eng.pyramid.com 
	by gossip.pyramid.com (5.61/OSx5.1a Pyramid-Internet-Gateway)
	id AA25250; Tue, 22 Jun 93 08:48:01 -0700
Received: from goss.pyramid.com
	by sword.eng.pyramid.com (5.61/Pyramid_Internal_Configuration)
	id AA03132; Tue, 22 Jun 93 08:45:03 -0700
Received: from marsh.cs.curtin.edu.au 
	by gossip.pyramid.com (5.61/OSx5.1a Pyramid-Internet-Gateway)
	id AA25234; Tue, 22 Jun 93 08:47:52 -0700
Received: from vincent.cs.curtin.edu.au by marsh.cs.curtin.edu.au with SMTP id AA11135
  (5.67a/IDA-1.4.4 for <riscy@pyramid.com>); Tue, 22 Jun 1993 23:43:35 +0800
Received: by vincent.cs.curtin.edu.au id AA14749
  (5.65c/IDA-1.4.4 for riscy@pyramid.com); Tue, 22 Jun 1993 23:43:24 +0800
From: Patrick Mackinlay <mackinla@cs.curtin.edu.au>
Message-Id: <199306221543.AA14749@vincent.cs.curtin.edu.au>
Subject: Re: Monitor code...
To: riscy@pyramid.com
Date: Tue, 22 Jun 1993 23:43:23 +0800 (WST)
X-Mailer: ELM [version 2.4 PL20]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1808      
Status: RO
X-Status: 


>*  Serial port
>
>How about using one of the 8 port chips. They come in a 68 lead PLCC.

Is this really necessary? This will probably get under Steve's (and
Jerry's) skin <grin>, but I think _one_ serial port on the motherboard
would be adequate. Remember, more can always be added with the ISA
bus... I mean seriously, the _CPU_ is only an 84 lead PLCC! <grin>

>*  Ethernet port
>
>I designed a card using the 7990, and I guess I could do it again.
>But, the 7990 was around in 1985, and there are better chips now.

Ok, so at least we have someone with enet experience on board. I
don't suppose you could tell me if there are any particular problems
with using an ISA card to do the networking? This could cut the
cost of the board a lot, while not necessarily reducing performance,
and make enet optional in the bargain. Are there any obvious
difficulties/problems doing it this way? Are PC enet cards particularly
obnoxious?

>*  Diagnostics / monitor code
>
>What fun. I bet we will have to fight over who does this one.

Are you serious!? I'd _love_ to do this part! The problem for me is
going to be getting ROMs burned, although I think I can twist a
few arms around here...

BTW: I suggest we do a few introductions here. I'm Pat Mackinlay,
a 3rd year CS student down here in Australia. I've been working on
a similar kind of a project (on and off) with Steve Ligett and
Jerry Callen (both on this list now, I think). I'm in this to see
a viable alternative to the current PC i386/486 boards, hopefully
running Linux or something like that, with an eventual goal of
seeing the GNU Hurd up and running...

Next? <grin>

Pat -- "There's only one thing left to do Mama, I got to ding a ding dang
	my dang a long ling long" (Jesus Built My Hotrod -- Ministry)
GCS d* -p+ c++ l++ m--- s+/- !g w- t- r

 
