ne(4) [netbsd man page]
NE(4) BSD Kernel Interfaces Manual NE(4) NAME
ne -- NE2000 and compatible Ethernet cards device driver SYNOPSIS
ISA boards ne0 at isa? port 0x280 irq 9 ne1 at isa? port 0x300 irq 10 ne* at isapnp? MCA boards ne* at mca? slot ? PCI boards ne* at pci? dev ? function ? PCMCIA ne* at pcmcia? function ? acorn32 ne* at podulebus? amiga ne* at zbus0 # AriadneII, X-surf amigappc ne* at zbus0 # AriadneII, X-surf atari ne0 at mainbus0 # EtherNEC on Atari ROM cartridge slot evbarm ne0 at obio? addr 0x0e000200 intr 5 # on-board Asix AX88796 evbsh3 ne0 at mainbus? # Realtek RTL8019AS x68k ne* at intio0 addr 0xece300 intr 249 # Nereid Ethernet ne* at intio0 addr 0xeceb00 intr 248 # Nereid Ethernet neptune0 at intio0 addr 0xece000 intr 249 # Neptune-X neptune1 at intio0 addr 0xece400 intr 249 # Neptune-X at alt. addr. ne* at neptune? addr 0x300 DESCRIPTION
The ne device driver supports NE2000 and compatible (including NE1000) Ethernet cards. While the original NE2000 is designed for ISA bus, the compatible Realtek 8019 chip is widely used on various local busses and ne driver also supports such devices on various machines. MEDIA SELECTION
The Realtek 8019 (ISA, ISAPnP, some PCMCIA) and Realtek 8029 (PCI) NE2000-compatible Ethernet chips include support for software media selec- tion. If one of these chips is detected by the driver, the list of supported media will be displayed. For all other chips supported by the ne driver, media selection must be performed either via card jumper settings or by vendor-supplied con- figuration programs. DIAGNOSTICS
ne0: where did the card go? The driver found the card, but was unable to make the card respond to complete the configuration sequence. SEE ALSO
ifmedia(4), intro(4), isa(4), isapnp(4), mca(4), pci(4), pcmcia(4), ifconfig(8) BSD
April 3, 2010 BSD
Check Out this Related Man Page
SLHCI(4) BSD Kernel Interfaces Manual SLHCI(4) NAME
slhci -- Cypress/ScanLogic SL811HS USB Host Controller driver SYNOPSIS
PCMCIA (CF) controllers slhci* at pcmcia? function ? usb* at slhci? ISA controllers slhci* at isa? port ? irq ? usb* at slhci? x68k slhci0 at intio0 addr 0xece380 intr 251 slhci1 at intio0 addr 0xeceb80 intr 250 usb* at slhci? options SLHCI_TRY_LSVH DESCRIPTION
The slhci driver provides support for Cypress/ScanLogic SL811HS USB Host Controller. The driver supports control, bulk, and interrupt transfers but not isochronous (audio), which cannot be supported by this chip without per- fectly reliable 1ms interrupts. USB is polled and this chip requires the driver to initiate all transfers. The driver interrupts at least once every ms when a device is attached even if no data is transferred. The driver polls the chip when the transfer is expected to be com- pleted soon; with maximum use of the bus, the driver will not exit for most of each ms. Use of this driver can easily have a significant performance impact on any system. The chip is unreliable in some conditions, possibly due in part to difficulty meeting timing restrictions (this is likely to be worse on mul- tiprocessor systems). Unexpected device behavior may trigger some problems; power cycling externally powered devices may help resolve per- sistent problems. Detection of invalid chip state will usually cause the driver to halt, however is recommended that all data transfers be verified. Data corruption due to controller error will not be detected automatically. Unmounting and remounting a device is necessary to prevent use of cached data. The driver currently will start the next incoming packet before copying in the previous packet but will not copy the next outgoing packet before the previous packet is transferred. Reading or writing the chip is about the same speed as the USB bus, so this means that one outgo- ing transfer is half the speed of one incoming transfer and two outgoing transfers are needed to use the full available bandwidth. All revisions of the SL811HS have trouble with low speed devices attached to some (likely most) hubs. Low speed traffic via hub is not allowed by default, but can be enabled with options SLHCI_TRY_LSVH in the kernel config file or by setting the slhci_try_lsvh variable to non-zero using ddb(4) or gdb(1). Many USB keyboards have built in hubs and may be low speed devices. All USB mice I have seen are low speed devices, however a serial mouse should be usable on a hub with a full speed Serial-USB converter. A PS2-USB keyboard and mouse converter is likely to be a single low speed device. Some hardware using this chip does not provide the USB minimum 100mA current, which could potentially cause problems even with externally powered hubs. The system can allow excess power use in some other cases as well. Some signs of excess power draw may cause the driver to halt, however this may not stop the power draw. To be safe verify power use and availability before connecting any device. HARDWARE
Hardware supported by the slhci driver includes: Ratoc CFU1U Nereid Ethernet/USB/Memory board SEE ALSO
config(1), isa(4), pcmcia(4), usb(4) Cypress SL811HS datasheet, errata, and application note, http://www.cypress.com. HISTORY
The slhci driver appeared in NetBSD 2.0 and was rewritten in NetBSD 5.0. AUTHORS
Tetsuya Isaki <isaki@NetBSD.org> Matthew Orgass BSD
April 24, 2007 BSD