Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sunybcs!boulder!hao!oddjob!mimsy!chris
From: chris@mimsy.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Ultrix 2.0 boot -- a driver interface change?
Message-ID: <8223@mimsy.UUCP>
Date: Fri, 28-Aug-87 02:52:42 EDT
Article-I.D.: mimsy.8223
Posted: Fri Aug 28 02:52:42 1987
Date-Received: Sat, 29-Aug-87 16:22:53 EDT
References: <3244@ci-dandelion.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 20

In article <3244@ci-dandelion.UUCP> david@ci-dandelion.UUCP (David M.
Watson) writes:
>... From the first time we booted ULTRIX 2.0, the autoconf has reported
>that the vs's didn't interrupt, so I put a couple of printf's in the
>driver  probe routine and found that the autoconf appears to lie -- the
>probe is returning normally.

`did not interrupt' means not that probe() returned zero, but rather
that `cvec' was not altered.  cvec is a global variable in Ultrix
2.0, so code that says

	register int br, cvec;

	br = 0x15;
	cvec = <expr>;

will fail until the declarations for br and cvec are removed.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	seismo!mimsy!chris