Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site umn-cs.UUCP
Path: utzoo!watmath!clyde!burl!we13!ihnp4!stolaf!umn-cs!smith
From: smith@umn-cs.UUCP (Richard Smith)
Newsgroups: net.arch
Subject: Re: What other topics besides RISC? - (nf)
Message-ID: <444@umn-cs.UUCP>
Date: Wed, 25-Apr-84 16:00:27 EDT
Article-I.D.: umn-cs.444
Posted: Wed Apr 25 16:00:27 1984
Date-Received: Mon, 30-Apr-84 00:43:14 EDT
Sender: notes@umn-cs.UUCP
Organization: Computer Science Dept., U of Minn, Mpls, MN
Lines: 22

#R:houxk:-25300:umn-cs:13900009:000:801
umn-cs!smith    Apr 25 18:48:00 1984

[]
  Another interesting 'problem' might be those in trying to implement
co-processor systems.  It seems to me that 'old software' is a key
problem that newer architectures need to face: people are less and
less apt to discard old, working software when new hardware appears
[case in point: BBN designed the C30 processor to perfectly emulate
the crufty old Honeywell 316s that the Arpanet IMP software runs on
since 316s haven't been sold for about a decade.  The IMP/TIP software
was a pain to re-write: we did it once for the Pluribus and that
was enough].
  In the small computer world this may mean more machines with 6502's
grafted onto the same bus as 8088s and 68000s.  What kinds of problems
does this cause?
  Well, it's a thought.

Rick.
[smith.umn-cs@CSNet-Relay]
 [...ihnp4!umn-cs!smith]