1.\" $NetBSD: se.4,v 1.5 2002/02/13 08:17:45 ross Exp $ 2.\" 3.Dd February 3, 1997 4.Dt SE 4 5.Os 6.Sh NAME 7.Nm se 8.Nd Cabletron EA41x SCSI bus Ethernet interface driver 9.Sh SYNOPSIS 10.Cd "se* at scsibus? target ? lun ?" 11.Sh DESCRIPTION 12The 13.Nm 14driver supports the 15.Tn Cabletron 16EA41x 17.Tn SCSI 18bus 19.Tn Ethernet 20interface. 21.Pp 22This driver is a bit unusual. 23It must look like a network interface and it must also appear to be a 24.Tn SCSI 25device to the 26.Tn SCSI 27system. 28.Pp 29In addition, to facilitate 30.Tn SCSI 31commands issued by userland programs, there are 32.Fn open , 33.Fn close , 34and 35.Fn ioctl 36entry points. 37This allows a user program to, for example, 38display the EA41x statistic and download new code into the adaptor \- 39functions which can't be performed through the 40.Xr ifconfig 8 41interface. 42Normal operation does not require any special userland program. 43.Sh SEE ALSO 44.Xr scsi 4 , 45.Xr ifconfig 8 46.Sh AUTHORS 47Ian Dall \*[Lt]ian.dall@dsto.defence.gov.au\*[Gt] 48.Pp 49Acknowledgement: Thanks are due to Philip L. Budne \*[Lt]budd@cs.bu.edu\*[Gt] 50who reverse engineered the EA41x. 51In developing this code, Phil's userland daemon "etherd", 52was referred to extensively in lieu of accurate documentation for the device. 53.Sh BUGS 54The EA41x doesn't conform to the 55.Tn SCSI 56specification in much at all. 57About the only standard command supported is 58.Qq inquiry . 59Most commands are 6 bytes long, but the recv data is only 1 byte. 60Data must be received by periodically polling the device with the 61recv command. 62