Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.periphs.scsi
Subject: Re: Multitasking Scripts on NCR 53c710
Message-ID: <20628@cbmvax.commodore.com>
Date: 15 Apr 91 05:32:45 GMT
References: <1991Apr12.130847.13990@sinix.UUCP> <1991Apr13.164615.1117@netcom.COM>
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 23

In article <1991Apr13.164615.1117@netcom.COM> feustel@netcom.COM (David Feustel) writes:
>I worked for NCR on OS/2 drivers for the 700 chip; it was not designed to work
>well with Intel architectures. I explained in excruciating detail to
>NCR what they needed to do to fix the design. The 710 was NCR's answer
>to my suggestions. They didn't really understand what I was trying to
>tell them.

	Care to elaborate?  I've read the programmers docs for the 700 and 710,
and they look like really hot chips.  Particularily the reduction in # of
interrupts to be serviced by the CPU (in a multitasking environment) would
seem to be a large win.  The 710's indexing registers mean you don't have to
essentially use a code-generator to queue up operations.

	Note: I work in a 680x0 multitasking environment, since from your
comments above that's likely to affect your comparison.

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com  BIX: rjesup  
Disclaimer: Nothing I say is anything other than my personal opinion.
Thus spake the Master Ninjei: "To program a million-line operating system
is easy, to change a man's temperament is more difficult."
(From "The Zen of Programming")  ;-)