From owner-freebsd-scsi Fri Sep 8 15:16: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 63A4937B423 for ; Fri, 8 Sep 2000 15:16:03 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA22082; Fri, 8 Sep 2000 16:15:50 -0600 (MDT) (envelope-from ken) Date: Fri, 8 Sep 2000 16:15:50 -0600 From: "Kenneth D. Merry" To: Matthew Jacob Cc: Wilko Bulte , freebsd-scsi@FreeBSD.ORG Subject: Re: suggestion for camcontrol Message-ID: <20000908161550.A21933@panzer.kdm.org> References: <20000908134520.A20744@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Fri, Sep 08, 2000 at 02:54:09PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Sep 08, 2000 at 14:54:09 -0700, Matthew Jacob wrote: > > The points about cleanliness are worthy- except the deal here is that the > interfaces have to be clean. The program 'camcontrol devlist' does not. Interfaces don't "have" to be clean, and neither does code that accesses those interfaces. Cleanliness is a choice made by the developer, and in this case I'm chosing the clean path rather than the quick-n-dirty path. The information in question is available through 'camcontrol negotiate -v', (once I commit the patch) so I don't think there's an urgent need for this, anyway. We've got time to do this the right way instead of throwing something in there that will likely stay there a long time. > You should be able to do XPT_PATH_INQ for paths 0 through 0xff to get at the > list of SIMs. Actually, you can't do that at the moment. To do a path inquiry, you need a device to do a path inquiry on. (i.e. path inquiries can only be done via the pass driver at the moment, they aren't supported through the xpt driver.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message