1.\" $NetBSD: se.4,v 1.7 2017/07/04 06:35:46 wiz 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 47.An -nosplit 48.An Ian Dall Aq Mt ian.dall@dsto.defence.gov.au 49.Pp 50Acknowledgement: Thanks are due to 51.An Philip L. Budne Aq Mt budd@cs.bu.edu 52who reverse engineered the EA41x. 53In developing this code, Phil's userland daemon "etherd", 54was referred to extensively in lieu of accurate documentation for the device. 55.Sh BUGS 56The EA41x doesn't conform to the 57.Tn SCSI 58specification in much at all. 59About the only standard command supported is 60.Qq inquiry . 61Most commands are 6 bytes long, but the recv data is only 1 byte. 62Data must be received by periodically polling the device with the 63recv command. 64