From owner-freebsd-hackers Mon Jul 3 19:10:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hurlame.pdl.cs.cmu.edu (HURLAME.PDL.CS.CMU.EDU [128.2.189.78]) by hub.freebsd.org (Postfix) with SMTP id B4F9637BAAF; Mon, 3 Jul 2000 19:10:11 -0700 (PDT) (envelope-from magus+@hurlame.pdl.cs.cmu.edu) To: Mike Smith Cc: scsi@freebsd.org, hackers@freebsd.org Subject: Re: SCSI HBA device detection? References: <200007040146.SAA00380@mass.osd.bsdi.com> From: Nat Lanza Date: 03 Jul 2000 22:09:36 -0400 In-Reply-To: Mike Smith's message of "Mon, 03 Jul 2000 18:46:30 -0700" Message-ID: Lines: 26 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > If this is meant to be an exercise in writing a CAM HBA driver, then you > need to teach your disk-emulation code about the basic SCSI commands > (INQUIRY, TEST UNIT READY, etc). The SCSI infrastructure will use these > commands to automatically detect your drives. I already have code for handling the basic SCSI commands (I'm really porting a scsi-ramdisk driver from Linux rather than writing from scratch). The bit I'm curious about are which XPT actions I'll need to support other than XPT_PATH_INQ and XPT_SCSI_IO. > If you're writing a generic ramdisk, this is a really masochistic way to > go about doing it. 8) It's really a mix of an exercise in writing a CAM HBA driver and a first step towards a SCSI-over-IP driver. Also, a SCSI ramdisk can be handy for some of the benchmarking and tracing we do. --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message