Date: Thu, 18 Mar 1999 14:36:15 -0500 (EST) From: "Matthew N. Dodd" <winter@jurai.net> To: freebsd-scsi@FreeBSD.ORG Subject: CAM entry point for SCSI-to-Ethernet device. Message-ID: <Pine.BSF.4.02.9903181424310.2158-100000@sasami.jurai.net>
next in thread | raw e-mail | index | archive | help
On a whim I purchased an old SCSI to Ethernet box which happens to be supported by NetBSD by the 'se' device. pt0: <Cabletrn EA412/EA419 R 0100> Fixed Processor SCSI-0 device Now, as I understand it, the various CAM devices are attached by announcing them to the csa.callback set by the XXinit routine specified in the periph_driver struct that gets added to the magicical CAM config via DATA_SET(periphdriver_set, chdriver); Which is all fine and dandy. In porting the driver from NetBSD I'm curious to know where to hook up the driver to CAM. My thought was to create 'scsi_se.[ch]' and let the driver live there (or I can split up the network parts to live elsewhere) and in my csa.callback routine examine the device name as well as the device type (T_PROCESSOR) before attaching (so I know I have a valid SE device). Since I'd like the device to show up as 'seX' (woo!) this means that the 'pt' driver will have to not attach (or attach in the way that the 'pass' device does). Any ideas? I really don't want to intrude on the 'PT" device. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | 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?Pine.BSF.4.02.9903181424310.2158-100000>