From owner-freebsd-scsi Thu Sep 30 13:29:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CCDD214E9B for ; Thu, 30 Sep 1999 13:29:30 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA13795; Thu, 30 Sep 1999 13:29:16 -0700 Date: Thu, 30 Sep 1999 13:29:08 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Gerard Roudier Cc: Chris Csanady , scsi@FreeBSD.ORG Subject: Re: sym driver 0.4.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > I'll try it for higher LUNs when I get a chance to look at this- I have a > > target I can configure for up to a fairly arbitrary number of luns, > > Thanks. > > > although I'd like to know how you can support more than 32 luns for > > parallel SCSi w/o going to SCCLUN semantics. > > SPI2 allows 6 bits for the LUN number. I'll go back and (re)check that spec then. How does this apply to revisions less than SCSI-3? > > > You should note that there is a setting now in cam_xpt.c such that only > > luns 0..7 will be searched unless there's a quirk for a device. There are > > far too many broken devices out there that just do strange things when you > > go into the higher luns. > > May-be, for covering all existing multi-lun devices, at least luns 0,..,15 > should be supported. I would think not for the generic case. I originally thought so, but I ran into too much breakage. It's simple enough to say "if <= SCSI2 and !HILUNS_QUIRKED, then maxlun == 8". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message