cue(4) [centos man page]

CUE(4)                                                     BSD Kernel Interfaces Manual                                                     CUE(4)

NAME

     cue -- CATC USB-EL1210A USB Ethernet driver

SYNOPSIS

     To compile this driver into the kernel, place the following lines in your kernel configuration file:

           device uhci
           device ohci
           device usb
           device cue

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

           if_cue_load="YES"

DESCRIPTION

     The cue driver provides support for USB Ethernet adapters based on the Computer Access Technology Corporation's USB-EL1210A chipset.

     The USB-EL1210A supports a 512-bit multicast hash filter, single perfect filter entry for the station address and promiscuous mode.  Packets
     are received and transmitted over separate USB bulk transfer endpoints.

     The CATC chipset supports only 10Mbps half-duplex mode, hence there are no ifmedia(4) modes to select.

     For more information on configuring this device, see ifconfig(8).

HARDWARE

     The cue driver supports CATC USB-EL1210A based USB Ethernet adapters including:

     o   Belkin F5U011/F5U111
     o   CATC Netmate
     o   CATC Netmate II
     o   SmartBridges SmartLink

DIAGNOSTICS

     cue%d: watchdog timeout  A packet was queued for transmission and a transmit command was issued, however the device failed to acknowledge the
     transmission before a timeout expired.

     cue%d: no memory for rx list  The driver failed to allocate an mbuf for the receiver ring.

SEE ALSO

     arp(4), netintro(4), ng_ether(4), ifconfig(8)

HISTORY

     The cue device driver first appeared in FreeBSD 4.0.

AUTHORS

     The cue driver was written by Bill Paul <wpaul@ee.columbia.edu>.

BSD                                                                July 16, 2005                                                               BSD

KUE(4)							   BSD Kernel Interfaces Manual 						    KUE(4)

NAME

     kue -- Kawasaki LSI KL5KUSB101B USB Ethernet driver

SYNOPSIS

     To compile this driver into the kernel, place the following lines in your kernel configuration file:

	   device uhci
	   device ohci
	   device usb
	   device kue

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   if_kue_load="YES"

DESCRIPTION

     The kue driver provides support for USB Ethernet adapters based on the Kawasaki LSI KL5KLUSB101B chipset.

     The KL5KLUSB101B supports a 128-entry multicast filter, single perfect filter entry for the station address and promiscuous mode.	Packets
     are received and transmitted over separate USB bulk transfer endpoints.

     The Kawasaki chipset supports only 10Mbps half-duplex mode, hence there are no ifmedia(4) modes to select.

     For more information on configuring this device, see ifconfig(8).

HARDWARE

     The kue driver supports Kawasaki LSI KL5KLUSB101B based USB Ethernet adapters including:

     o	 3Com 3c19250
     o	 3Com 3c460 HomeConnect Ethernet USB Adapter
     o	 ADS Technologies USB-10BT
     o	 AOX USB101
     o	 ATen UC10T
     o	 Abocom URE 450
     o	 Corega USB-T
     o	 D-Link DSB-650C
     o	 Entrega NET-USB-E45, NET-HUB-3U1E
     o	 I/O Data USB ETT
     o	 Kawasaki DU-H3E
     o	 LinkSys USB10T
     o	 Netgear EA101
     o	 Peracom USB Ethernet Adapter
     o	 Psion Gold Port USB Ethernet adapter
     o	 SMC 2102USB, 2104USB

DIAGNOSTICS

     kue%d: watchdog timeout  A packet was queued for transmission and a transmit command was issued, however the device failed to acknowledge the
     transmission before a timeout expired.

     kue%d: no memory for rx list  The driver failed to allocate an mbuf for the receiver ring.

SEE ALSO

     arp(4), netintro(4), ng_ether(4), ifconfig(8)

HISTORY

     The kue device driver first appeared in FreeBSD 4.0.

AUTHORS

     The kue driver was written by Bill Paul <wpaul@ee.columbia.edu>.

BUGS

     The kue driver does not accumulate Ethernet collisions statistics because the Kawasaki firmware does not appear to maintain any internal sta-
     tistics.

BSD
								  October 7, 2006							       BSD