Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!necntc!ci-dandelion!david
From: david@ci-dandelion.UUCP (David M. Watson)
Newsgroups: comp.unix.wizards
Subject: Ultrix 2.0 boot -- a driver interface change?
Message-ID: <3244@ci-dandelion.UUCP>
Date: Thu, 27-Aug-87 16:27:35 EDT
Article-I.D.: ci-dande.3244
Posted: Thu Aug 27 16:27:35 1987
Date-Received: Sat, 29-Aug-87 12:08:03 EDT
Reply-To: david@ci-dandelion.UUCP (David M. Watson)
Organization: Cognition, Inc., Billerica, MA
Lines: 21


Before we converted our 11/750 to ULTRIX-32 v2.0, we ran two vs100's
without problems, although DEC did not, and still does not support that
device for ULTRIX.

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.

Therefore, I assume that the autoconf is looking for a different
sort of return value from the probe than the value which indicated
success in 1.2 (sizeof(struct vsdevice)).  Is this true?  What value
is autoconf looking for as an indication that the device actually did interrupt?

Or have I jumped to some wrong conclusions?

			-David Watson
			 Cognition, Inc. (617) 667-4800
			 900 Technology Park Drive
			 Billerica, MA  01821