From owner-freebsd-scsi Mon Dec 11 12: 0:26 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 12:00:24 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from search.sparks.net (unknown [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id E79FF37B400 for ; Mon, 11 Dec 2000 12:00:23 -0800 (PST) Received: by search.sparks.net (Postfix, from userid 100) id 09CB8DC74; Mon, 11 Dec 2000 14:57:37 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id E5DEDD93D; Mon, 11 Dec 2000 14:57:37 -0500 (EST) Date: Mon, 11 Dec 2000 14:57:37 -0500 (EST) From: David Miller To: "Justin T. Gibbs" Cc: mjacob@feral.com, Reverend K Kanno , freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? In-Reply-To: <200012111950.eBBJols02740@aslan.scsiguy.com> 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 On Mon, 11 Dec 2000, Justin T. Gibbs wrote: > >> The lack of a peripheral driver doesn't have anything to do with > >> whether luns are supported or not. It also doesn't preclude the > >> system from talking to the array as a disk. David seemed to > >> imply that the Chapparal arrays didn't work *at all*. Actually that was Reverend K Kanno. > > > >Uh, if they report themselves as Processor type, they won't attach as disk: > > Only the control port on these devices is processor type. That makes sense, except that I have a da0 and a pass1 and pass2: pass1 at ahc0 bus 0 target 2 lun 1 pass1: Fixed Processor SCSI-2 device pass1: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged Queueing Enabled pass2 at ahc0 bus 0 target 2 lun 2 pass2: Fixed Processor SCSI-2 device pass2: 80.000MB/s transfers (40.000MHz, offset 127, 16bit) Why that second array would come up as a processor type is quite the mystery. --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message