Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!male!jethro!exodus!wonky.Eng.Sun.COM!mjacob
From: mjacob@wonky.Eng.Sun.COM (Matt Jacob)
Newsgroups: comp.periphs.scsi
Subject: Re: Auto Configuring SCSI
Message-ID: <10756@exodus.Eng.Sun.COM>
Date: 30 Mar 91 08:40:40 GMT
References: <2208@atlas.tegra.COM>
Sender: news@exodus.Eng.Sun.COM
Organization: Sun Microsystems, Mt. View, Ca.
Lines: 20


Using the INQUIRY command makes a lot of sense. The reason
why it is not done (at least, at Sun) can be broken down
into:

a) We support non-CCS compatible devices. That is, the INQUIRY
command was optional until the CCS pseudo standard (and now
mandatory in SCSI-2).

b) You can get a generic device type out of the INQUIRY
data, and you can also get Vendor ID and specific Product
data from the INQUIRY data as well. However, that may
present problems when you wish to bind one of several
slightly different drivers. If you structure your I/O
system such that each GENERIC class of SCSI device
gets a driver that can grok how to deal with variants,
yer a happy camper.


-matt