From owner-freebsd-scsi Thu Dec 10 14:21:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28315 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 14:21:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28308 for ; Thu, 10 Dec 1998 14:21:18 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id PAA02711; Thu, 10 Dec 1998 15:13:26 -0700 (MST) Date: Thu, 10 Dec 1998 15:13:26 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199812102213.PAA02711@narnia.plutotech.com> To: mjacob@feral.com cc: scsi@FreeBSD.ORG Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: >> >> I think that's a good idea, and in fact we've been planning on doing it for >> a while. The idea is to add a SCSI revision field to the quirk entry >> format, and then just not send serial number requests to anything < 2. > > You don't need a quirk entry. You know what revisions the device is when > you do the initial inquiry. As long as there are no SCSI 1 devices that support that feature, sure, but I don't really know if this is the case for every SCSI I (or SCSI III) quirk or feature. The idea was to have a generic SCSI I devive quirk entry that disabled all likely "unimplemented in SCSI I" features, allowing you to add overriding entries for more advanced SCSI I devices. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message