Date: Fri, 19 Mar 1999 13:35:01 -0700 From: "Justin T. Gibbs" <gibbs@plutotech.com> To: "Matthew N. Dodd" <winter@jurai.net> Cc: "Justin T. Gibbs" <gibbs@plutotech.com>, scsi@FreeBSD.org Subject: Re: CAM entry point for SCSI-to-Ethernet device. Message-ID: <199903192044.NAA14226@pluto.plutotech.com> In-Reply-To: Your message of "Fri, 19 Mar 1999 14:49:12 EST." <Pine.BSF.4.02.9903191446230.2158-100000@sasami.jurai.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903192044.NAA14226>