From owner-freebsd-scsi Fri Mar 19 12:44:29 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 7BA2A15106 for ; Fri, 19 Mar 1999 12:44:24 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id NAA14226; Fri, 19 Mar 1999 13:44:03 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199903192044.NAA14226@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Matthew N. Dodd" Cc: "Justin T. Gibbs" , scsi@FreeBSD.org Subject: Re: CAM entry point for SCSI-to-Ethernet device. In-reply-to: Your message of "Fri, 19 Mar 1999 14:49:12 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Mar 1999 13:35:01 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Any opinions on filenames and such? se is probably best. If it turns out that we want to support other SCSI-ethernet protocols, we can break the driver out into common and device specific sub-modules. >How about the network code? Does that belong in a 'scsi' directory? I'm >not sure it makes much sense to separate it out but still. I would expect this to fall into the same category as for say a disk driver. These drivers are not split out into a buffer I/O portion and a SCSI portion. They are, in effect, buffer I/O to SCSI translators. The SE driver is a network to SCSI I/O translator. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message