Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!houxm!hogpc!houti!ariel!vax135!cornell!uw-beaver!tektronix!hplabs!hao!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP
Newsgroups: net.unix-wizards
Subject: Re: 785 and 4.2BSD
Message-ID: <8169@umcp-cs.UUCP>
Date: Sat, 25-Aug-84 06:50:06 EDT
Article-I.D.: umcp-cs.8169
Posted: Sat Aug 25 06:50:06 1984
Date-Received: Thu, 30-Aug-84 06:32:44 EDT
References: <56@decvax.UUCP>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 28

> From: aps@decvax.UUCP (Armando P. Stettner)

> >    From:      Doug Kingston <dpk@BRL-TGR.ARPA>
> >    
> >    4.2 WILL run on a 785 but only with the fixes for the 64K
> >    memory controller (the new memory controller).  Your local
> >    4.2BSD system hacker should be able to obtain these fixes.
> >    They are widely available.
> >    
> >    					-Doug-

> I do believe that 4.2 will come up on the 785 (or a 780 with
> the MS780-E) with out the fixes for the new memory controller.
> I think that certain error reporting "tasks" will not work
> or be started in the kernel and that the annoying message of
> unknown Nexus type will be printed at auto-configure time.
> Let me know if this is not the case.

If the 785 really is ``bug-compatible'' with the 780 (I like that
phrase!), then Armando Stettner has got it exactly.  The only thing
that happens if autoconf doesn't recognize the nexus type is that
it gets ignored.  For memory controllers, this just means you don't
get soft ECC reports.  (Hard errors cause SBI faults anyway, so
you *do* get notified about those, if kinda ``the hard way''.)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci (301) 454-7690
UUCP:	{seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland