diff --git a/share/man/man4/an.4 b/share/man/man4/an.4 index 8a63fb0f595b..91f44690b6e6 100644 --- a/share/man/man4/an.4 +++ b/share/man/man4/an.4 @@ -1,144 +1,145 @@ .\" Copyright (c) 1997, 1998, 1999 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt AN 4 .Os .Sh NAME .Nm an .Nd "Aironet Communications 4500/4800 wireless network adapter driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device an" .Cd "device wlan" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following lines in .Xr loader.conf 5 : .Bd -literal -offset indent if_an_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for Aironet Communications 4500 and 4800 wireless network adapters and variants, including the following: .Pp .Bl -bullet -compact -offset indent .It Aironet Communications 4500 and 4800 series .It Cisco Aironet 340 and 350 series .It Xircom Wireless Ethernet Adapter .El .Pp Support for these devices include the ISA, PCI and PCMCIA varieties. The Aironet 4500 series adapters operate at 1 and 2Mbps while the Aironet 4800 series and Cisco adapters can operate at 1, 2, 5.5 and 11Mbps. The ISA, PCI and PCMCIA devices are all based on the same core PCMCIA modules and all have the same programming interface, however unlike the Lucent WaveLAN/IEEE cards, the ISA and PCI cards appear to the host as normal ISA and PCI devices and do not require any PCCARD support. .Pp The PCMCIA Aironet cards require PC Card support, including the kernel .Xr pccard 4 driver. ISA cards can either be configured to use ISA Plug and Play or to use a particular I/O address and IRQ by properly setting the DIP switches on the board. (The default switch setting is for Plug and Play.) The .Nm driver has Plug and Play support and will work in either configuration, however when using a hard-wired I/O address and IRQ, the driver configuration and the NIC's switch settings must agree. PCI cards require no switch settings of any kind and will be automatically probed and attached. .Pp All host/device interaction with the Aironet cards is via programmed I/O. The Aironet devices support 802.11 and 802.3 frames, power management, BSS (infrastructure) and IBSS (ad-hoc) operation modes. The .Nm driver encapsulates all IP and ARP traffic as 802.11 frames, however it can receive either 802.11 or 802.3 frames. Transmit speed is selectable between 1Mbps, 2Mbps, 5.5Mbps, 11Mbps or "auto" (the NIC automatically chooses the best speed). .Pp By default, the .Nm driver configures the Aironet card for infrastructure operation. .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh DIAGNOSTICS .Bl -diag .It "an%d: init failed" The Aironet card failed to become ready after an initialization command was issued. .It "an%d: failed to allocate %d bytes on NIC" The driver was unable to allocate memory for transmit frames in the NIC's on-board RAM. .It "an%d: device timeout" The Aironet card failed to generate an interrupt to acknowledge a transmit command. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr wlan 4 , .Xr ancontrol 8 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 4.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ee.columbia.edu . diff --git a/share/man/man4/ath.4 b/share/man/man4/ath.4 index 10b2622f4dfc..75255754f7fd 100644 --- a/share/man/man4/ath.4 +++ b/share/man/man4/ath.4 @@ -1,342 +1,343 @@ .\"- .\" Copyright (c) 2002-2004 Sam Leffler, Errno Consulting .\" All rights reserved. .\"" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer, .\" without modification. .\" 2. Redistributions in binary form must reproduce at minimum a disclaimer .\" similar to the "NO WARRANTY" disclaimer below ("Disclaimer") and any .\" redistribution must be conditioned upon including a substantially .\" similar Disclaimer requirement for further binary redistribution. .\" 3. Neither the names of the above-listed copyright holders nor the names .\" of any contributors may be used to endorse or promote products derived .\" from this software without specific prior written permission. .\" .\" NO WARRANTY .\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS .\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT .\" LIMITED TO, THE IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTIBILITY .\" AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL .\" THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR SPECIAL, EXEMPLARY, .\" OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER .\" IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGES. .\" .\" $FreeBSD$ .\"/ .Dd July 16, 2005 .Dt ATH 4 .Os .Sh NAME .Nm ath .Nd "Atheros IEEE 802.11 wireless network driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device ath" .Cd "device ath_hal" .Cd "device ath_rate_onoe" .Cd "device wlan" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following lines in .Xr loader.conf 5 : .Bd -literal -offset indent if_ath_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for wireless network adapters based on the Atheros AR5210, AR5211, and AR5212 chips. Chip-specific support is provided by the Atheros Hardware Access Layer (HAL), that is packaged separately. .Pp Supported features include 802.11 and 802.3 frames, power management, BSS, IBSS, and host-based access point operation modes. All host/device interaction is via DMA. .Pp The .Nm driver encapsulates all IP and ARP traffic as 802.11 frames, however it can receive either 802.11 or 802.3 frames. Transmit speed and operating mode is selectable and depends on the specific chipset. AR5210-based devices support 802.11a operation with transmit speeds of 6 Mbps, 9 Mbps, 12 Mbps, 18 Mbps, 24 Mbps, 36 Mbps, 48 Mbps, and 54 Mbps. AR5211-based devices support 802.11a and 802.11b operation with transmit speeds as above for 802.11a operation and 1Mbps, 2Mbps, 5.5 Mbps and 11Mbps for 802.11b operation. AR5212-based devices support 802.11a, 802.11b, and 802.11g operation with transmit speeds appropriate to each. All chips also support an Atheros Turbo Mode (TM) that operates in the 5Ghz frequency range with 2x the transmit speeds. Some chips also support Turbo mode in the 2.4Ghz range with 802.11g. (These modes are, however, only interoperable with other Atheros-based devices.) The actual transmit speed used is dependent on signal quality and the .Dq "rate control" algorithm employed by the driver. All chips support WEP encryption. The AR5212 has hardware support for the AES-CCM, TKIP, and Michael cryptographic operations required for WPA. To enable encryption, use .Xr ifconfig 8 as shown below. .Pp By default, the .Nm driver configures the card for BSS operation (aka infrastructure mode). This mode requires the use of an access point (base station). .Pp The .Nm driver also supports the standard IBSS point-to-point mode where stations can communicate amongst themselves without the aid of an access point. .Pp The driver may also be configured to operate in hostap mode. In this mode a host may function as an access point (base station). Access points are different than operating in IBSS mode. They operate in BSS mode. They allow for easier roaming and bridge all Ethernet traffic such that machines connected via an access point appear to be on the local Ethernet segment. .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Pp Devices supported by the .Nm driver come in either Cardbus or mini-PCI packages. Wireless cards in Cardbus slots may be inserted and ejected on the fly. .Sh HARDWARE The following cards are among those supported by the .Nm driver: .Pp .Bl -column -compact "Samsung SWL-5200N" "AR5212" "Cardbus" "a/b/g" .It Em "Card Chip Bus Standard" .It "Aztech WL830PC AR5212 CardBus b/g" .It "Cisco AIR-CB21AG AR5115 Cardbus a/b/g" .It "Cisco AIR-PI21AG AR5115 PCI a/b/g" .It "D-Link DWL-A650 AR5210 CardBus a" .It "D-Link DWL-AB650 AR5211 CardBus a/b" .It "D-Link DWL-A520 AR5210 PCI a" .It "D-Link DWL-AG520 AR5212 PCI a/b/g" .It "D-Link DWL-AG650 AR5212 CardBus a/b/g" .It "D-Link DWL-G520B AR5212 PCI b/g" .It "D-Link DWL-G650B AR5212 CardBus b/g" .It "Elecom LD-WL54AG AR5212 Cardbus a/b/g" .It "Elecom LD-WL54 AR5211 Cardbus a" .It "Fujitsu E5454 AR5212 Cardbus a/b/g" .It "Fujitsu FMV-JW481 AR5212 Cardbus a/b/g" .It "Fujitsu E5454 AR5212 Cardbus a/b/g" .It "HP NC4000 AR5212 PCI a/b/g" .It "I/O Data WN-AB AR5212 CardBus a/b" .It "I/O Data WN-AG AR5212 CardBus a/b/g" .It "I/O Data WN-A54 AR5212 CardBus a" .It "Linksys WMP55AG AR5212 PCI a/b/g" .It "Linksys WPC51AB AR5211 CardBus a/b" .It "Linksys WPC55AG AR5212 CardBus a/b/g" .It "NEC PA-WL/54AG AR5212 CardBus a/b/g" .It "Netgear WAG311 AR5212 PCI a/b/g" .It "Netgear WAB501 AR5211 CardBus a/b" .It "Netgear WAG511 AR5212 CardBus a/b/g" .It "Netgear WG311T AR5212 PCI b/g" .It "Netgear WG511T AR5212 CardBus b/g" .It "Orinoco 8480 AR5212 CardBus a/b/g" .It "Orinoco 8470WD AR5212 CardBus a/b/g" .It "Proxim Skyline 4030 AR5210 CardBus a" .It "Proxim Skyline 4032 AR5210 PCI a" .It "Samsung SWL-5200N AR5212 CardBus a/b/g" .It "SMC SMC2536W-AG AR5212 CardBus a/b/g" .It "SMC SMC2735W AR5210 CardBus a" .It "Sony PCWA-C700 AR5212 Cardbus a/b" .It "Sony PCWA-C300S AR5212 Cardbus b/g" .It "Sony PCWA-C500 AR5210 Cardbus a" .It "3Com 3CRPAG175 AR5212 CardBus a/b/g" .El .Pp An up to date list can be found at .Pa http://customerproducts.atheros.com/customerproducts . .Sh EXAMPLES Join an existing BSS network (ie: connect to an access point): .Pp .Dl "ifconfig ath0 inet 192.168.0.20 netmask 0xffffff00" .Pp Join a specific BSS network with network name .Dq Li my_net : .Pp .Dl "ifconfig ath0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net" .Pp Join a specific BSS network with WEP encryption: .Bd -literal -offset indent ifconfig ath0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e wepmode on wepkey 0x8736639624 .Ed .Pp Join/create an 802.11b IBSS network with network name .Dq Li my_net : .Bd -literal -offset indent ifconfig ath0 inet 192.168.0.22 netmask 0xffffff00 ssid my_net \e mode 11b mediaopt adhoc .Ed .Pp Create an 802.11g host-based access point: .Bd -literal -offset indent ifconfig ath0 inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e mode 11g mediaopt hostap .Ed .Pp Create an 802.11a host-based access point with WEP enabled: .Bd -literal -offset indent ifconfig ath0 inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e wepmode on wepkey 0x1234567890 mode 11a mediaopt hostap .Ed .Pp Create a host-based wireless bridge to fxp0: .Bd -literal -offset indent Add BRIDGE to the kernel config. ifconfig ath0 inet up ssid my_ap media DS/11Mbps mediaopt hostap sysctl net.link.ether.bridge.enable=1 sysctl net.link.ether.bridge.config="ath0 fxp0" sysctl net.inet.ip.check_interface=0 .Ed .Pp This will give you the same functionality as an access point. .Sh DIAGNOSTICS .Bl -diag .It "ath%d: unable to attach hardware; HAL status %u" The Atheros Hardware Access Layer was unable to configure the hardware as requested. The status code is explained in the HAL include file .Pa sys/contrib/dev/ath/ah.h . .It "ath%d: failed to allocate descriptors: %d" The driver was unable to allocate contiguous memory for the transmit and receive descriptors. This usually indicates system memory is scarce and/or fragmented. .It "ath%d: unable to setup a data xmit queue!" The request to the HAL to set up the transmit queue for normal data frames failed. This should not happen. .It "ath%d: unable to setup a beacon xmit queue!" The request to the HAL to set up the transmit queue for 802.11 beacon frames frames failed. This should not happen. .It "ath%d: 802.11 address: %s" The MAC address programmed in the EEPROM is displayed. .It "ath%d: hardware error; resetting" An unrecoverable error in the hardware occurred. Errors of this sort include unrecoverable DMA errors. The driver will reset the hardware and continue. .It "ath%d: rx FIFO overrun; resetting" The receive FIFO in the hardware overflowed before the data could be transferred to the host. This typically occurs because the hardware ran short of receive descriptors and had no place to transfer received data. The driver will reset the hardware and continue. .It "ath%d: unable to reset hardware; hal status %u" The Atheros Hardware Access Layer was unable to reset the hardware as requested. The status code is explained in the HAL include file .Pa sys/contrib/dev/ath/ah.h . This should not happen. .It "ath%d: unable to start recv logic" The driver was unable to restart frame reception. This should not happen. .It "ath%d: device timeout" A frame dispatched to the hardware for transmission did not complete in time. The driver will reset the hardware and continue. This should not happen. .It "ath%d: bogus xmit rate 0x%x" An invalid transmit rate was specified for an outgoing frame. The frame is discarded. This should not happen. .It "ath%d: ath_chan_set: unable to reset channel %u (%u Mhz)" The Atheros Hardware Access Layer was unable to reset the hardware when switching channels during scanning. This should not happen. .It "ath%d: unable to allocate channel table" The driver was unable to allocate memory for the table used to hold the set of available channels. .It "ath%d: unable to collect channel list from hal" A problem occurred while querying the HAL to find the set of available channels for the device. This should not happen. .It "ath%d: failed to enable memory mapping" The driver was unable to enable memory-mapped I/O to the PCI device registers. This should not happen. .It "ath%d: failed to enable bus mastering" The driver was unable to enable the device as a PCI bus master for doing DMA. This should not happen. .It "ath%d: cannot map register space" The driver was unable to map the device registers into the host address space. This should not happen. .It "ath%d: could not map interrupt" The driver was unable to allocate an IRQ for the device interrupt. This should not happen. .It "ath%d: could not establish interrupt" The driver was unable to install the device interrupt handler. This should not happen. .El .Sh SEE ALSO .Xr an 4 , .Xr arp 4 , .Xr ath_hal 4 , .Xr card 4 , .Xr netintro 4 , .Xr pcic 4 , .Xr wi 4 , .Xr wlan 4 , .Xr ifconfig 8 , .Xr wicontrol 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 5.2 . .Sh CAVEATS Different regulatory domains have different default channels for adhoc mode. See .Xr ifconfig 8 for information on how to change the channel. See .Xr wicontrol 8 for information on different regulatory domains. Different regulatory domains may not be able to communicate with each other with 802.11a as different regulatory domains do not necessarily have overlapping channels. .Pp Revision A1 of the D-LINK DWL-G520 and DWL-G650 are based on an Intersil PrismGT chip and are not supported by this driver. .Sh BUGS Performance in lossy environments is suboptimal. The algorithm used to select the rate for transmitted packets is very simplistic. There is no software retransmit; only hardware retransmit is used. Contributors are encouraged to replace the existing rate control algorithm with a better one (hint: all the information needed is available to the driver). .Pp The driver does not fully enable power-save operation of the chip; consequently power use is suboptimal. .Pp The driver honors the regulatory domain programmed into the EEPROM of a device and does not support overriding this setting. This is done to insure compliance with local regulatory agencies when operating as an access point. Unfortunately this also means that devices purchased for use in one locale may not be usable in another. Changes are planned to remove this restriction when operating in station mode. diff --git a/share/man/man4/aue.4 b/share/man/man4/aue.4 index 9056d2de39ac..0acd181f2f3e 100644 --- a/share/man/man4/aue.4 +++ b/share/man/man4/aue.4 @@ -1,205 +1,206 @@ .\" Copyright (c) 1997, 1998, 1999 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt AUE 4 .Os .Sh NAME .Nm aue .Nd ADMtek AN986 Pegasus USB Ethernet driver .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device uhci" .Cd "device ohci" .Cd "device usb" .Cd "device miibus" .Cd "device aue" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_aue_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for USB Ethernet adapters based on the ADMtek AN986 Pegasus chipset. .Pp The LinkSys USB10T adapters that contain the AN986 Pegasus chipset will operate at 100Base-TX and full-duplex. .Pp The Pegasus contains a 10/100 Ethernet MAC with MII interface and is designed to work with both Ethernet and HomePNA transceivers. Although designed to interface with 100Mbps peripherals, the existing USB standard specifies a maximum transfer speed of 12Mbps. Users should therefore not expect to actually achieve 100Mbps speeds with these devices. .Pp The Pegasus supports a 64-bit multicast hash table, single perfect filter entry for the station address and promiscuous mode. Packets are received and transmitted over separate USB bulk transfer endpoints. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to the .Pa /etc/rc.conf file. .It 10baseT/UTP Set 10Mbps operation. The .Ar mediaopt option can also be used to enable .Ar full-duplex operation. Not specifying .Ar full duplex implies .Ar half-duplex mode. .It 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Ar mediaopt option can also be used to enable .Ar full-duplex operation. Not specifying .Ar full duplex implies .Ar half-duplex mode. .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It full-duplex Force full duplex operation. The interface will operate in half duplex mode if this media option is not specified. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE Adapters supported by the .Nm driver include: .Pp .Bl -bullet -compact .It Abocom UFE1000, DSB650TX_NA .It Accton USB320-EC, SpeedStream .It ADMtek AN986, AN8511 .It Billionton USB100, USB100LP, USB100EL, USBE100 .It Corega Ether FEther USB-T, FEther USB-TX, FEther USB-TXS .It D-Link DSB-650, DSB-650TX, DSB-650TX-PNA .It Elecom LD-USBL/TX .It Elsa Microlink USB2Ethernet .It HP hn210e .It I-O Data USB ETTX .It Kingston KNU101TX .It LinkSys USB10T adapters that contain the AN986 Pegasus chipset, USB10TA, USB10TX, USB100TX, USB100H1 .It MELCO LUA-TX, LUA2-TX .It Planex UE-200TX .It Sandberg USB to Network Link (model number 133-06) .It Siemens Speedstream .It SmartBridges smartNIC .It SMC 2202USB .It SOHOware NUB100 .El .Sh DIAGNOSTICS .Bl -diag .It "aue%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. .It "aue%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Rs .%T ADMtek AN986 data sheet .%O http://www.admtek.com.tw .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 4.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ee.columbia.edu . diff --git a/share/man/man4/awi.4 b/share/man/man4/awi.4 index 2769517b776d..4dc43949761b 100644 --- a/share/man/man4/awi.4 +++ b/share/man/man4/awi.4 @@ -1,156 +1,157 @@ .\" $NetBSD: awi.4,v 1.6 2000/03/22 11:24:33 onoe Exp $ .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt AWI 4 .Os .Sh NAME .Nm awi .Nd "AMD PCnetMobile IEEE 802.11 PCMCIA wireless network driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device awi" .Cd "device wlan" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_awi_load="YES" .Ed .Sh DESCRIPTION The .Nm driver supports various IEEE 802.11 wireless cards which run AMD PCnetMobile firmware based on AMD 79c930 controller with Intersil (formerly Harris) PRISM radio chipset. It provides access to 32kb of memory shared between the controller and the host. All host/device interaction is via this shared memory, which can be accessed either via PCMCIA memory space or I/O space. The .Nm driver encapsulates all IP and ARP traffic as 802.11 frames. .Pp The driver works both in infrastructure mode and in adhoc (independent BSS) mode. .Pp In infrastructure mode, it communicates with an Access Point which serves as a link-layer bridge between an Ethernet and the wireless network. An access point also provides roaming capability which allows wireless nodes to move between access points. .Pp In adhoc mode, it communicates peer to peer. Though it is more efficient to communicate between wireless nodes, the coverage is limited spatially due to lack of roaming capability. .Pp In addition to these two modes in the IEEE 802.11 specification, the .Nm driver also supports a variant of adhoc mode out of spec for DS radio cards, which makes it possible to communicate with adhoc mode of .Xr wi 4 driver. The NWID does not affect in this mode. .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE Cards supported by the .Nm driver include: .Pp .Bl -tag -width BayStack_650x -offset indent .It BayStack 650 1Mbps Frequency Hopping PCCARD adapter .It BayStack 660 2Mbps Direct Sequence PCCARD adapter .It Icom SL-200 2Mbps Direct Sequence PCCARD adapter .It Melco WLI-PCM 2Mbps Direct Sequence PCCARD adapter .It NEL SSMagic 2Mbps Direct Sequence PCCARD adapter .It Netwave AirSurfer Plus 1Mbps Frequency Hopping PCCARD adapter .It Netwave AirSurfer Pro 2Mbps Direct Sequence PCCARD adapter .It Nokia C020 WLAN 2Mbps Direct Sequence PCCARD adapter .It Farallon SkyLINE 2Mbps Direct Sequence PCCARD adapter .El .Pp The original Xircom Netwave AirSurfer is supported by the .Xr cnw 4 driver. .Sh MEDIA SELECTION The DS cards support .Em DS1 and .Em DS2 media types, while the FH cards support .Em FH1 media type. For each media type, .Em adhoc mediaopt can be used to indicate the driver to operate in adhoc mode. For DS radio cards, .Em adhoc , Ns Em flag0 mediaopt can be used for .Xr wi 4 compatible adhoc mode. In addition to these station modes, .Em hostap mediaopt can be used to create a host-based access point. .Sh DIAGNOSTICS .Bl -diag .It "awi0: awi_pccard_probe: bad banner:" The device failed to initialize its firmware. .It "awi0: failed to complete selftest (%s)" The device failed to complete its self test. In some circumstances, resetting device after power on fails. Re-inserting the card or down-then-up interface may be helpful. .It "awi0: transmit timeout" The device failed to generate an interrupt to acknowledge a transmitted packet. .It "awi0: failed to lock interrupt" The system was unable to obtain the lock to access shared memory. .It "awi0: command %d failed %x" The device failed to complete the request from the system. .El .Sh SEE ALSO .Xr arp 4 , .Xr card 4 , .Xr cnw 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr pccard 4 , .Xr wi 4 , .Xr wlan 4 , .Xr ifconfig 8 .Rs .%T Am79C930 PCnet Mobile Single-Chip Wireless LAN Media Access Controller .%O http://www.amd.com .Re .Sh HISTORY The .Nm device driver first appeared in .Nx 1.5 . .Sh AUTHORS .An -nosplit The initial version of the .Nm driver was written by .An Bill Sommerfeld Aq sommerfeld@netbsd.org . Then the .Nm driver module was completely rewritten to support cards with DS phy and to support adhoc mode by .An Atsushi Onoe Aq onoe@netbsd.org . diff --git a/share/man/man4/axe.4 b/share/man/man4/axe.4 index af79f120928d..20d301a58e2d 100644 --- a/share/man/man4/axe.4 +++ b/share/man/man4/axe.4 @@ -1,176 +1,177 @@ .\" Copyright (c) 1997, 1998, 1999, 2000-2003 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt AXE 4 .Os .Sh NAME .Nm axe .Nd "ASIX Electronics AX88172 USB Ethernet driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device ehci" .Cd "device uhci" .Cd "device ohci" .Cd "device usb" .Cd "device miibus" .Cd "device axe" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_axe_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for USB Ethernet adapters based on the ASIX Electronics AX88172 USB 2.0 chipset. .Pp The AX88172 is a USB 2.0 device which contains a 10/100 Ethernet MAC with MII interface and is designed to work with both Ethernet and HomePNA transceivers. The AX88172 will operate with both USB 1.x and USB 2.0 controllers, however performance with 1.x controllers will be limited since the USB 1.x standard specifies a maximum transfer speed of 12Mbps. Users with USB 1.x controllers should therefore not expect to actually achieve 100Mbps speeds with these devices. .Pp The AX88172 supports a 64-bit multicast hash table, single perfect filter entry for the station address, all-multicast mode and promiscuous mode. Packets are received and transmitted over separate USB bulk transfer endpoints. .Pp The .Nm driver supports the following media types: .Bl -tag -width ".Cm 10baseT/UTP" .It Cm autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to the .Pa /etc/rc.conf file. .It Cm 10baseT/UTP Set 10Mbps operation. The .Cm mediaopt option can also be used to enable .Cm full-duplex operation. Not specifying .Cm full-duplex implies .Cm half-duplex mode. .It Cm 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Cm mediaopt option can also be used to enable .Cm full-duplex operation. Not specifying .Cm full-duplex implies .Cm half-duplex mode. .El .Pp The .Nm driver supports the following media options: .Bl -tag -width ".Cm 10baseT/UTP" .It Cm full-duplex Force full duplex operation. The interface will operate in half duplex mode if this media option is not specified. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports ASIX Electronics AX88172 based USB Ethernet adapters including: .Pp .Bl -bullet -compact .It Buffalo (Melco Inc.) LUA-U2-KTX .It D-Link DUBE100 .It LinkSys USB200M .It Netgear FA120 .It Sitecom LN-029 .It System TALKS Inc.\& SGC-X2UL .El .Sh DIAGNOSTICS .Bl -diag .It "axe%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. .It "axe%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Rs .%T "ASIX AX88172 data sheet" .%O http://www.asix.com.tw .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 5.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@windriver.com . diff --git a/share/man/man4/bfe.4 b/share/man/man4/bfe.4 index eae0c06f4581..cb5621750dca 100644 --- a/share/man/man4/bfe.4 +++ b/share/man/man4/bfe.4 @@ -1,109 +1,110 @@ .\" .\" Copyright (c) 2003 Stuart Walsh .\" .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. .\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT, .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt BFE 4 .Os .Sh NAME .Nm bfe .Nd "Broadcom BCM4401 Ethernet Device Driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device bfe" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_bfe_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for Broadcom BCM4401 based Fast Ethernet adapters. .Pp The .Nm driver supports the following media types: .Bl -tag -width ".Cm 10baseT/UTP" .It Cm autoselect Enable autoselection of the media type and options. .It Cm 10baseT/UTP Set 10Mbps operation. .It Cm 100baseTX Set 100Mbps (Fast Ethernet) operation. .El .Pp The .Nm driver supports the following media options: .Bl -tag -width ".Cm full-duplex" .It Cm full-duplex Set full duplex operation. .El .Pp For further information on configuring this device, see .Xr ifconfig 8 . .Sh DIAGNOSTICS .Bl -diag .It "bfe%d: couldn't map memory" A fatal initialization error has occurred. .It "bfe%d: couldn't map interrupt" A fatal initialization error has occurred. .It "bfe%d: failed to allocate DMA resources" There are not enough mbufs available for allocation. .It "bfe%d: watchdog timeout -- resetting" The device has stopped responding to the network, or there is a problem with the network connection (cable). .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 5.1 . .Sh AUTHORS .An -nosplit The .Nm device driver was written by .An Stuart Walsh and .An Duncan Barclay . This manual page was written by .An Stuart Walsh . diff --git a/share/man/man4/bge.4 b/share/man/man4/bge.4 index b21923bf44f9..ad8c3320279e 100644 --- a/share/man/man4/bge.4 +++ b/share/man/man4/bge.4 @@ -1,239 +1,239 @@ .\" Copyright (c) 2001 Wind River Systems .\" Copyright (c) 1997, 1998, 1999, 2000, 2001 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt BGE 4 .Os .Sh NAME .Nm bge .Nd "Broadcom BCM570x/5714/5721/5750/5751/5789 PCI Gigabit Ethernet adapter driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device bge" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_bge_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for various NICs based on the Broadcom BCM570x, 5714, 5721, 5750, 5751 and 5789 families of Gigabit Ethernet controller chips. .Pp All of these NICs are capable of 10, 100 and 1000Mbps speeds over CAT5 copper cable, except for the SysKonnect SK-9D41 which supports only 1000Mbps over multimode fiber. The BCM570x builds upon the technology of the Alteon Tigon II. It has two R4000 CPU cores and is PCI v2.2 and PCI-X v1.0 compliant. It supports IP, TCP and UDP checksum offload for both receive and transmit, multiple RX and TX DMA rings for QoS applications, rules-based receive filtering, and VLAN tag stripping/insertion as well as a 256-bit multicast hash filter. Additional features may be provided via value-add firmware updates. The BCM570x supports TBI (ten bit interface) and GMII transceivers, which means it can be used with either copper or 1000baseX fiber applications. Note however the device only supports a single speed in TBI mode. .Pp Most BCM5700-based cards also use the Broadcom BCM5401 or BCM5411 10/100/1000 copper gigabit transceivers, which support autonegotiation of 10, 100 and 1000Mbps modes in full or half duplex. .Pp The BCM570x also supports jumbo frames, which can be configured via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the .Xr ifconfig 8 utility configures the adapter to receive and transmit jumbo frames. Using jumbo frames can greatly improve performance for certain tasks, such as file transfers and data streaming. .Pp The .Nm driver supports the following media types: .Bl -tag -width ".Cm 10baseT/UTP" .It Cm autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to .Xr rc.conf 5 . .It Cm 10baseT/UTP Set 10Mbps operation. The .Xr ifconfig 8 .Ic mediaopt option can also be used to select either .Cm full-duplex or .Cm half-duplex modes. .It Cm 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Xr ifconfig 8 .Ic mediaopt option can also be used to select either .Cm full-duplex or .Cm half-duplex modes. .It Cm 1000baseTX Set 1000baseTX operation over twisted pair. Only .Cm full-duplex mode is supported. .It Cm 1000baseSX Set 1000Mbps (Gigabit Ethernet) operation. Both .Cm full-duplex and .Cm half-duplex modes are supported. .El .Pp The .Nm driver supports the following media options: .Bl -tag -width ".Cm full-duplex" .It Cm full-duplex Force full duplex operation. .It Cm half-duplex Force half duplex operation. .El .Pp The .Nm driver also supports one special link option for 1000baseTX cards: .Bl -tag -width ".Cm link0" .It Cm link0 With 1000baseTX cards, establishing a link between two ports requires that one port be configured as a master and the other a slave. With autonegotiation, the master/slave settings will be chosen automatically. However when manually selecting the link state, it is necessary to force one side of the link to be a master and the other a slave. The .Nm driver configures the ports as slaves by default. Setting the .Cm link0 flag with .Xr ifconfig 8 will set a port as a master instead. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver provides support for various NICs based on the Broadcom BCM570x family of Gigabit Ethernet controller chips, including the following: .Pp .Bl -bullet -compact .It 3Com 3c996-T (10/100/1000baseTX) .It Dell PowerEdge 1750 integrated BCM5704C NIC (10/100/1000baseTX) .It Dell PowerEdge 2550 integrated BCM5700 NIC (10/100/1000baseTX) .It Dell PowerEdge 2650 integrated BCM5703 NIC (10/100/1000baseTX) .It IBM x235 server integrated BCM5703x NIC (10/100/1000baseTX) .It HP ProLiant NC7760 embedded Gigabit NIC (10/100/1000baseTX) .It HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseTX) .It HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseTX) .It Netgear GA302T (10/100/1000baseTX) .It SysKonnect SK-9D21 (10/100/1000baseTX) .It SysKonnect SK-9D41 (1000baseSX) .El .Sh DIAGNOSTICS .Bl -diag .It "bge%d: couldn't map memory" A fatal initialization error has occurred. .It "bge%d: couldn't map ports" A fatal initialization error has occurred. .It "bge%d: couldn't map interrupt" A fatal initialization error has occurred. .It "bge%d: no memory for softc struct!" The driver failed to allocate memory for per-device instance information during initialization. .It "bge%d: failed to enable memory mapping!" The driver failed to initialize PCI shared memory mapping. This might happen if the card is not in a bus-master slot. .It "bge%d: no memory for jumbo buffers!" The driver failed to allocate memory for jumbo frames during initialization. .It "bge%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr vlan 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 4.5 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@windriver.com . diff --git a/share/man/man4/cdce.4 b/share/man/man4/cdce.4 index 19fae4bb7e0e..d0da7211ee59 100644 --- a/share/man/man4/cdce.4 +++ b/share/man/man4/cdce.4 @@ -1,153 +1,153 @@ .\" Copyright (c) 2004 Daniel Hartmeier .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" .\" - Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" - Redistributions in binary form must reproduce the above .\" copyright notice, this list of conditions and the following .\" disclaimer in the documentation and/or other materials provided .\" with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS .\" "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT .\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS .\" FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE .\" COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, .\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; .\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER .\" CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN .\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" .\" $NetBSD: cdce.4,v 1.4 2004/12/08 18:35:56 peter Exp $ .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt CDCE 4 .Os .Sh NAME .Nm cdce .Nd "USB Communication Device Class Ethernet driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device uhci" .Cd "device ohci" .Cd "device usb" .Cd "device cdce" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_cdce_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for USB Host-to-Host (aka USB-to-USB) and USB-to-Ethernet bridges based on the USB Communication Device Class (CDC) and Ethernet subclass, including the following: .Pp .Bl -bullet -compact .It Prolific PL-2501 Host-to-Host Bridge Controller .It Sharp Zaurus PDA .It Terayon TJ-715 DOCSIS Cable Modem .El .Pp The USB bridge appears as a regular network interface on both sides, transporting Ethernet frames. .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Pp USB 1.x bridges support speeds of up to 12Mbps, and USB 2.0 speeds of up to 480Mbps. .Pp Packets are received and transmitted over separate USB bulk transfer endpoints. .Pp The .Nm driver does not support different media types or options. .Sh DIAGNOSTICS .Bl -diag .It "cdce%d: no union descriptor" The driver could not fetch an interface descriptor from the USB device. For a manually added USB vendor/product, the CDCE_NO_UNION flag can be tried to work around the missing descriptor. .It "cdce%d: no data interface" .It "cdce%d: could not read endpoint descriptor" .It "cdce%d: unexpected endpoint" .It "cdce%d: could not find data bulk in/out" For a manually added USB vendor/product, these errors indicate that the bridge is not compatible with the driver. .It "cdce%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. .It "cdce%d: no memory for rx list -- packet dropped!" Memory allocation through MGETHDR or MCLGET failed, the system is running low on mbufs. .It "cdce%d: abort/close rx/tx pipe failed" .It "cdce%d: rx/tx list init failed" .It "cdce%d: open rx/tx pipe failed" .It "cdce%d: usb error on rx/tx" .El .Sh SEE ALSO .Xr arp 4 , .Xr intro 4 , .Xr netintro 4 , .Xr usb 4 , .\" .Xr hostname.if 5 , .Xr ifconfig 8 .Rs .%T "Universal Serial Bus Class Definitions for Communication Devices" .%O http://www.usb.org/developers/devclass_docs/usbcdc11.pdf .Re .Rs .%T "Data sheet Prolific PL-2501 Host-to-Host Bridge/Network Controller" .%O http://tech.prolific.com.tw/visitor/fcabdl.asp?fid=20679530 .Re .Sh HISTORY The .Nm device driver first appeared in .Ox 3.6 , .Nx 3.0 and .Fx 6.0 . .Sh AUTHORS .An -nosplit The .Nm driver was written by .An Craig Boston Aq craig@tobuj.gank.org based on the .Xr aue 4 driver written by .An Bill Paul Aq wpaul@windriver.com and ported to .Ox by .An Daniel Hartmeier Aq dhartmei@openbsd.org . .Sh CAVEATS Many USB devices notoriously fail to report their class and interfaces correctly. Undetected products might work flawlessly when their vendor and product IDs are added to the driver manually. diff --git a/share/man/man4/cm.4 b/share/man/man4/cm.4 index a6506ac4b124..b6260988f3cb 100644 --- a/share/man/man4/cm.4 +++ b/share/man/man4/cm.4 @@ -1,175 +1,175 @@ .\" .\" Copyright (c) 2004 Tom Rhodes .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16,2005 .Dt CM 4 .Os .Sh NAME .Nm cm .Nd "SMC Arcnet Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in +your kernel configuration file: .Bd -ragged -offset indent .Cd "device isa" .Cd "device cm" .Ed .Pp Alternatively, to load the .Xr cm 4 driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_cm_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for the .Tn Arcnet .Tn ISA network adapters. .Pp This driver also has quirks preset in the .Xr device.hints 5 file for card detection. .Sh HARDWARE The .Nm driver supports the following card models: .Pp .Bl -bullet -compact .It SMC90c26 .It SMC90c56 .It SMC90c66 in '56 compatibility mode. .El .Sh IMPLEMENTATION NOTES When the .Va NOARP flag is set on the .Nm interface, it does not employ the address resolution protocol described in .Xr arp 4 to dynamically map between Internet and Ethernet addresses on the local network. Instead it uses the least significant 8 bits of the .Tn IP address as the hardware address like described in .Tn RFC 1051 and .Tn RFC 1201. .Pp With the .Dv IFF_LINK0 flag cleared .Tn IP/ARP/RARP encoding is done according to .Tn RFC 1201 that is, with Packet Header Definition Standard header and packet type 212 / 213. The .Tn MTU is normally 1500. The .Dv IFF_LINK0 flag is cleared by default. .Pp With the .Dv IFF_LINK0 flag set, .Tn IP and .Tn ARP encoding is done according to the deprecated .Tn RFC 1051 encoding, that is with simple header, packet type 240 / 241, and the .Tn MTU is 507. .Pp When switching between the two modes, use .Dl ifconfig interfacename down up to switch the .Tn MTU . .Sh DIAGNOSTICS The following driver specific error messages may be reported: .Bl -diag .It "reset: card reset, link addr = 0x%02x (cm%d)" The card is being reset and a new link address assigned. .It "srint: restarted rx on buf cm%d" The rx buffer has been emptied and will be reset. .El .Sh SEE ALSO .Xr netintro 4 , .Xr watchdog 4 , .Xr device.hints 5 , .Xr ifconfig 8 , .Xr watchdog 8 .Sh HISTORY The .Nm device was ported from .Nx by .An Max Khon Aq fjoe@FreeBSD.org and first appeared in .Fx 4.6 . This manual page first appeared in .Fx 5.3 . .Sh AUTHORS This manual page was written by .An Tom Rhodes Aq trhodes@FreeBSD.org . The .Sx IMPLEMENTATION NOTES section was submitted by .An Max Khon Aq fjoe@FreeBSD.org and originated from .Nx . .Sh BUGS The .Nm driver code could do with a bit of improvement, it would be nice if some one could come along and take care of this. .Pp The .Sx IMPLEMENTATION NOTES section is specific to all Arcnet devices (see .Pa sys/net/if_arcsubr.c ) and should be moved to a more generic location. diff --git a/share/man/man4/cue.4 b/share/man/man4/cue.4 index 77080880e3d5..7dbeac7ff82d 100644 --- a/share/man/man4/cue.4 +++ b/share/man/man4/cue.4 @@ -1,115 +1,115 @@ .\" Copyright (c) 1997, 1998, 1999, 2000 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt CUE 4 .Os .Sh NAME .Nm cue .Nd "CATC USB-EL1210A USB Ethernet driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device uhci" .Cd "device ohci" .Cd "device usb" .Cd "device cue" .Ed .Pp Alternatively, to load the .Xr cue 4 driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_cue_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for USB Ethernet adapters based on the Computer Access Technology Corporation's USB-EL1210A chipset. .Pp 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. .Pp The CATC chipset supports only 10Mbps half-duplex mode, hence there are no .Xr ifmedia 4 modes to select. .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports CATC USB-EL1210A based USB Ethernet adapters including: .Pp .Bl -bullet -compact .It Belkin F5U011/F5U111 .It CATC Netmate .It CATC Netmate II .It SmartBridges SmartLink .El .Sh DIAGNOSTICS .Bl -diag .It "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. .It "cue%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .El .Sh SEE ALSO .Xr arp 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 4.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ee.columbia.edu . diff --git a/share/man/man4/dc.4 b/share/man/man4/dc.4 index 142f368bde8e..486e30bf17b7 100644 --- a/share/man/man4/dc.4 +++ b/share/man/man4/dc.4 @@ -1,452 +1,452 @@ .\" Copyright (c) 1997, 1998, 1999 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt DC 4 .Os .Sh NAME .Nm dc .Nd "DEC/Intel 21143 and clone 10/100 Ethernet driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device dc" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_dc_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for several PCI Fast Ethernet adapters and embedded controllers based on the the DEC/Intel 21143 chipset and clones. .Pp All of supported chipsets have the same general register layout, DMA descriptor format and method of operation. All of the clone chips are based on the 21143 design with various modifications. The 21143 itself has support for 10baseT, BNC, AUI, MII and symbol media attachments, 10 and 100Mbps speeds in full or half duplex, built in NWAY autonegotiation and wake on LAN. The 21143 also offers several receive filter programming options including perfect filtering, inverse perfect filtering and hash table filtering. .Pp Some clone chips duplicate the 21143 fairly closely while others only maintain superficial similarities. Some support only MII media attachments. Others use different receiver filter programming mechanisms. At least one supports only chained DMA descriptors (most support both chained descriptors and contiguously allocated fixed size rings). Some chips (especially the PNIC) also have peculiar bugs. The .Nm driver does its best to provide generalized support for all of these chipsets in order to keep special case code to a minimum. .Pp These chips are used by many vendors which makes it difficult to provide a complete list of all supported cards. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width ".Cm 10baseT/UTP" .It Cm autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to the .Pa /etc/rc.conf file. .Pp Note: the built-in NWAY autonegotiation on the original PNIC 82c168 chip is horribly broken and is not supported by the .Nm driver at this time (see the .Sx BUGS section for details). The original 82c168 appears on very early revisions of the LinkSys LNE100TX and Matrox FastNIC. .It Cm 10baseT/UTP Set 10Mbps operation. The .Cm mediaopt option can also be used to enable .Cm full-duplex operation. Not specifying .Cm full-duplex implies .Cm half-duplex mode. .It Cm 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Cm mediaopt option can also be used to enable .Cm full-duplex operation. Not specifying .Cm full-duplex implies .Cm half-duplex mode. .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width ".Cm full-duplex" .It Cm full-duplex Force full duplex operation. The interface will operate in half duplex mode if this media option is not specified. .El .Pp Note that the 100baseTX media type may not be available on certain Intel 21143 adapters which support 10Mbps media attachments only. For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver provides support for the following chipsets: .Pp .Bl -bullet -compact .It DEC/Intel 21143 .It ADMtek AL981 Comet, AN985 Centaur, ADM9511 Centaur II and ADM9513 Centaur II .It ASIX Electronics AX88140A and AX88141 .It Conexant LANfinity RS7112 (miniPCI) .It Davicom DM9009, DM9100, DM9102 and DM9102A .It Lite-On 82c168 and 82c169 PNIC .It Lite-On/Macronix 82c115 PNIC II .It Macronix 98713, 98713A, 98715, 98715A, 98715AEC-C, 98725, 98727 and 98732 .It Xircom X3201 (cardbus only) .El .Pp The following NICs are known to work with the .Nm driver at this time: .Pp .Bl -bullet -compact .It 3Com OfficeConnect 10/100B (ADMtek AN985 Centaur-P) .It Abocom FE2500 .It Accton EN1217 (98715A) .It Accton EN2242 MiniPCI .It Adico AE310TX (98715A) .It Alfa Inc GFC2204 (ASIX AX88140A) .It Built in 10Mbps only Ethernet on Compaq Presario 7900 series desktops (21143, non-MII) .It Built in DE500-BA on DEC Alpha workstations (21143, non-MII) .It Built in Sun DMFE 10/100 Mbps Ethernet on Sun Netra X1 and Sun Fire V100 (DM9102A, MII) .It Built in Ethernet on LinkSys EtherFast 10/100 Instant GigaDrive (DM9102, MII) .It CNet Pro110B (ASIX AX88140A) .It CNet Pro120A (98715A or 98713A) and CNet Pro120B (98715) .It Compex RL100-TX (98713 or 98713A) .It D-Link DFE-570TX (21143, MII, quad port) .It Digital DE500-BA 10/100 (21143, non-MII) .It ELECOM Laneed LD-CBL/TXA (ADMtek AN985) .It Hawking CB102 CardBus .It IBM EtherJet Cardbus Adapter .It Intel PRO/100 Mobile Cardbus (versions that use the X3201 chipset) .It Jaton XpressNet (Davicom DM9102) .It Kingston KNE100TX (21143, MII) .It Kingston KNE110TX (PNIC 82c169) .It LinkSys LNE100TX (PNIC 82c168, 82c169) .It LinkSys LNE100TX v2.0 (PNIC II 82c115) .It LinkSys LNE100TX v4.0/4.1 (ADMtek AN985 Centaur-P) .It Matrox FastNIC 10/100 (PNIC 82c168, 82c169) .It Melco LGY-PCI-TXL .It Microsoft MN-120 10/100 CardBus (ADMTek Centaur-C) .It Microsoft MN-130 10/100 PCI (ADMTek Centaur-P) .It NDC SOHOware SFA110A (98713A) .It NDC SOHOware SFA110A Rev B4 (98715AEC-C) .It NetGear FA310-TX Rev.\& D1, D2 or D3 (PNIC 82c169) .It Netgear FA511 .It PlaneX FNW-3602-T (ADMtek AN985) .It SMC EZ Card 10/100 1233A-TX (ADMtek AN985) .It SVEC PN102-TX (98713) .It Xircom Cardbus Realport .It Xircom Cardbus Ethernet 10/100 .It Xircom Cardbus Ethernet II 10/100 .El .Sh NOTES On sparc64 the .Nm driver respects the .Va local-mac-address? system configuration variable for the built in Sun DMFE 10/100 Mbps Ethernet interfaces on Sun Netra X1 and Sun Fire V100. This system configuration variable can be set in the Open Firmware boot monitor using the .Ic setenv command or by .Xr eeprom 8 . If set to .Dq Li false (the default), the .Nm driver will use the system's default MAC address for both of the built in devices. If set to .Dq Li true , the unique MAC address of each interface is used rather than the system's default MAC address. .Sh DIAGNOSTICS .Bl -diag .It "dc%d: couldn't map ports/memory" A fatal initialization error has occurred. .It "dc%d: couldn't map interrupt" A fatal initialization error has occurred. .It "dc%d: watchdog timeout" A packet was queued for transmission and a transmit command was issued, but the device failed to acknowledge the transmission before a timeout expired. This can happen if the device is unable to deliver interrupts for some reason, of if there is a problem with the network connection (cable or network equipment) that results in a loss of link. .It "dc%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .It "dc%d: TX underrun -- increasing TX threshold" The device generated a transmit underrun error while attempting to DMA and transmit a packet. This happens if the host is not able to DMA the packet data into the NIC's FIFO fast enough. The driver will dynamically increase the transmit start threshold so that more data must be DMAed into the FIFO before the NIC will start transmitting it onto the wire. .It "dc%d: TX underrun -- using store and forward mode" The device continued to generate transmit underruns even after all possible transmit start threshold settings had been tried, so the driver programmed the chip for store and forward mode. In this mode, the NIC will not begin transmission until the entire packet has been transfered into its FIFO memory. .It "dc%d: chip is in D3 power state -- setting to D0" This message applies only to adapters which support power management. Some operating systems place the controller in low power mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. If you see this message at boot time and the driver fails to attach the device as a network interface, you will have to perform a second warm boot to have the device properly configured. .Pp Note that this condition only occurs when warm booting from another operating system. If you power down your system prior to booting .Fx , the card should be configured correctly. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr polling 4 , .Xr eeprom 8 , .Xr ifconfig 8 .Rs .%T ADMtek AL981, AL983 and AL985 data sheets .%O http://www.admtek.com.tw .Re .Rs .%T ASIX Electronics AX88140A and AX88141 data sheets .%O http://www.asix.com.tw .Re .Rs .%T Davicom DM9102 data sheet .%O http://www.davicom8.com .Re .Rs .%T Intel 21143 Hardware Reference Manual .%O http://developer.intel.com .Re .Rs .%T Macronix 98713/A, 98715/A and 98725 data sheets .%O http://www.macronix.com .Re .Rs .%T Macronix 98713/A and 98715/A app notes .%O http://www.macronix.com .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 4.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ee.columbia.edu . .Sh BUGS The Macronix application notes claim that in order to put the chips in normal operation, the driver must write a certain magic number into the CSR16 register. The numbers are documented in the app notes, but the exact meaning of the bits is not. .Pp The 98713A seems to have a problem with 10Mbps full duplex mode. The transmitter works but the receiver tends to produce many unexplained errors leading to very poor overall performance. The 98715A does not exhibit this problem. All other modes on the 98713A seem to work correctly. .Pp The original 82c168 PNIC chip has built in NWAY support which is used on certain early LinkSys LNE100TX and Matrox FastNIC cards, however it is horribly broken and difficult to use reliably. Consequently, autonegotiation is not currently supported for this chipset: the driver defaults the NIC to 10baseT half duplex, and it is up to the operator to manually select a different mode if necessary. (Later cards use an external MII transceiver to implement NWAY autonegotiation and work correctly.) .Pp The .Nm driver programs 82c168 and 82c169 PNIC chips to use the store and forward setting for the transmit start threshold by default. This is to work around problems with some NIC/PCI bus combinations where the PNIC can transmit corrupt frames when operating at 100Mbps, probably due to PCI DMA burst transfer errors. .Pp The 82c168 and 82c169 PNIC chips also have a receiver bug that sometimes manifests during periods of heavy receive and transmit activity, where the chip will improperly DMA received frames to the host. The chips appear to upload several kilobytes of garbage data along with the received frame data, dirtying several RX buffers instead of just the expected one. The .Nm driver detects this condition and will salvage the frame; however, it incurs a serious performance penalty in the process. .Pp The PNIC chips also sometimes generate a transmit underrun error when the driver attempts to download the receiver filter setup frame, which can result in the receive filter being incorrectly programmed. The .Nm driver will watch for this condition and requeue the setup frame until it is transfered successfully. .Pp The ADMtek AL981 chip (and possibly the AN985 as well) has been observed to sometimes wedge on transmit: this appears to happen when the driver queues a sequence of frames which cause it to wrap from the end of the transmit descriptor ring back to the beginning. The .Nm driver attempts to avoid this condition by not queuing any frames past the end of the transmit ring during a single invocation of the .Fn dc_start routine. This workaround has a negligible impact on transmit performance. diff --git a/share/man/man4/de.4 b/share/man/man4/de.4 index 052d43d9d0b3..d070ea0910e2 100644 --- a/share/man/man4/de.4 +++ b/share/man/man4/de.4 @@ -1,155 +1,155 @@ .\" .\" Copyright (c) 1997 David E. O'Brien .\" .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. .\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT, .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt DE 4 .Os .Sh NAME .Nm de .Nd "DEC DC21x4x Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration -file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device de" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_de_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for the Ethernet adapters based on the Digital Equipment DC21x4x based self-contained Ethernet and Fast Ethernet chips. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width xxxxxxxxxxxxxxx .It autoselect Enable autoselection of the media type and options .It 10baseT/UTP Set 10Mbps operation on the 10baseT port .It 10base2/BNC Set 10Mbps operation on the BNC port .It 10base5/AUI Set 10Mbps operation on the AUI port .It 100baseTX Set 100Mbps (Fast Ethernet) operation .It 100baseFX Set 100Mbps operation .It 100baseT4 Set 100Mbps operation (4-pair cat-3 cable) .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxx .It full-duplex Set full duplex operation .El .Pp Note that the media types available depend on the particular card in use. Some cards are explicitly programmed to a particular media type by a setup utility and are not changeable. .Pp Use the .Xr ifconfig 8 command an in particular the .Fl m flag to list the supported media types for your particular card. .Pp The old .Dq ifconfig linkN method of configuration is not supported. .Sh HARDWARE Adapters supported by the .Nm driver include: .Pp .Bl -bullet -compact .It Adaptec ANA-6944/TX .It Cogent EM100FX and EM440TX .It Corega FastEther PCI-TX .It D-Link DFE-500TX .It DEC DE435, DE425, DEC DE450, and DEC DE500 .It ELECOM LD-PCI2T, LD-PCITS .It I-O DATA LA2/T-PCI .It SMC Etherpower 8432, 9332 and 9334 .It ZNYX ZX3xx .El .Sh DIAGNOSTICS .Bl -diag .It "de%d: waking device from sleep/snooze mode" The 21041 and 21140A chips support suspending the operation of the card. .It "de%d: error: desired IRQ of %d does not match device's actual IRQ of %d" The device probe detected that the board is configured for a different interrupt than the one specified in the kernel configuration file. .It "de%d: not configured; limit of %d reached or exceeded" There is a limit of 32 .Nm devices allowed in a single machine. .It "de%d: not configured; 21040 pass 2.0 required (%d.%d found)" .It "de%d: not configured; 21140 pass 1.1 required (%d.%d found)" Certain revisions of the chipset are not supported by this driver. .El .Sh CAVEATS Since the 21040 is available on both EISA and PCI boards, one must be careful in how one defines the 21040 in the kernel config file. .Sh SEE ALSO .Xr arp 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh AUTHORS .An -nosplit The .Nm device driver was written by .An Matt Thomas . This manual page was written by .An David E. O'Brien . diff --git a/share/man/man4/ed.4 b/share/man/man4/ed.4 index df455e1b1298..5e91ae649e4c 100644 --- a/share/man/man4/ed.4 +++ b/share/man/man4/ed.4 @@ -1,395 +1,395 @@ .\" .\" Copyright (c) 1994, David Greenman .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by David Greenman. .\" 4. The name of the author may not be used to endorse or promote products .\" derived from this software without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt ED 4 .Os .Sh NAME .Nm ed .Nd "NE-2000 and WD-80x3 Ethernet driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device ed" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_ed_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for 8 and 16bit Ethernet cards that are based on the National Semiconductor DS8390 and similar NICs manufactured by other companies. .Pp The .Nm driver uses a unique multi-buffering mechanism to achieve high transmit performance. When using 16bit ISA cards, as high as 97% of the theoretical maximum performance of the IEEE 802.3 CSMA Ethernet is possible. .Pp In addition to the standard port and IRQ specifications, the .Nm driver also supports a number of .Cd flags which can force 8/16bit mode, enable/disable multi-buffering, and select the default interface type (AUI/BNC, and for cards with twisted pair, AUI/10BaseT). .Pp The .Cd flags are a bit field, and are summarized as follows: .Bl -tag -width indent .It Li 0x01 Disable transceiver. On those cards which support it, this flag causes the transceiver to be disabled and the AUI connection to be used by default. .It Li 0x02 Force 8bit mode. This flag forces the card to 8bit mode regardless of how the card identifies itself. This may be needed for some clones which incorrectly identify themselves as 16bit, even though they only have an 8bit interface. This flag takes precedence over force 16bit mode. .It Li 0x04 Force 16bit mode. This flag forces the card to 16bit mode regardless of how the card identifies itself. This may be needed for some clones which incorrectly identify themselves as 8bit, even though they have a 16bit ISA interface. .It Li 0x08 Disable transmitter multi-buffering. This flag disables the use of multiple transmit buffers and may be necessary in rare cases where packets are sent out faster than a machine on the other end can handle (as evidenced by severe packet lossage). Some .No ( non- Ns Fx :-)) machines have terrible Ethernet performance and simply cannot cope with 1100K+ data rates. Use of this flag also provides one more packet worth of receiver buffering, and on 8bit cards, this may help reduce receiver lossage. .El .Pp When using a 3c503 card, the AUI connection may be selected by specifying the .Cm link2 option to .Xr ifconfig 8 (BNC is the default). .Sh HARDWARE The .Nm driver supports the following Ethernet NICs: .Pp .Bl -bullet -compact .It 3Com 3c503 Etherlink II .Pq Cd "options ED_3C503" .It AR-P500 Ethernet .It Accton EN1644 (old model), EN1646 (old model), EN2203 (old model) (110pin) (flags 0xd00000) .It Accton EN2212/EN2216/UE2216 .It Allied Telesis CentreCOM LA100-PCM_V2 .It Allied Telesis LA-98 (flags 0x000000) (PC-98) .It Allied Telesis SIC-98, SIC-98NOTE (110pin), SIU-98 (flags 0x600000) (PC-98) .It Allied Telesis SIU-98-D (flags 0x610000) (PC-98) .It AmbiCom 10BaseT card .It Bay Networks NETGEAR FA410TXC Fast Ethernet .It Belkin F5D5020 PC Card Fast Ethernet .It Billionton LM5LT-10B Ethernet/Modem PC Card .It Bromax iPort 10/100 Ethernet PC Card .It Bromax iPort 10 Ethernet PC Card .It Buffalo LPC2-CLT, LPC3-CLT, LPC3-CLX, LPC4-TX PC Card .It CNet BC40 adapter .It Compex Net-A adapter .It Contec C-NET(98), RT-1007(98), C-NET(9N) (110pin) (flags 0xa00000) (PC-98) .It Contec C-NET(98)E-A, C-NET(98)L-A, C-NET(98)P (flags 0x300000) (PC-98) .It Corega Ether98-T (flags 0x000000) (PC-98) .It Corega Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD .It CyQ've ELA-010 .It DEC EtherWorks DE305 .It Danpex EN-6200P2 .It D-Link DE-298, DE-298P (flags 0x500000) (PC-98) .It D-Link DE-650/660 .It D-Link IC-CARD/IC-CARD+ Ethernet .It ELECOM LD-98P (flags 0x500000) (PC-98) .It ELECOM LD-BDN, LD-NW801G (flags 0x200000) (PC-98) .It ELECOM Laneed LD-CDL/TX, LD-CDF, LD-CDS, LD-10/100CD, LD-CDWA (DP83902A) .It HP PC Lan+ 27247B and 27252A .Pq Cd "options ED_HPP" .It IBM Creditcard Ethernet I/II .It ICM AD-ET2-T, DT-ET-25, DT-ET-T5, IF-2766ET, IF-2771ET, NB-ET-T (110pin) (flags 0x500000) (PC-98) .It I-O DATA LA/T-98, LA/T-98SB, LA2/T-98, ET/T-98 (flags 0x900000) (PC-98) .It I-O DATA ET2/T-PCI .It I-O DATA PCLATE .It Kansai KLA-98C/T (flags 0x900000) (PC-98) .It Kingston KNE-PC2, CIO10T, KNE-PCM/x Ethernet .It Linksys EC2T/PCMPC100/PCM100, PCMLM56 .It Linksys EtherFast 10/100 PC Card, Combo PCMCIA Ethernet Card (PCMPC100 V2) .It Logitec LAN-98T (flags 0xb00000) (PC-98) .It MACNICA Ethernet ME1 for JEIDA .It MACNICA ME98 (flags 0x900000) (PC-98) .It MACNICA NE2098 (flags 0x400000) (PC-98) .It MELCO EGY-98 (flags 0x300000) (PC-98) .It MELCO LGH-98, LGY-98, LGY-98-N (110pin), IND-SP, IND-SS (flags 0x400000) (PC-98) .It MELCO LGY-PCI-TR .It MELCO LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX .It NDC Ethernet Instant-Link .It NEC PC-9801-77, PC-9801-78 (flags 0x910000) (PC-98) .It NEC PC-9801-107, PC-9801-108 (flags 0x800000) (PC-98) .It National Semiconductor InfoMover NE4100 .It NetGear FA-410TX .It NetVin 5000 .It Network Everywhere Ethernet 10BaseT PC Card .It Networld 98X3 (flags 0xd00000) (PC-98) .It Networld EC-98X, EP-98X (flags 0xd10000) (PC-98) .It New Media LANSurfer 10+56 Ethernet/Modem .It New Media LANSurfer .It Novell NE1000/NE2000/NE2100 .It PLANEX ENW-8300-T .It PLANEX EN-2298-C (flags 0x200000) (PC-98) .It PLANEX EN-2298P-T, EN-2298-T (flags 0x500000) (PC-98) .It PLANEX FNW-3600-T .It Psion 10/100 LANGLOBAL Combine iT .It RealTek 8029 .It Relia Combo-L/M-56k PC Card .It SMC Elite 16 WD8013 .It SMC Elite Ultra .It SMC EtherEZ98 (flags 0x000000) (PC-98) .It SMC WD8003E/WD8003EBT/WD8003S/WD8003SBT/WD8003W/WD8013EBT/WD8013W and clones .It SMC EZCard PC Card, 8040-TX, 8041-TX .It Socket LP-E, ES-1000 Ethernet/Serial, LP-E CF, LP-FE CF .It Surecom EtherPerfect EP-427 .It Surecom NE-34 .It TDK 3000/3400/5670 Fast Etherenet/Modem .It TDK LAK-CD031, Grey Cell GCS2000 Ethernet Card .It TDK DFL5610WS Ethernet/Modem PC Card .It Telecom Device SuperSocket RE450T .It VIA VT86C926 .It Winbond W89C940 .El .Pp C-Bus, ISA, PCI and PC Card devices are supported. .Sh DIAGNOSTICS .Bl -diag .It "ed%d: kernel configured irq %d doesn't match board configured irq %d." The IRQ number that was specified in the kernel config file (and then compiled into the kernel) differs from the IRQ that has been set on the interface card. .It "ed%d: failed to clear shared memory at %x - check configuration." When the card was probed at system boot time, the .Nm driver found that it could not clear the card's shared memory. This is most commonly caused by a BIOS extension ROM being configured in the same address space as the Ethernet card's shared memory. Either find the offending card and change its BIOS ROM to be at an address that does not conflict, or change the .Cd iomem option in the kernel config file so that the card's shared memory is mapped at a non-conflicting address. .It "ed%d: Invalid irq configuration (%d) must be 2-5 for 3c503." The IRQ number that was specified in the kernel config file is not valid for the 3Com 3c503 card. The 3c503 can only be assigned to IRQs 2 through 5. .It "ed%d: Cannot find start of RAM." .It "ed%d: Cannot find any RAM, start : %d, x = %d." The probe of a Gateway card was unsuccessful in configuring the card's packet memory. This likely indicates that the card was improperly recognized as a Gateway or that the card is defective. .It "ed: packets buffered, but transmitter idle." Indicates a logic problem in the driver. Should never happen. .It "ed%d: device timeout" Indicates that an expected transmitter interrupt did not occur. Usually caused by an interrupt conflict with another card on the ISA bus. This condition could also be caused if the kernel is configured for a different IRQ channel than the one the card is actually using. If that is the case, you will have to either reconfigure the card using a DOS utility or set the jumpers on the card appropriately. .It "ed%d: NIC memory corrupt - invalid packet length %d." Indicates that a packet was received with a packet length that was either larger than the maximum size or smaller than the minimum size allowed by the IEEE 802.3 standard. Usually caused by a conflict with another card on the ISA bus, but in some cases may also indicate faulty cabling. .It "ed%d: remote transmit DMA failed to complete." This indicates that a programmed I/O transfer to an NE1000 or NE2000 style card has failed to properly complete. Usually caused by the ISA bus speed being set too fast. .El .Sh CAVEATS Early revision DS8390 chips have problems. They lock up whenever the receive ring-buffer overflows. They occasionally switch the byte order of the length field in the packet ring header (several different causes of this related to an off-by-one byte alignment) - resulting in .Qq Li "NIC memory corrupt - invalid packet length" messages. The card is reset whenever these problems occur, but otherwise there is no problem with recovering from these conditions. .Pp The NIC memory access to 3Com and Novell cards is much slower than it is on WD/SMC cards; it is less than 1MB/second on 8bit boards and less than 2MB/second on the 16bit cards. This can lead to ring-buffer overruns resulting in dropped packets during heavy network traffic. .Pp 16bit Compex cards identify themselves as being 8bit. While these cards will work in 8bit mode, much higher performance can be achieved by specifying .Cd "flags 0x04" (force 16bit mode) in your kernel config file. In addition, you should also specify .Cd "iosiz 16384" to take advantage of the extra 8K of shared memory that 16bit mode provides. .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 1.0 . .Sh AUTHORS The .Nm device driver and this manual page were written by .An David Greenman . .Sh BUGS The .Nm driver is a bit too aggressive about resetting the card whenever any bad packets are received. As a result, it may throw out some good packets which have been received but not yet transferred from the card to main memory. .Pp The .Nm PC Card attachment supports the D-Link DMF650TX Lan/Modem card's ethernet port only at this time. diff --git a/share/man/man4/em.4 b/share/man/man4/em.4 index 5d114915bdf9..547a24a2cd82 100644 --- a/share/man/man4/em.4 +++ b/share/man/man4/em.4 @@ -1,221 +1,221 @@ .\" Copyright (c) 2001-2003, Intel Corporation .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions are met: .\" .\" 1. Redistributions of source code must retain the above copyright notice, .\" this list of conditions and the following disclaimer. .\" .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" 3. Neither the name of the Intel Corporation nor the names of its .\" contributors may be used to endorse or promote products derived from .\" this software without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" .\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE .\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" .\" * Other names and brands may be claimed as the property of others. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt EM 4 .Os .Sh NAME .Nm em .Nd "Intel(R) PRO/1000 Gigabit Ethernet adapter driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration -file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device em" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_em_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for PCI Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547 and 82573 Ethernet controller chips. The driver supports Transmit/Receive checksum offload and Jumbo Frames only on 82540, 82543, 82544 and 82546-based adapters. For further hardware information, see the .Pa README included with the driver. .Pp For questions related to hardware requirements, refer to the documentation supplied with your Intel PRO/1000 adapter. All hardware requirements listed apply to use with .Fx . .Pp Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the .Xr ifconfig 8 utility configures the adapter to receive and transmit Jumbo Frames. The maximum MTU size for Jumbo Frames is 16114. .Pp This driver version supports VLANs. For information on enabling VLANs, see the .Pa README . The .Nm driver supports the following media types: .Bl -tag -width ".Cm 10baseT/UTP" .It Cm autoselect Enables auto-negotiation for speed and duplex. .It Cm 10baseT/UTP Sets 10Mbps operation. Use the .Cm mediaopt option to select .Cm full-duplex mode. .It Cm 100baseTX Sets 100Mbps operation. Use the .Cm mediaopt option to select .Cm full-duplex mode. .It Cm 1000baseSX Sets 1000Mbps operation. Only .Cm full-duplex mode is supported at this speed. .It Cm 1000baseTX Sets 1000Mbps operation. Only .Cm full-duplex mode is supported at this speed. .El .Pp The .Nm driver supports the following media options: .Bl -tag -width ".Cm full-duplex" .It Cm full-duplex Forces full-duplex operation .It Cm half-duplex Forces half-duplex operation. .El .Pp Only use .Cm mediaopt to set the driver to .Cm full-duplex . If .Cm mediaopt is not specified, the driver defaults to .Cm half-duplex . .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547 and 82573 controller chips: .Pp .Bl -bullet -compact .It Intel PRO/1000 CT Network Connection (82547) .It Intel PRO/1000 F Server Adapter (82543) .It Intel PRO/1000 Gigabit Server Adapter (82542) .It Intel PRO/1000 GT Desktop Adapter (82541PI) .It Intel PRO/1000 MF Dual Port Server Adapter (82546) .It Intel PRO/1000 MF Server Adapter (82545) .It Intel PRO/1000 MF Server Adapter (LX) (82545) .It Intel PRO/1000 MT Desktop Adapter (82540) .It Intel PRO/1000 MT Desktop Adapter (82541) .It Intel PRO/1000 MT Dual Port Server Adapter (82546) .It Intel PRO/1000 MT Quad Port Server Adapter (82546EB) .It Intel PRO/1000 MT Server Adapter (82545) .It Intel PRO/1000 T Desktop Adapter (82544) .It Intel PRO/1000 T Server Adapter (82543) .It Intel PRO/1000 XF Server Adapter (82544) .It Intel PRO/1000 XT Server Adapter (82544) .El .Sh DIAGNOSTICS .Bl -diag .It "em%d: Unable to allocate bus resource: memory" A fatal initialization error has occurred. .It "em%d: Unable to allocate bus resource: interrupt" A fatal initialization error has occurred. .It "em%d: watchdog timeout -- resetting" The device has stopped responding to the network, or there is a problem with the network connection (cable). .El .Sh SUPPORT For additional information regarding building and installation, see the .Pa README included with the driver. For general information and support, go to the Intel support website at: .Pa http://support.intel.com . .Pp If an issue is identified with the released source code on the supported kernel with a supported adapter, email the specific information related to the issue to .Aq freebsdnic@mailbox.intel.com . .Sh SEE ALSO .Xr arp 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr polling 4 , .Xr vlan 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 4.4 . .Sh AUTHORS The .Nm driver was written by .An Intel Corporation Aq freebsdnic@mailbox.intel.com . .Sh BUGS Hardware-assisted VLAN processing is disabled by default. You can enable it on an .Nm interface using .Xr ifconfig 8 . diff --git a/share/man/man4/en.4 b/share/man/man4/en.4 index f5dedd620db1..ef26f3a1ddc2 100644 --- a/share/man/man4/en.4 +++ b/share/man/man4/en.4 @@ -1,80 +1,80 @@ .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt EN 4 .Os .Sh NAME .Nm en .Nd "device driver for Midway-based ATM interfaces" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device en" .Cd "device atm" .Cd "device utopia" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following liness in .Xr loader.conf 5 : .Bd -literal -offset indent if_en_load="YES" .Ed .Sh DESCRIPTION The .Nm device driver supports Midway-based ATM interfaces including the Efficient Networks, Inc.\& ENI-155 and Adaptec ANA-59x0. Midway is an AAL5 SAR (Segmentation and Reassembly) chip. .Pp For configuring the card for IP see .Xr natmip 4 . .Pp The following sysctls are recognized by the driver additionally to those handled by .Xr utopia 4 : .Bl -tag -width indent .It Va hw.atm.enX.istats Contains an array of .Vt uint32_t with internal driver statistics. .It Va hw.atm.enX.debug This is a bit map of debugging options. This variable is only available when the driver is compiled with debugging support. .El .Pp The driver supports the media options .Cm sdh , .Cm noscramb and .Cm unassigned (see .Xr utopia 4 ) . .Sh DIAGNOSTICS .Bd -literal en0 rev 0 int a irq 5 on pci0:16 en0: ATM midway v0, board IDs 6.0, Utopia (pipelined), 512KB on-board RAM en0: maximum DMA burst length = 64 bytes en0: 7 32KB receive buffers, 8 32KB transmit buffers allocated .Ed .Sh CAVEATS The driver extensively uses DMA on PCI. The first generation PCI chipsets do not work or exhibit poor performance. .Sh SEE ALSO .Xr natm 4 , .Xr natmip 4 , .Xr utopia 4 , .Xr ifconfig 8 , .Xr route 8 .Sh AUTHORS .An Chuck Cranor of Washington University implemented .Nm driver in 1996 for .Nx . diff --git a/share/man/man4/fwe.4 b/share/man/man4/fwe.4 index df7b71391b81..6469ef4d2b7a 100644 --- a/share/man/man4/fwe.4 +++ b/share/man/man4/fwe.4 @@ -1,98 +1,98 @@ .\" Copyright (c) 2002 Hidetoshi Shimokawa .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED .\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE .\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, .\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES .\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR .\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, .\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN .\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .\" .Dd July 16, 2005 .Dt FWE 4 .Os .Sh NAME .Nm fwe .Nd "Ethernet emulation driver for FireWire" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device firewire" .Cd "device fwe" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_fwe_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides non-standard Ethernet emulation over FireWire (IEEE 1394). .Pp .Xr firewire 4 and .Xr fwohci 4 must be configured in the kernel as well. .Pp This driver exploits asynchronous stream over IEEE 1394 to carry Ethernet frames. The stream channel can be specified by the .Va hw.firewire.fwe.stream_ch .Xr sysctl 8 . .Pp This driver supports .Xr polling 4 as well if it is compiled with the .Dv DEVICE_POLLING option. .Sh SEE ALSO .Xr arp 4 , .Xr firewire 4 , .Xr fwip 4 , .Xr fwohci 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr polling 4 , .Xr ifconfig 8 , .Xr kldload 8 , .Xr sysctl 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 5.0 . .Sh AUTHORS The .Nm driver and this manual page were written by .An Hidetoshi Shimokawa . .Sh BUGS This driver emulates Ethernet in a very adhoc way and it does not reserve a stream channel using an isochronous manager. Note that this driver uses a protocol which is very different from RFC 2734 (IPv4 over IEEE 1394). diff --git a/share/man/man4/fwip.4 b/share/man/man4/fwip.4 index 2e6391ec779d..0c32fe9a0c36 100644 --- a/share/man/man4/fwip.4 +++ b/share/man/man4/fwip.4 @@ -1,97 +1,97 @@ .\" Copyright (c) 2004 Doug Rabson .\" Copyright (c) 2002 Hidetoshi Shimokawa .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED .\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE .\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, .\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES .\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR .\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, .\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN .\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt FWIP 4 .Os .Sh NAME .Nm fwip .Nd "IP over FireWire driver" .Sh SYNOPSIS To compile support for the .Xr fwip 4 -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device firewire" .Cd "device fwip" .Ed .Pp Alternatively, to load the .Xr fwip 4 driver at boot time, place the following lines in .Xr loader.conf 5 : .Bd -literal -offset indent firewire_load="YES" if_fwip_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides standard IP over FireWire (IEEE 1394) based on the protocols described in RFC 2734 and RFC 3146. .Pp The .Xr firewire 4 and .Xr fwohci 4 drivers must be configured in the kernel as well. .Pp This driver supports .Xr polling 4 as well if it is compiled with the .Dv DEVICE_POLLING option. .Sh SEE ALSO .Xr arp 4 , .Xr firewire 4 , .Xr fwe 4 , .Xr fwohci 4 , .Xr netintro 4 , .Xr polling 4 , .Xr ifconfig 8 , .Xr kldload 8 , .Xr sysctl 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 5.3 . .Sh AUTHORS .An -nosplit The .Nm driver and this manual page were written by .An Doug Rabson , based on earlier work by .An Hidetoshi Shimokawa . .Sh BUGS This driver currently does not support the MCAP protocol for multicast IP over FireWire. Multicast packets are treated as broadcast packets which is sufficient for most trivial uses of multicast. diff --git a/share/man/man4/fxp.4 b/share/man/man4/fxp.4 index c21879c9c764..c383a64c274a 100644 --- a/share/man/man4/fxp.4 +++ b/share/man/man4/fxp.4 @@ -1,183 +1,183 @@ .\" .\" Copyright (c) 1997 David E. O'Brien .\" .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. .\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT, .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt FXP 4 .Os .Sh NAME .Nm fxp .Nd "Intel EtherExpress PRO/100 Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device fxp" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_fxp_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for Ethernet adapters based on the Intel i82557, i82558, i82559, i82550, and i82562 chips. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It autoselect Enable autoselection of the media type and options .It 10baseT/UTP Set 10Mbps operation .It 100baseTX Set 100Mbps (Fast Ethernet) operation .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It full-duplex Set full duplex operation .El .Pp Note that 100baseTX media type is not available on the Pro/10. For further information on configuring this device, see .Xr ifconfig 8 . .Pp The .Nm driver supports reception and transmission of extended frames for .Xr vlan 4 . This capability of .Nm can be controlled by means of the .Cm vlanmtu parameter to .Xr ifconfig 8 . .Pp The .Nm driver also supports a special link option: .Bl -tag -width link0 .It Cm link0 Some chip revisions have loadable microcode which can be used to reduce the interrupt load on the host cpu. Not all boards have microcode support. Setting the .Cm link0 flag with .Xr ifconfig 8 will download the microcode to the chip if it is available. .El .Sh HARDWARE Adapters supported by the .Nm driver include: .Pp .Bl -bullet -compact .It Intel EtherExpress PRO/10 .It Intel InBusiness 10/100 .It Intel PRO/100B / EtherExpressPRO/100 B PCI Adapter .It Intel PRO/100+ Management Adapter .It Intel PRO/100 VE Desktop Adapter .It Intel PRO/100 M Desktop Adapter .It Intel PRO/100 S Desktop, Server and Dual-Port Server Adapters .It Contec C-NET(PI)-100TX (PC-98) .It NEC PC-9821Ra20, Rv20, Xv13, Xv20 internal 100Base-TX (PC-98) .It NEC PC-9821X-B06 (PC-98) .It Many on-board network interfaces on Intel motherboards .El .Sh DIAGNOSTICS .Bl -diag .It "fxp%d: couldn't map memory" A fatal initialization error has occurred. .It "fxp%d: couldn't map interrupt" A fatal initialization error has occurred. .It "fxp%d: Failed to malloc memory" There are not enough mbuf's available for allocation. .It "fxp%d: device timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .It "fxp%d: Ethernet address ff:ff:ff:ff:ff:ff" In some Alpha's (AXPpci and Multia) you must tell the driver to use (slower) I/O rather than memory to access the card. Create, if it does not yet exist, and add to the file .Pa /boot/device.hints the line .Dq Li hint.fxp.0.prefer_iomap="0" . .It "fxp%d: Microcode loaded, int_delay: %d usec bundle_max: %d" The chip has successfully downloaded the microcode, and changed the parameterized values to the given settings. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr polling 4 , .Xr vlan 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 2.1 . .Sh AUTHORS .An -nosplit The .Nm device driver was written by .An David Greenman . It has then been updated to use the busdma API and made endian-clean by .An Maxime Henrion . This manual page was written by .An David E. O'Brien . diff --git a/share/man/man4/hme.4 b/share/man/man4/hme.4 index 37b11040ccaa..87d9080789ac 100644 --- a/share/man/man4/hme.4 +++ b/share/man/man4/hme.4 @@ -1,150 +1,150 @@ .\" $NetBSD: hme.4,v 1.4 2003/02/14 15:20:18 grant Exp $ .\" .\" Copyright (c) 2001 The NetBSD Foundation, Inc. .\" All rights reserved. .\" .\" This code is derived from software contributed to The NetBSD Foundation .\" by Klaus Klein. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by the NetBSD .\" Foundation, Inc. and its contributors. .\" 4. Neither the name of The NetBSD Foundation nor the names of its .\" contributors may be used to endorse or promote products derived .\" from this software without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS .\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt HME 4 .Os .Sh NAME .Nm hme .Nd "Sun Microelectronics STP2002-STQ Ethernet interfaces device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device hme" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_hme_load="YES" .Ed .Sh DESCRIPTION The .Nm driver supports Sun Microelectronics STP2002-STQ Fast Ethernet interfaces. .Sh HARDWARE The .Nm driver supports the on-board Ethernet interfaces of many Sun .Tn UltraSPARC workstation and server models. .Pp Cards supported by the .Nm driver include: .Pp .Bl -bullet -compact .It Sun PCI SunSwift Adapter .Pq Dq SUNW,hme .It Sun SBus SunSwift Adapter .Dq ( hme and .Dq SUNW,hme ) .It Sun PCI Sun100BaseT Adapter 2.0 .Pq Dq SUNW,hme .It Sun SBus Sun100BaseT 2.0 .Pq Dq SUNW,hme .It Sun PCI Quad FastEthernet Controller .Pq Dq SUNW,qfe .It Sun SBus Quad FastEthernet Controller .Pq Dq SUNW,qfe .El .Sh NOTES On sparc64 the .Nm driver respects the .Va local-mac-address? system configuration variable which can be set in the Open Firmware boot monitor using the .Ic setenv command or by .Xr eeprom 8 . If set to .Dq Li false (the default), the .Nm driver will use the system's default MAC address for all of its devices. If set to .Dq Li true , the unique MAC address of each interface is used if present rather than the system's default MAC address. .Pp Supported interfaces having their own MAC address include on-board versions on boards equipped with more than one Ethernet interface and all add-on cards except the single-port SBus versions. .Sh SEE ALSO .Xr gem 4 , .Xr intro 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr eeprom 8 , .Xr ifconfig 8 .Rs .%T "STP2002QFP Fast Ethernet, Parallel Port, SCSI (FEPS) User's Guide" .%D April 1996 .%A Sun Microelectronics .%O http://www.sun.com/oem/products/manuals/STP2002QFP-UG.pdf .Re .Sh HISTORY The .Nm driver first appeared in .Nx 1.5 . The first .Fx version to include it was .Fx 5.0 . .Sh AUTHORS The .Nm driver was written by .An Paul Kranenburg .Aq pk@NetBSD.org . diff --git a/share/man/man4/ipw.4 b/share/man/man4/ipw.4 index 57da181fd2a5..0903cbbebcfa 100644 --- a/share/man/man4/ipw.4 +++ b/share/man/man4/ipw.4 @@ -1,126 +1,126 @@ .\" Copyright (c) 2004 .\" Damien Bergamini . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice unmodified, this list of conditions, and the following .\" disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Os .Dt IPW 4 .Sh NAME .Nm ipw .Nd "Intel PRO/Wireless 2100 IEEE 802.11 driver" .Sh SYNOPSIS To compile support for the .Xr ipw 4 -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device ipw" .Cd "device pci" .Cd "device wlan" .Ed .Pp Alternatively, to load the .Xr ipw 4 driver at boot time, place the following lines in .Xr loader.conf 5 : .Bd -literal -offset indent if_ipw_load="YES" wlan_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for the .Tn Intel PRO/Wireless 2100 MiniPCI network adapter. .Pp By default, the .Nm driver configures the adapter for BSS operation (aka infrastructure mode). This mode requires the use of an access point. .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Pp This driver requires firmware to be loaded before it will work. You need to obtain .Xr ipwcontrol 8 from the IPW web page listed below to accomplish loading the firmware before .Xr ifconfig 8 will work. .Sh EXAMPLES Join an existing BSS network (i.e., connect to an access point): .Pp .Dl "ifconfig ipw0 inet 192.168.0.20 netmask 0xffffff00" .Pp Join a specific BSS network with network name .Dq Li my_net : .Pp .Dl "ifconfig ipw0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net" .Pp Join a specific BSS network with 40-bit WEP encryption: .Bd -literal -offset indent ifconfig ipw0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e wepmode on wepkey 0x1234567890 .Ed .Pp Join a specific BSS network with 104-bit WEP encryption: .Bd -literal -offset indent ifconfig ipw0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e wepmode on wepkey 0x01020304050607080910111213 .Ed .Sh DIAGNOSTICS .Bl -diag .It "ipw%d: device timeout" The driver will reset the hardware. This should not happen. .It "ipw%d: Please load firmware" The required firmware has not been loaded into the card, and therefore the card cannot operate. Load the firmware with .Xr ipwcontrol 8 before proceeding. .El .Sh SEE ALSO .Xr an 4 , .Xr ath 4 , .Xr iwi 4 , .Xr pci 4 , .Xr wi 4 , .Xr wlan 4 , .Xr ifconfig 8 , .Xr ipwcontrol 8 , .Xr wicontrol 8 .Rs .%T The IPW Web Page .%O http://damien.bergamini.free.fr/ipw/ .Re .Sh AUTHORS The .Nm driver was written by .An Damien Bergamini Aq damien@FreeBSD.org . diff --git a/share/man/man4/iwi.4 b/share/man/man4/iwi.4 index 65dc8a66995f..75afd7578e1d 100644 --- a/share/man/man4/iwi.4 +++ b/share/man/man4/iwi.4 @@ -1,125 +1,125 @@ .\" Copyright (c) 2004, 2005 .\" Damien Bergamini . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice unmodified, this list of conditions, and the following .\" disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Os .Dt IWI 4 .Sh NAME .Nm iwi .Nd "Intel PRO/Wireless 2200BG/2225BG/2915ABG IEEE 802.11 driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device iwi" .Cd "device pci" .Cd "device wlan" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_iwi_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for .Tn Intel PRO/Wireless 2200BG/2915ABG MiniPCI and 2225BG PCI network adapters. .Pp By default, the .Nm driver configures the adapter for BSS operation (aka infrastructure mode). This mode requires the use of an access point. .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Pp This driver requires firmware to be loaded before it will work. You need to obtain .Xr iwicontrol 8 from the IWI web page listed below to accomplish loading the firmware before .Xr ifconfig 8 will work. .Sh EXAMPLES Join an existing BSS network (i.e., connect to an access point): .Pp .Dl "ifconfig iwi0 inet 192.168.0.20 netmask 0xffffff00" .Pp Join a specific BSS network with network name .Dq Li my_net : .Pp .Dl "ifconfig iwi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net" .Pp Join a specific BSS network with 64-bit WEP encryption: .Bd -literal -offset indent ifconfig iwi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e wepmode on wepkey 0x1234567890 .Ed .Pp Join a specific BSS network with 128-bit WEP encryption: .Bd -literal -offset indent ifconfig iwi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e wepmode on wepkey 0x01020304050607080910111213 .Ed .Sh DIAGNOSTICS .Bl -diag .It "iwi%d: device timeout" The driver will reset the hardware. This should not happen. .It "iwi%d: Please load firmware" The required firmware has not been loaded into the card, and therefore the card cannot operate. Load the firmware with .Xr iwicontrol 8 before proceeding. .El .Sh SEE ALSO .Xr an 4 , .Xr ath 4 , .Xr ipw 4 , .Xr pci 4 , .Xr wi 4 , .Xr wlan 4 , .Xr ifconfig 8 , .Xr iwicontrol 8 , .Xr wicontrol 8 .Rs .%T The IWI Web Page .%O http://damien.bergamini.free.fr/ipw/ .Re .Sh AUTHORS The .Nm driver was written by .An Damien Bergamini Aq damien@FreeBSD.org . diff --git a/share/man/man4/kue.4 b/share/man/man4/kue.4 index 63aefef4d573..c943926f15a0 100644 --- a/share/man/man4/kue.4 +++ b/share/man/man4/kue.4 @@ -1,142 +1,142 @@ .\" Copyright (c) 1997, 1998, 1999, 2000 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt KUE 4 .Os .Sh NAME .Nm kue .Nd "Kawasaki LSI KL5KUSB101B USB Ethernet driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device uhci" .Cd "device ohci" .Cd "device usb" .Cd "device kue" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_kue_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for USB Ethernet adapters based on the Kawasaki LSI KL5KLUSB101B chipset. .Pp 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. .Pp The Kawasaki chipset supports only 10Mbps half-duplex mode, hence there are no .Xr ifmedia 4 modes to select. .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports Kawasaki LSI KL5KLUSB101B based USB Ethernet adapters including: .Pp .Bl -bullet -compact .It 3Com 3c19250 .It 3Com 3c460 HomeConnect Ethernet USB Adapter .It ADS Technologies USB-10BT .It AOX USB101 .It ATen UC10T .It Abocom URE 450 .It Corega USB-T .It D-Link DSB-650C .It Entrega NET-USB-E45, NET-HUB-3U1E .It I/O Data USB ETT .It Kawasaki DU-H3E .It LinkSys USB10T .It Netgear EA101 .It Peracom USB Ethernet Adapter .It SMC 2102USB, 2104USB .El .Sh DIAGNOSTICS .Bl -diag .It "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. .It "kue%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .El .Sh SEE ALSO .Xr arp 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 4.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ee.columbia.edu . .Sh BUGS The .Nm driver does not accumulate Ethernet collisions statistics because the Kawasaki firmware does not appear to maintain any internal statistics. diff --git a/share/man/man4/lge.4 b/share/man/man4/lge.4 index 6d148d109f04..dd95e892637d 100644 --- a/share/man/man4/lge.4 +++ b/share/man/man4/lge.4 @@ -1,159 +1,159 @@ .\" Copyright (c) 2001 Wind River Systems .\" Copyright (c) 1997, 1998, 1999, 2000, 2001 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt LGE 4 .Os .Sh NAME .Nm lge .Nd "Level 1 LXT1001 NetCellerator PCI Gigabit Ethernet adapter driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device lge" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_lge_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for various NICs based on the Level 1 LXT1001 NetCellerator Gigabit Ethernet controller chip. .Pp The LXT1001 supports fiber PHYs and also a GMII port for use with 10/100/1000 copper PHYs, however there are currently no NICs on the market that use this feature. .Pp The LXT1001 supports TCP/IP checksum offload for receive and VLAN-based filtering as well as a 64-bit multicast hash filter. It also supports jumbo frames, which can be configured via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the .Xr ifconfig 8 utility configures the adapter to receive and transmit jumbo frames. Using jumbo frames can greatly improve performance for certain tasks, such as file transfers and data streaming. .Pp The .Nm driver supports the following media types: .Bl -tag -width ".Cm 1000baseSX" .It Cm autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to .Xr rc.conf 5 . .It Cm 1000baseSX Set 1000baseSX operation over fiber optic cable. Both .Cm full-duplex and .Cm half-duplex modes are supported. .El .Pp The .Nm driver supports the following media options: .Bl -tag -width ".Cm full-duplex" .It Cm full-duplex Force full duplex operation. .It Cm half-duplex Force half duplex operation. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE Adapters supported by the .Nm driver include: .Pp .Bl -bullet -compact .It SMC TigerCard 1000 (SMC9462SX) .It D-Link DGE-500SX .El .Sh DIAGNOSTICS .Bl -diag .It "lge%d: couldn't map memory" A fatal initialization error has occurred. .It "lge%d: couldn't map ports" A fatal initialization error has occurred. .It "lge%d: couldn't map interrupt" A fatal initialization error has occurred. .It "lge%d: no memory for softc struct!" The driver failed to allocate memory for per-device instance information during initialization. .It "lge%d: failed to enable memory mapping!" The driver failed to initialize PCI shared memory mapping. This might happen if the card is not in a bus-master slot. .It "lge%d: no memory for jumbo buffers!" The driver failed to allocate memory for jumbo frames during initialization. .It "lge%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Rs .%T Level 1 LXT1001 Programming Manual .%O http://www.FreeBSD.org/~wpaul/Level1/LXT1001SRM.pdf .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 4.4 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq william.paul@windriver.com . diff --git a/share/man/man4/man4.i386/arl.4 b/share/man/man4/man4.i386/arl.4 index d2a1c3be9311..7cbe5d0616b1 100644 --- a/share/man/man4/man4.i386/arl.4 +++ b/share/man/man4/man4.i386/arl.4 @@ -1,116 +1,117 @@ .\" Copyright (c) 2004 .\" Ivan Sharov . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Ivan Sharov. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Ivan Sharov AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Ivan Sharov OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt ARL 4 i386 .Os .Sh NAME .Nm arl .Nd "Aironet Arlan 655 wireless network adapter driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device arl" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_arl_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for Aironet Arlan 655 wireless network adapters. The Arlan 655 series adapters operate at 354kbps, 512kbps, 1Mbps and 2Mbps. .Pp The Aironet Arlan 655 devices support Aironet TMA, Aironet Non-TMA and PSP operating modes. .Pp By default, the .Nm driver configures the Aironet Arlan 655 card for TMA operation. .Pp To set up Radio Network parameters, use .Xr arlcontrol 8 . .Sh SEE ALSO .Xr arp 4 , .Xr netintro 4 , .Xr arlcontrol 8 , .Xr ifconfig 8 .Sh LIMITATIONS When using .Xr ifconfig 8 for setting .Va SSID you must use a 4-byte even hexadecimal digit value and it must start with 00 or 02. .Pp You can change .Va channel for current .Va country only through .Xr ifconfig 8 . You must use .Xr arlcontrol 8 for changing .Va country . .Pp Cannot change link-level address. .Sh HISTORY The .Nm device driver first appeared in .Fx 5.3 . .Sh AUTHORS .An -nosplit The .Nm driver was initially written by .An Ivan Sharov Aq ivan.sharov@iname.com . .Aq ran@styx.aic.net wrote the .Xr arlcontrol 8 utility and added .Xr ioctl 2 support to the driver. .An Stanislav Svirid Aq count@riss-telecom.ru ported this driver to the new ISA architecture, merged some al driver changes, fixed some bugs and made it a module. .An Yuri Kurenkov Aq y.kurenkov@init.ru wrote this manpage. diff --git a/share/man/man4/man4.i386/cp.4 b/share/man/man4/man4.i386/cp.4 index 4b1f7f890bad..d5ac69e50fb6 100644 --- a/share/man/man4/man4.i386/cp.4 +++ b/share/man/man4/man4.i386/cp.4 @@ -1,115 +1,115 @@ .\" Copyright (c) 2003-2004 Roman Kurakin .\" Copyright (c) 2003-2004 Cronyx Engineering .\" All rights reserved. .\" .\" This software is distributed with NO WARRANTIES, not even the implied .\" warranties for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. .\" .\" Authors grant any other persons or organisations a permission to use, .\" modify and redistribute this software in source and binary forms, .\" as long as this message is kept with the software, all derivative .\" works or modified versions. .\" .\" Cronyx Id: cp.4,v 1.1.2.5 2004/06/21 17:47:40 rik Exp $ .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt CP 4 i386 .Os .Sh NAME .Nm cp .Nd "driver for synchronous Cronyx Tau-PCI WAN adapters" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration -file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device cp" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_cp_load="YES" .Ed .Pp Additional options: .Cd "device sppp" .Cd "options NETGRAPH" .Cd "options NETGRAPH_CRONYX" .Sh DESCRIPTION The .Nm driver needs either .Xr sppp 4 or .Xr netgraph 4 . Which one to use is determined by the .Dv NETGRAPH_CRONYX option. If this option is present in your kernel configuration file, the .Nm driver will be compiled with .Xr netgraph 4 support. Otherwise, it will be compiled with .Xr sppp 4 support. .Pp Refer to .Xr sconfig 8 for information about the .Nm adapter configuration. .Sh HARDWARE The .Nm driver supports the following models of Tau-PCI WAN adapters: .Pp .Bl -tag -width 20n -compact .It Cronyx Tau-PCI V.35 and RS-232 interfaces .It Cronyx Tau-PCI/R RS-530(RS-449) and X.21 interfaces .It Cronyx Tau-PCI-L one V.35 and RS-232 interface, low profile .It Cronyx Tau-PCI-L/R one RS-530(RS-449) and X.21 interface, low profile .It Cronyx Tau-PCI-E1 fractional E1 interfaces .It Cronyx Tau-PCI-G703 unframed E1 interfaces .It Cronyx Tau-PCI-2E1 fractional E1 and unframed E1 interfaces .It Cronyx Tau-PCI-4E1 fractional E1 and unframed E1 interfaces .It Cronyx Tau-PCI-E3 E3 interface .It Cronyx Tau-PCI-T3 T3 interface .It Cronyx Tau-PCI-STS1 STS-1 interface .El .Sh SEE ALSO .Xr ctau 4 , .Xr cx 4 , .Xr sppp 4 , .Xr ifconfig 8 , .Xr sconfig 8 , .Xr spppcontrol 8 .Sh HISTORY The .Nm driver was added in .Fx 5.3 and .Fx 4.11 . The .Nm driver for previous versions of .Fx is available from .Pa http://www.cronyx.ru/ . diff --git a/share/man/man4/man4.i386/cs.4 b/share/man/man4/man4.i386/cs.4 index 12fc4978507e..baf2c2fc0bf6 100644 --- a/share/man/man4/man4.i386/cs.4 +++ b/share/man/man4/man4.i386/cs.4 @@ -1,145 +1,145 @@ .\" .\" Copyright (c) 1998 Michael Smith .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt CS 4 i386 .Os .Sh NAME .Nm cs .Nd "Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration -file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device cs" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_cs_load="YES" .Ed .Pp In .Pa /boot/device.hints : .Cd hint.cs.0.at="isa" .Cd hint.cs.0.port="0x300" .Cd hint.cs.0.irq="10" .Cd hint.cs.0.maddr="0xd000" .Sh DESCRIPTION The .Nm driver provides support for ISA Ethernet adapters based on the .Tn Crystal Semiconductor CS8900 and .Tn CS8920 NICs. These devices are used on the .Tn IBM EtherJet ISA adapters and in many embedded applications where the high integration, small size and low cost of the CS89x0 family compensate for their drawbacks. .Pp The .Nm driver will obtain configuration parameters either from .Pa /boot/device.hints or from the card. At least the I/O port number must be specified. Other parameters specified in .Pa /boot/device.hints will be used if present; the card may be soft-configured so these may be any valid value. Adapters based on the CS8920 normally offer PnP configuration and the driver will detect the .Tn IBM EtherJet and the .Tn CSC6040 adapters automatically. .Pp Note that the CS8900 is limited to 4 IRQ values; these are normally implemented as 5, 10, 11 and 12. The CS8920 has no such limitation. .Pp Memory-mapped and DMA operation are not supported at this time. .Sh DIAGNOSTICS .Bl -diag .It "cs%d: full/half duplex negotiation timeout" The attempt to negotiate duplex settings with the hub timed out. This may indicate a cabling problem or a faulty or incompatible hub. .It "cs%d: failed to enable " The CS89x0 failed to select the nominated media, either because it is not present or not operating correctly. .It "cs%d: No EEPROM, assuming defaults" The CS89x0 does not have an EEPROM, or the EEPROM is hopelessly damaged. Operation will only be successful if the configuration entry lists suitable values for the adapter. .It "cs%d: Invalid irq" The IRQ specified in the configuration entry is not valid for the adapter. .It "cs%d: Could not allocate memory for NIC" There is a critical memory shortage. The adapter will not function. .It "cs%d: Adapter has no media" The adapter is not configured for a specific media type. The media type will have to be manually set. .It "This is a %s, but LDN %d is disabled" The PnP probe code found a recognised adapter, but the adapter is disabled. .It "failed to read pnp parms" A PnP adapter was found, but configuration parameters for it could not be read. .It "failed to pnp card parameters" The parameters obtained via PnP were not accepted by the driver. The adapter may not function. .El .Sh CAVEATS The CS89x0 family of adapters have a very small RAM buffer (4K). This may cause problems with extremely high network loads or bursty network traffic. In particular, NFS operations should be limited to 1k read/write transactions in order to avoid overruns. .Sh SEE ALSO .Xr arp 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh AUTHORS .An -nosplit The .Nm device driver was written by .An Maxim Bolotin and .An Oleg Sharoiko . This manpage was written by .An Michael Smith . diff --git a/share/man/man4/man4.i386/cx.4 b/share/man/man4/man4.i386/cx.4 index f25db06334c6..46cbc42734c9 100644 --- a/share/man/man4/man4.i386/cx.4 +++ b/share/man/man4/man4.i386/cx.4 @@ -1,141 +1,141 @@ .\" Copyright (c) 2003-2004 Roman Kurakin .\" Copyright (c) 2003-2004 Cronyx Engineering .\" All rights reserved. .\" .\" This software is distributed with NO WARRANTIES, not even the implied .\" warranties for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. .\" .\" Authors grant any other persons or organisations a permission to use, .\" modify and redistribute this software in source and binary forms, .\" as long as this message is kept with the software, all derivative .\" works or modified versions. .\" .\" Cronyx Id: cx.4,v 1.1.2.6 2004/06/21 17:56:40 rik Exp $ .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt CX 4 i386 .Os .Sh NAME .Nm cx .Nd "driver for synchronous/asynchronous Cronyx Sigma WAN adapters" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration -file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device cx" .Ed Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_cx_load="YES" .Ed .Pp Additional options: .Cd "device sppp" .Cd "options NETGRAPH" .Cd "options NETGRAPH_CRONYX" .Pp In .Pa /boot/device.hints : .Cd hint.cx.0.at="isa" .Cd hint.cx.0.port="0x240" .Cd hint.cx.0.irq="15" .Cd hint.cx.0.drq="7" .Sh DESCRIPTION The .Nm driver needs either .Xr sppp 4 or .Xr netgraph 4 . Which one to use is determined by the .Dv NETGRAPH_CRONYX option. If this option is present in your kernel configuration file, the .Nm driver will be compiled with .Xr netgraph 4 support. Otherwise, it will be compiled with .Xr sppp 4 support. .Pp The base I/O port address specified in .Pa /boot/device.hints must match the port address set by the jumpers on the board. The DMA I/O channel and interrupt request numbers are configured by software at adapter initialization. Legal values are: .Pp .Bl -tag -compact -width Port: .It Port : 0x240, 0x260, 0x280, 0x300, 0x320, 0x380 .It IRQ : 3, 5, 7, 10, 11, 12, 15 .It DMA : 5, 6, 7 .El .Pp The .Nm driver supports autodetection. As for all non-PNP hardware, using autodetection could lead to some potential problems with other devices during the hardware detection process. It is always better to specify hardware resources manually. .Pp Refer to .Xr sconfig 8 for information about the .Nm adapter configuration. .Sh HARDWARE The .Nm driver supports the following cards: .Pp .Bl -bullet -compact .It Cronyx Sigma-22, Sigma-24 .It Cronyx Sigma-100 .It Cronyx Sigma-400, Sigma-401, Sigma-404, Sigma-410, Sigma-440 .It Cronyx Sigma-500 .It Cronyx Sigma-703 .It Cronyx Sigma-800, Sigma-801, Sigma-810, Sigma-840 .El .Sh SEE ALSO .Xr cp 4 , .Xr ctau 4 , .Xr sppp 4 , .Xr ifconfig 8 , .Xr sconfig 8 , .Xr spppcontrol 8 .Sh HISTORY The .Nm driver was updated in .Fx 5.2 and .Fx 4.10 . In most of the previous versions of .Fx the .Nm driver is out of date. The .Nm driver for previous versions of .Fx is available from .Pa http://www.cronyx.ru/ . diff --git a/share/man/man4/man4.i386/el.4 b/share/man/man4/man4.i386/el.4 index 7d60d133fa8d..3188d82cc8f5 100644 --- a/share/man/man4/man4.i386/el.4 +++ b/share/man/man4/man4.i386/el.4 @@ -1,80 +1,80 @@ .\" .\" Copyright (c) 1994 James A. Jegers .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. The name of the author may not be used to endorse or promote products .\" derived from this software without specific prior written permission .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt EL 4 i386 .Os .Sh NAME .Nm el .Nd "Ethernet driver for 3Com Etherlink 3C501 devices" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration -file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device el" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_el_load="YES" .Ed .Pp In .Pa /boot/device.hints : .Cd hint.el.0.at="isa" .Cd hint.el.0.port="0x300" .Cd hint.el.0.irq="9" .Sh DESCRIPTION The .Nm interface provides support for the 3Com 3c501 8bit ISA Ethernet card. The 3c501 card is known to be quite slow, and a different Ethernet card should be used if possible. However, they allow inexpensive access to 10 Mb/s Ethernet networks. .Pp The valid I/O ports are in the range 0x280-0x3f0. .Sh HARDWARE The .Nm driver supports the 3Com 3c501 8bit ISA Ethernet card. .Sh SEE ALSO .Xr ed 4 , .Xr ep 4 , .Xr ie 4 , .Xr intro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh BUGS The driver assumes the card is configured for the same IRQ as the kernel. No probing or checking is done to determine if this is the case. .Pp Does not currently support DMA. .Pp Does not currently support multicasts. diff --git a/share/man/man4/man4.i386/ep.4 b/share/man/man4/man4.i386/ep.4 index a4fe0e9a3fd9..7f162cf24aa6 100644 --- a/share/man/man4/man4.i386/ep.4 +++ b/share/man/man4/man4.i386/ep.4 @@ -1,205 +1,205 @@ .\" .\" Copyright (c) 1994 Herb Peyerl .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Herb Peyerl .\" 3. The name of the author may not be used to endorse or promote products .\" derived from this software without specific prior written permission .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt EP 4 i386 .Os .Sh NAME .Nm ep .Nd "Ethernet driver for 3Com Etherlink III (3c5x9) interfaces" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration -file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device ep" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_ep_load="YES" .Ed .Sh DESCRIPTION The .Nm device driver supports network adapters based on the 3Com 3C5x9 Etherlink III Parallel Tasking chipset. .Pp Various models of these cards come with a different assortment of connectors: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It AUI/DIX Standard 15 pin connector, also known as 10base5 (thick-net) .It 10Base2 BNC, also known as thin-net .It 10BaseT UTP, also known as twisted pair .El .Pp The default port to use is the port that has been selected with the setup utility. To override this, use the following media options with .Xr ifconfig 8 or in your .Pa /etc/rc.conf file. .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It 10base5/AUI Use the AUI port. .It 10base2/BNC Use the BNC port. .It 10baseT/UTP Use the UTP port. .El .Pp If there are multiple cards in the computer, they are searched for in the following order: bus, slot, then Ethernet address. .Sh HARDWARE The .Nm driver supports Ethernet adapters based on the 3Com 3C5x9 Etherlink III Parallel Tasking chipset, including: .Pp .Bl -bullet -compact .It 3Com 3C1 CF .It 3Com 3C509-TP, 3C509-BNC, 3C509-Combo, 3C509-TPO, 3C509-TPC ISA .It 3Com 3C509B-TP, 3C509B-BNC, 3C509B-Combo, 3C509B-TPO, 3C509B-TPC ISA .It 3Com 3C529, 3C529-TP MCA .It 3Com 3C562/3C563 PCMCIA .It 3Com 3C569B-J-TPO, 3C569B-J-COMBO CBUS .It 3Com 3C574, 3C574TX, 3C574-TX, 3CCFE574BT, 3CXFE574BT, 3C3FE574BT PCMCIA .It 3Com 3C579-TP, 3C579-BNC EISA .It 3Com 3C589, 3C589B, 3C589C, 3C589D, 3CXE589DT PCMCIA .It 3Com 3CCFEM556B, 3CCFEM556BI PCMCIA .It 3Com 3CXE589EC, 3CCE589EC, 3CXE589ET, 3CCE589ET PCMCIA .It 3Com Megahertz 3CCEM556, 3CXEM556, 3CCEM556B, 3CXEM556B, 3C3FEM556C PCMCIA .It 3Com OfficeConnect 3CXSH572BT, 3CCSH572BT PCMCIA .El .Sh NOTES The 3c509 card has no jumpers to set the address. 3Com supplies software to set the address of the card in software. To find the card on the ISA bus, the kernel performs a complex scan operation at IO address 0x110. Beware! Avoid placing other cards at that address! .Pp Furthermore, the 3c509 should only be configured in EISA mode when installed in a computer that has actual EISA slots (and an EISA-aware BIOS). The normal driver auto-detection support is sufficient for non-EISA systems. .Pp Many different companies sold the 3Com PC Cards under their own private label. These cards also work. .Sh DIAGNOSTICS .Bl -diag .It ep0: reset (status: %x) The driver has encountered a FIFO underrun or overrun. The driver will reset the card and the packet will be lost. This is not fatal. .It ep0: eeprom failed to come ready The eeprom failed to come ready. This probably means the card is wedged. .It ep0: 3c509 in test mode. Erase pencil mark! This means that someone has scribbled with pencil in the test area on the card. Erase the pencil mark and reboot. (This is not a joke). .It ep0: No I/O space?! The driver was unable to allocate the I/O space that it thinks should be there. Look for conflicts with other devices. .It ep0: No irq?! The driver couldn't allocate the interrupt it wanted. Look for conflicts, although sharing interrupts for PC Card is normal. .It ep0: No connectors! The driver querried the hardware for what ethernet attachment were present, but the hardware reported none that the driver recognized. .It ep0: Unable to get Ethernet address! The driver was unabel to read the ethernet address from the EEPROM. This is likely the result of the card being wedged. .It ep0: if_alloc() failed The driver was unable to allocate a ifnet structure. This may happen in extremely low memory conditions. .It ep0: strange connector type in EEPROM: assuming AUI The driver does not know what to do with the information the EEPROM has about connectors, so it is assuming the worst. .It ep0: unknown ID 0xXXXXXXXX The driver has found an ID that it believes it supports, but doesn't have a specific identification string to present to the user. .It ep0: <%s> at port 0x%03x in EISA mode The 3C509 ISA card is in EISA mode. This message appears to be purely informational. .It ep0: <%s> at x0%03x in PnP mode This card appears to be in Plug and Play mode. It should be probed as part of the plug and play phase of the ISA probes. .It ep0: Invalid EEPROM checksum! The EEPROM has a bad checksum, so the driver is ignoring the card. .It ep0: bus_setup_intr() failed! The driver was unable to setup the interrupt handler. This should never happen. .El .Sh SEE ALSO .Xr ed 4 , .Xr el 4 , .Xr ie 4 , .Xr intro 4 , .Xr ng_ether 4 , .Xr vx 4 , .Xr ifconfig 8 .Sh STANDARDS are great. There is so many to choose from. .Sh BUGS Support for the 3Com 3C1 is not working. diff --git a/share/man/man4/man4.i386/ex.4 b/share/man/man4/man4.i386/ex.4 index c87c0b753a67..b7a6b2c7b3f2 100644 --- a/share/man/man4/man4.i386/ex.4 +++ b/share/man/man4/man4.i386/ex.4 @@ -1,121 +1,121 @@ .\" .\" Copyright (c) 1997 David E. O'Brien .\" .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. .\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT, .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt EX 4 i386 .Os .Sh NAME .Nm ex .Nd "Ethernet device driver for the Intel EtherExpress Pro/10 and Pro/10+" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration -file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device ex" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_ex_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for Ethernet adapters based on the Intel i82595 chip. .Pp On the ISA bus, the card will be searched for in the I/O address range 0x200 - 0x3a0. The IRQ will be read from the EEPROM on the card. For correct operation Plug-N-Play support should be disabled. .Pp On the PC Card bus, the card will be automatically recognized and configured. .Sh HARDWARE The .Nm driver supports the following Ethernet adapters: .Pp .Bl -bullet -compact .It Intel EtherExpress Pro/10 ISA .It Intel EtherExpress Pro/10+ ISA .It Olicom OC2220 Ethernet PC Card .It Olicom OC2232 Ethernet/Modem PC Card .It Silicom Ethernet LAN PC Card .It Silicom EtherSerial LAN PC Card .El .Sh DIAGNOSTICS .Bl -diag .It "ex%d: Intel EtherExpress Pro/10, address %6D, connector %s" The device probe found an installed card, and was able to correctly install the device driver. .It "ex%d: WARNING: board's EEPROM is configured for IRQ %d, using %d" The device probe detected that the board is configured for a different interrupt than the one specified in the kernel configuration file. .It "ex%d: invalid IRQ." The device probe detected an invalid IRQ setting. .El .Sh SEE ALSO .Xr arp 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 2.2 . .Sh AUTHORS .An -nosplit The .Nm device driver was written by .An Javier Mart\('in Rueda . The PC Card attachment was written by .An Mitsuru ISAWAKI and .An Warner Losh . This manual page was written by .An David E. O'Brien . .Sh BUGS Currently the driver does not support multicast. .Pp The Silicom EtherSerial card's serial port does not currently work. The Olicom OC2232 PC Card should work with the .Nm driver, but is currently completely broken. diff --git a/share/man/man4/man4.i386/fe.4 b/share/man/man4/man4.i386/fe.4 index bf08c2e1d2a2..87f9cd423d27 100644 --- a/share/man/man4/man4.i386/fe.4 +++ b/share/man/man4/man4.i386/fe.4 @@ -1,375 +1,375 @@ .\" All Rights Reserved, Copyright (C) Fujitsu Limited 1995 .\" .\" This document may be used, modified, copied, distributed, and sold, in .\" both source and printed form provided that the above copyright, these .\" terms and the following disclaimer are retained. The name of the author .\" and/or the contributor may not be used to endorse or promote products .\" derived from this software without specific prior written permission. .\" .\" THIS DOCUMENT IS PROVIDED BY THE AUTHOR AND THE CONTRIBUTOR ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR THE CONTRIBUTOR BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS DOCUMENT, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" Contributed by M. Sekiguchi . .\" for fe driver. .\" .\" $FreeBSD$ .Dd July 16, 2005 .Dt FE 4 i386 .Os .Sh NAME .Nm fe .Nd "Fujitsu MB86960A/MB86965A based Ethernet adapters" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration -file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device fe" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_fe_load="YES" .Ed .Pp In .Pa /boot/device.hints : .Cd hint.fe.0.at="isa" .Cd hint.fe.0.port="0x300" .Cd hint.fe.0.flags="0x0" .Sh DESCRIPTION The .Nm is a network device driver for Ethernet adapters based on Fujitsu MB86960A, MB86965A, or other compatible chips. .Pp The driver provides automatic I/O port address configuration and automatic IRQ configuration, when used with suitable adapter hardware. .Pp The driver works with program I/O data transfer technique. It gives a fair performance. Shared memory is never used, even if the adapter has one. .Pp It currently works with Fujitsu FMV-180 series for ISA, Allied-Telesis AT1700 series and RE2000 series for ISA, and Fujitsu MBH10302 PC card. .Ss Parameters In the .Pa /boot/device.hints file, two parameters, .Ar port and .Ar irq , must be specified to reflect adapter hardware settings. Another parameter .Ar flags can be specified to provide additional configuration as an option. .Pp The .Ar port parameter specifies a base I/O port address of the adapter. It must match with the hardware setting of the adapter. The .Ar port may be left unspecified by removing .Dl hint.fe.0.port="..." from the file. In that case, the driver tries to detect the hardware setting of the I/O address automatically. This feature may not work with some adapter hardware. .Pp The .Ar irq parameter specifies an IRQ number used by the adapter. It must match the hardware setting of the adapter. .Ar Irq may be left unspecified by removing .Dl hint.fe.0.irq="..." from the file. in that case, the driver tries to detect the hardware setting of the IRQ automatically. This feature may not work on some adapters. .Pp The .Ar flags is a numeric value which consists of a combination of various device settings. The following flags are defined in the current version. To specify two or more settings for a device, use a numeric sum of each flag value. Flag bits not specified below are reserved and must be set to 0. Actually, each bit is either just ignored by the driver, or tested and used to control undocumented features of the driver. Consult the source program for undocumented features. .Bl -tag -width 8n .It Li 0x007F These flag bits are used to initialize DLCR6 register of MB86960A/MB86965A chip, when the .Li 0x0080 bit of the .Ar flags is set. See below for more about DLCR6 override feature. The .Li 0x007F flag bits must be 0 unless the .Li 0x0080 bit is set, to maintain the compatibility with future versions of the driver. .It Li 0x0080 This flag overrides the default setting to the DLCR6 register of MB86960A/MB86965A chip by a user supplied value, which is taken from the lower 7 bits of the flag value. This is a troubleshooting flag and should not be used without understanding of the adapter hardware. Consult the Fujitsu manual for more information on DLCR6 settings. .El .Sh HARDWARE Controllers and cards supported by the .Nm driver include: .Pp .Bl -bullet -compact .It Allied Telesis RE1000, RE1000Plus, ME1500 (110-pin) .It CONTEC C-NET(98)P2, C-NET (9N)E (110-pin), C-NET(9N)C (ExtCard) .It CONTEC C-NET(PC)C PCMCIA Ethernet .It Eagle Tech NE200T .It Eiger Labs EPX-10BT .It Fujitsu FMV-J182, FMV-J182A .It Fujitsu MB86960A, MB86965A .It Fujitsu MBH10303, MBH10302 Ethernet PCMCIA .It Fujitsu Towa LA501 Ethernet .It HITACHI HT-4840-11 .It NextCom J Link NC5310 .It RATOC REX-5588, REX-9822, REX-4886, and REX-R280 .It RATOC REX-9880/9881/9882/9883 .It TDK LAC-98012, LAC-98013, LAC-98025, LAC-9N011 (110-pin) .It TDK LAK-CD021, LAK-CD021A, LAK-CD021BX .It Ungermann-Bass Access/PC N98C+(PC85152, PC85142), Access/NOTE N98(PC86132) (110-pin) .El .Sh OPTIONS The .Nm driver has some private options, which can be specified with an .Dq option statement in the kernel configuration file. The following lists the private options. The driver also accepts some other undocumented options, all of whose names start with a fixed prefix .Dv "FE_" . Consult the source program for undocumented options. .Bl -tag -width "FE_" .It Dv "FE_DEBUG=" Ns Ar level This option takes a numeric value .Ar level which controls the debugging level for the device and/or the driver. Setting the .Dv "FE_DEBUG" option to a value which is not listed here may cause undocumented behavior. The default setting of this option is 1. .Bl -bullet .It Setting .Dv "FE_DEBUG=0" makes most of debugging codes, including sanity check, be excluded from the object code of the driver. It generates fastest and smallest object code. Some emergency messages are logged even under this setting, though. .It Setting .Dv "FE_DEBUG=1" makes minimum debugging codes be included, setting the amount of logged messages minimum. Only fatal error messages are logged under this setting. .It Setting .Dv "FE_DEBUG=2" makes standard debugging codes be included, setting the amount of logged messages middle. Messages on lair events and/or questionable conditions are logged under this setting. .It Setting .Dv "FE_DEBUG=3" makes all debugging codes be included, and sets the amount of logged messages to the maximum possible. Redundant messages such as those reporting usual actions or dumping register values are logged under this setting. .El .El .Sh FEATURES SPECIFIC TO HARDWARE MODELS The .Nm driver has some features and limitations which depend on adapter hardware models. The following is a summary of these dependencies. .Ss Fujitsu FMV-180 series adapters Both automatic IRQ detection and automatic I/O port address detection is available with these adapters. .Pp Automatic I/O port address detection feature of .Nm works mostly fine for FMV-180 series. It works even if there are two or more FMV-180s in a system. However, some combination of other adapters may confuse the driver. It is recommended to explicitly specify .Ar port when you experience some difficulties with hardware probe. .Pp Automatic IRQ detection feature of .Nm works reliably for FMV-180 series. It is recommended to explicitly specify .Ar irq always for FMV-180. The hardware setting of IRQ is read from the configuration EEPROM on the adapter, even when the kernel config file specifies an IRQ value. The driver will generate a warning message, if the IRQ setting specified in .Pa /boot/device.hints does not match one stored in EEPROM. Then, it will use the value specified in the file. (This behavior has been changed from the previous releases.) .Ss Allied-Telesis AT1700 series and RE2000 series adapters Automatic I/O port address detection is available with Allied-Telesis AT1700 series and RE2000 series, while it is less reliable than FMV-180 series. Using the feature with Allied-Telesis adapters is not recommended. .Pp Automatic IRQ detection is also available with some limitation. The .Nm driver tries to get IRQ setting from the configuration EEPROM on the board, if .Ar irq is not specified in .Pa /boot/device.hints . Unfortunately, AT1700 series and RE2000 series seems to have two types of models; One type allows IRQ selection from 3/4/5/9, while the other from 10/11/12/15. Identification of the models are not well known. Hence, automatic IRQ detection with Allied-Telesis adapters may not be reliable. Specify an exact IRQ number if any troubles are encountered. .Pp Differences between AT1700 series and RE2000 series or minor models in those series are not recognized. .Ss Fujitsu MBH10302 PC card The .Nm driver supports Fujitsu MBH10302 and compatible PC cards. It requires the PC card (PCMCIA) support package. .Sh SEE ALSO .Xr netstat 1 , .Xr ed 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 , .Xr pccardd 8 .Sh HISTORY The .Nm driver appeared in .Fx 2.0.5 . .Sh AUTHORS, COPYRIGHT AND DISCLAIMER The .Nm driver was originally written and contributed by .An M. Sekiguchi Aq seki@sysrap.cs.fujitsu.co.jp , following the .Nm ed driver written by .An David Greenman . PC card support in .Nm is written by .An Hidetoshi Kimura Aq h-kimura@tokyo.se.fujitsu.co.jp . This manual page was written by .An M. Sekiguchi . .Pp .Em "All Rights Reserved, Copyright (C) Fujitsu Limited 1995" .Pp This document and the associated software may be used, modified, copied, distributed, and sold, in both source and binary form provided that the above copyright, these terms and the following disclaimer are retained. The name of the author and/or the contributor may not be used to endorse or promote products derived from this document and the associated software without specific prior written permission. .Pp THIS DOCUMENT AND THE ASSOCIATED SOFTWARE IS PROVIDED BY THE AUTHOR AND THE CONTRIBUTOR .Dq AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR THE CONTRIBUTOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENT AND THE ASSOCIATED SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .Sh BUGS Following are major known bugs: .Pp Statistics on the number of collisions maintained by the .Nm driver is not accurate; the .Fl i option of .Xr netstat 1 shows slightly less value than true number of collisions. .Pp More mbuf clusters are used than expected. The packet receive routine has an intended violation against the mbuf cluster allocation policy. The unnecessarily allocated clusters are freed within short lifetime, and it will not affect long term kernel memory usage. .Pp Although XNS and IPX support is included in the driver, it has never been tested and it is expected to have a lot of bugs. diff --git a/share/man/man4/man4.i386/ie.4 b/share/man/man4/man4.i386/ie.4 index 4508876a4f58..0d82e3056250 100644 --- a/share/man/man4/man4.i386/ie.4 +++ b/share/man/man4/man4.i386/ie.4 @@ -1,145 +1,145 @@ .\" .\" Copyright (c) 1994, Wilko Bulte .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt IE 4 i386 .Os .Sh NAME .Nm ie .Nd "Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration -file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device ie" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_ie_load="YES" .Ed .Pp In .Pa /boot/device.hints : .Cd hint.ie.0.at="isa" .Cd hint.ie.0.port="0x300" .Cd hint.ie.0.irq="5" .Cd hint.ie.0.maddr="0xd0000" .Sh HARDWARE The .Nm driver provides supports the following 8 and 16bit ISA Ethernet cards that are based on the Intel i82586 chip: .Pp .Bl -bullet -compact .It 3COM 3C507 .It AT&T EN100 .It AT&T Starlan 10 .It AT&T Starlan Fiber .It Intel EtherExpress 16 .It RACAL Interlan NI5210 .El .Sh DIAGNOSTICS .Bl -diag .It "ie%d: unknown board type code %d" An i82586 chip was found, but the driver was unable to determine the actual board type during the probe. .It "ie%d: kernel configured maddr %x doesn't match board configured maddr %x" The device probe detected a different maddr than the one specified in the kernel configuration file. .It "ie%d: can't find shared memory" The device probe could not access the shared memory to determine its size. .It "ie%d: kernel configured msize %d doesn't match board configured msize %d" The device probe found a different size for the shared memory than the one specified in the kernel configuration file. .It "ie%d: kernel configured irq %d doesn't match board configured irq %d" The device probe detected that the board is configured for a different interrupt than the one specified in the kernel configuration file. .It "ie%d: reset" The Intel i82586 had to be reset by the driver. .It "ie%d: transceiver problem" The driver has detected a problem with the Ethernet transceiver. This is usually due to a loose or broken transceiver cable when using an external transceiver. When you experience this problem with an on-card transceiver your card may be incorrectly jumpered for to use an external transceiver. Worst case your on-board transceiver may be broken. .It "ie%d: TDR detected an open %d clocks away" The driver detected an open circuit in the Ethernet cable. Check your coax cable and terminator resistors. .It "ie%d: TDR detected a short %d clocks away" The driver detected a short circuit in the Ethernet cable. Check your coax cable and terminator resistors. .It "ie%d: TDR returned unknown status %x" The driver got an unknown status from the card during the Ethernet cable test. .It "ie%d: multicast address setup command failed" The card could not be put into multicast mode. .It "ie%d: configure command failed" The card refused to respond correctly during configuration. .It "ie%d: individual address setup command failed" The programming of the Ethernet (MAC) address failed. .El .Sh CAVEATS The Racal Interlan NI5210 comes in variants with 8 and 16 kbytes of shared memory. It is strongly advisable to use the 16 kbyte variant. You can upgrade your 8 kbyte card to 16 kbyte by adding an additional RAM chip. .Sh SEE ALSO .Xr arp 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh AUTHORS .An -nosplit The .Nm device driver was written by .An Garrett A. Wollman , based on code by .An William F. Jolitz and Lawrence Berkeley Laboratories. .Tn 3C507 support was written by .An Charles M. Hannum . This manual page was written by .An Wilko C. Bulte . diff --git a/share/man/man4/man4.i386/lnc.4 b/share/man/man4/man4.i386/lnc.4 index a996910a24d4..8e3c15052767 100644 --- a/share/man/man4/man4.i386/lnc.4 +++ b/share/man/man4/man4.i386/lnc.4 @@ -1,170 +1,170 @@ .\" .\" Copyright (c) 1997 David E. O'Brien .\" .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. .\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT, .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt LNC 4 i386 .Os .Sh NAME .Nm lnc .Nd "AMD Lance/PCnet Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration -file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device lnc" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_lnc_load="YES" .Ed .Pp In .Pa /boot/device.hints : .Cd hint.lnc.0.at="isa" .Cd hint.lnc.0.port="0x280" .Cd hint.lnc.0.irq="10" .Cd hint.lnc.0.drq="0" .Sh DESCRIPTION The .Nm driver provides support for the AMD family of Lance/PCnet Ethernet NICs including the Am7990 and Am79C960. .Sh HARDWARE The .Nm driver supports the following adapters: .Pp .Bl -bullet -compact .It Novell NE2100 .It Novell NE32-VL .It Isolan AT 4141-0 (16 bit) .It Isolan BICC .It Isolink 4110 (8 bit) .It Diamond HomeFree .It Digital DEPCA .It Hewlett Packard Vectra 486/66XM .It Hewlett Packard Vectra XU .El .Pp Also supported are adapters working with the .Xr pcn 4 driver. The .Nm driver runs these in compatibility mode, thus the .Xr pcn 4 driver should be preferred. .Sh DIAGNOSTICS .Bl -diag .It "lnc%d: Framing error" A framing error occurred. This means a CRC error also occurred. This caused the driver to drop the packet that contained the framing error. .It "lnc%d: Receive CRC error The received Ethernet frame failed the CRC checksum. This caused the driver to drop the packet that failed the checksum. .It "lnc%d: Packet dropped, no mbufs" The driver ran out of mbuf's. This may suggest a resource problem. .It "lnc%d: Couldn't allocate memory for NIC" This is a fatal error. The driver will not attach to the card under this circumstance. .It "lnc%d: Memory allocated above 16Mb limit" ISA and ESIA cards require bounce buffers for DMA transfers above 16mb. The Am7990 and Am79C960 only have 24 address lines and so can only access the lower 16Mb of physical memory. The .Nm driver assumes the memory it allocates is within the lower 16Mb range. This is not a very valid assumption but there is nothing that can be done about it yet. For shared memory NICs this is not relevant. .It "lnc%d: Device timeout -- Resetting" The device has stopped responding to the network, or there is a problem with the network connection (cable). Make sure the network connection in use is the same one the card is configured for. .It "lnc%d: Transmit late collision -- Net error?" .It "lnc%d: Loss of carrier during transmit -- Net error?" .It "lnc%d: Transmit of packet failed after 16 attempts -- TDR = %d" .It "lnc%d: Heartbeat error -- SQE test failed" .It "lnc%d: Babble error - more than 1519 bytes transmitted" .It "lnc%d: Missed packet -- no receive buffer" .It "lnc%d: Memory error -- Resetting" .It "lnc%d: Couldn't get mbuf for transmit packet -- Resetting" .It "lnc%d: Receive buffer error" .It "lnc%d: Receive overflow error" .It "lnc%d: Receive interrupt with buffer still owned by controller -- Resetting" .It "lnc%d: Receive interrupt but not start of packet -- Resetting" .It "lnc%d: Start of packet found before end of previous in receive ring -- Resetting" .It "lnc%d: End of received packet not found -- Resetting" .It "lnc%d: Transmit interrupt with buffer still owned by controller -- Resetting" .It "lnc%d: Transmit interrupt but not start of packet -- Resetting" .It "lnc%d: Start of packet found before end of previous in transmit ring -- Resetting" .It "lnc%d: End of transmitted packet not found -- Resetting" .It "lnc%d: Transmit buffer error -- Resetting" .It "lnc%d: Transmit underflow error -- Resetting" .El .Sh SEE ALSO .Xr arp 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 2.2 . .Sh AUTHORS .An -nosplit The .Nm device driver was written by .An Paul Richards . Support for the AMD PCHome phone-line based network added by .An Robert Watson . This manual page was written by .An David E. O'Brien . .Sh BUGS This driver has the potential of being the most verbose of any of the Ethernet device drivers. diff --git a/share/man/man4/man4.i386/ray.4 b/share/man/man4/man4.i386/ray.4 index 90863b3179f9..99a570bd996a 100644 --- a/share/man/man4/man4.i386/ray.4 +++ b/share/man/man4/man4.i386/ray.4 @@ -1,420 +1,421 @@ .\" .\" Copyright (C) 2000 .\" Dr. Duncan McLennan Barclay, dmlb@ragnet.demon.co.uk. .\" .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY DUNCAN BARCLAY AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL DUNCAN BARCLAY OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt RAY 4 i386 .Os .Sh NAME .Nm ray .Nd "Raytheon Raylink/Webgear Aviator PCCard driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device ray" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_ray_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for .Tn "Raytheon Raylink" adapters (commonly available as .Tn "Webgear Aviator" , .Tn "Webgear Aviator Pro" and .Tn "Raylink PC Card" devices.) The core of the .Tn Raylink cards is a frequency hopping PHY with an .Tn IEEE 802.11 style MAC that interacts with the host using shared memory and mailboxes. .Pp The .Nm driver currently supports ad-hoc operation mode and the .Tn Aviator cards. Infrastructure mode, interworking with .Tn "Windows 2000" Ns / Ns Tn Linux Ns / Ns Nx , .Tn "Raylink PC Cards" and .Tn "Aviator Pros" is rudimentary and in active development. The .Nm driver currently encapsulates all IP and ARP traffic as .Tn Ethernet 2 frames within an .Tn IEEE 802.11 frame. Other translations will be forthcoming as needed. Transmit speed is selectable between 0.5Mbps, 1Mbp , 1.5Mbps or 2Mbps all with auto fallback. .Pp By default, the .Nm driver configures the card for ad-hoc operation. In this mode, stations can communicate amongst each other without the aid of an access point. To join a managed service set, the driver must be set for infrastructure mode using the .Xr raycontrol 8 utility. .Pp There are two known firmware versions; version 4 and version 5. Version 4 firmware was shipped on the orignal .Tn "Webgear Aviators" Version 5 firmware is used as part of the .Tn "Windows 2000" upgrade from .Tn Webgear and on the .Tn "Aviator Pro" , and .Tn "Raylink PC Cards" cards. Version 4 is not likely to be 100% .Tn IEEE 802.11 compliant - version 5 should be. .Pp For more information on configuring this device, see .Xr ifconfig 8 and .Xr raycontrol 8 . .Sh DIAGNOSTICS The following messages occur when there are problems setting up the memory mapped buffers due to nits in .Xr pccardd 8 . .Bl -diag .It "ray?: pccardd did not map CM - giving up" See the .Sx BUGS section and contact the author for help enclosing a copy of the output from .Xr dmesg 8 . This message only occurs on 3.x systems. .It "ray?: fixing up CM ..." .It "ray?: fixing up AM ..." The driver is fixing up PCCard memory management after mis-configuration by .Xr pccardd 8 , benign. .El .Pp .Bl -diag On 4.x and -current systems the following messages can occur when the memory mapped buffers are set up. .It "ray?: allocated common memory:" .It ". start 0xd0000 count 0xc0000 flags 0x40" Benign. .It "ray?: allocated attribute memory:" .It ". start 0xdc000 count 0x1000 flags 0x50" Benign. .It "ray?: allocated irq:" .It ". start 0x9 count 0x1" Benign. .It "ray?: Cannot allocate attribute memory" .It "ray?: Cannot allocate common memory" .It "ray?: Cannot allocate irq" .It "ray?: Failed to setup irq" .It "ray?: CARD_SET_MEMORY_OFFSET returned 0x??" .It "ray?: CARD_SET_RES_FLAGS returned 0x??" See the .Sx BUGS section and contact the author for help enclosing a copy of the output from .Xr dmesg 8 in your email. .El .Pp .Bl -diag If the kernel is booted with the verbose flag turned on then the extra information is printed when the driver is probed. These messages are also seen when the .Dv RAY_DBG_BOOTPARAM bit in the .Dv RAY_DEBUG option is turned on, as is the case for all existing versions of the driver. .It "ray?: memory start 0x???? count 0x???? flags 0x???? offset 0x????" Description of memory map settings on entry to the driver. .It "ray?: irq start 0x???? count 0x????" Description of irq settings on entry to the driver (only on 4.1 and above). .El .Pp On start-up the driver will report hardware failures thus: .Bl -diag .It "ray?: card failed self test: status 0x??" The card failed to come ready after it was plugged in to the PCCard slot. The most common cause of this message is incorrect PCCard memory management (indicated by a status of 0xff or 0x55). Bent cards might say that the receiver calibration failed. If you are brave enough removing the base of the case can resurrect cards (no warranties etc.). .It "ray?: unsupported firmware version 0x??" Self explanatory. Contact the author for help enclosing a copy of the output from .Xr dmesg 8 . .El .Pp The following messages are enabled using the .Cm debug option of .Xr ifconfig 8 . .Bl -diag .It "ray?: cannot transmit - not running" A packet was ready for transmission but the NIC is not connected to a BSS. May occur when removing the PCCard. .It "ray?: cannot transmit - no network" The wireless NIC has roamed from an access point and not connected with a new one yet. .It "ray?: cannot transmit - ECF busy" The controller firmware was busy when a packet was about to be sent out. It will be retried automatically. .It "ray?: mbuf too long ??" Should never happen, and if it does represents something wrong in the generic Ethernet driver in the kernel. .It "ray?: could not pullup ether" Problem with re-aligning mbufs. Very unlikely to happen. .It "ray?: unknown framing type ??" An impossible error - mail the author. .It "ray?: could not translate packet" An error occurred when trying to re-frame a packet for transmission. .It "ray?: ECF busy, dropping packet" The NIC was busy just before a packet was to be transmitted. .It "ray?: tx completed but status is fail" Typically associated with transmissions to out of range NICs. .It "ray?: packet too big or too small" A received packet was impossibly small or too large to fit into an mbuf. .It "ray?: MGETHDR failed" The driver could not get a mbuf to store a received packet into. Try increasing .Dv MAXUSERS in your kernel configuration. .It "ray?: MCLGET failed" The driver could not get a mbuf to store a received packet into. Try increasing .Dv MAXUSERS in your kernel configuration. .It "ray?: bad length current 0x?? pktlen 0x??" The lengths of a fragmented packet were inconsistent. .It "ray?: bad rcs index 0x??" The index of the buffer used for part of a fragmented packet is outside of the usable range. .It "ray?: header not version 0 fc0 0x??" The received .Tn IEEE 802.11 packet had an unknown header type. Represents link corruption or non standard nodes in the network. .It "ray?: unknown packet fc0 0x??" The received .Tn IEEE 802.11 packet type is unknown. Represents link corruption or non standard nodes in the network. .It "ray?: reserved DATA packet subtype 0x??" The received .Tn IEEE 802.11 data packet has a reserved (i.e., not allowed) subtype. Represents link corruption or non standard nodes in the network. .It "ray?: MGT TODS/FROMDS wrong fc1 0x??" The received .Tn IEEE 802.11 management packet had a malformed header. Represents link corruption or non standard nodes in the network. .It "ray?: unexpected MGT packet subtype 0x??" The received .Tn IEEE 802.11 management packet was of a subtype that the NIC should have processed. Benign, but might represent buggy firmware. .It "ray?: reserved MGT packet subtype 0x??" The received .Tn IEEE 802.11 management packet has a reserved (i.e., not allowed) subtype. Represents link corruption or non standard nodes in the network. .It "ray?: open system authentication request" Self explanatory and for testing .Tn "Aviator Pro" interworking. .It "ray?: authentication failed with status ??" Self explanatory and currently represents a bug as the driver never requests authentication. .It "ray?: shared key authentication request" Self explanatory and for testing .Tn "Aviator Pro" interworking. .It "ray?: reserved authentication subtype 0x??" An authentication request has been received for a reserved (i.e., not allowed) subtype. Represents link corruption or non standard nodes in the network. .It "ray?: CTL TODS/FROMDS wrong fc1 0x??" The received .Tn IEEE 802.11 management packet had a malformed header. Represents link corruption or non standard nodes in the network. .It "ray?: unexpected CTL packet subtype 0x??" The received .Tn IEEE 802.11 control packet was of a subtype that the NIC should have processed. Benign, but might represent buggy firmware. .It "ray?: reserved CTL packet subtype 0x??" The received .Tn IEEE 802.11 control packet has a reserved (i.e., not allowed) subtype. Represents link corruption or non standard nodes in the network. .It "ray?: bad ccs index 0x??" The NIC has generated an interrupt with an incorrect control block. .It "ray?: unexpected UPDATE_APM" .It "ray?: unexpected TEST_MEM" .It "ray?: unexpected SHUTDOWN" .It "ray?: unexpected DUMP_MEM" .It "ray?: unexpected START_TIMER" The NIC has generated an interrupt signalling that the indicated command has completed. At present these commands are never issued by the driver, so they represent firmware/hardware/driver bugs. .It "ray?: unknown command 0x??" The NIC has generated an interrupt for an unknown command completion. Represents firmware/hardware/driver bugs. .It "ray?: unexpected JAPAN_CALL_SIGNAL" The NIC has generated an interrupt with a control block requesting processing of a packet that is only ever used in Japanese RCR certification tests. Represents firmware/hardware/driver bugs unless you are trying to certify the NICs in Japan (in which case you would have to of modified the driver and this manual is out of date). .It "ray?: spinning" The controller firmware was busy when a command was about to be issued. If the driver spins for too long then it will panic. See the .Sx BUGS section for details. .It "ray?: freeing free ccs 0x??" Benign warning that may occur when the NIC is ejected. .El .Sh SEE ALSO .Xr arp 4 , .Xr netintro 4 , .Xr ifconfig 8 , .Xr pccardd 8 , .Xr raycontrol 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 3.3 . .Sh AUTHORS .An -nosplit Early versions of this .Nm driver were a port of the .Nx driver by .An "Christian E. Hopps" . The driver was re-structured by .An Duncan Barclay Aq dmlb@FreeBSD.org , so that .Xr dhclient 8 would work. .Sh BUGS Infra-structure mode is not supported yet. The driver is likely to panic if it is set into this mode. Testers are encouraged to contact the author. .Pp Currently .Fx has a small problem managing and setting up the correct memory maps. However, this driver should reset the memory maps correctly - it works around .Xr pccardd 8 (where it reads the CIS for common memory, sets it all up and then throws it all away assuming the card is an .Xr ed 4 driver...). Note that this could be dangerous (because it does not interact with .Xr pccardd 8 ) if you use other memory mapped cards at the same time or have SCSI cards with on-board BIOS. .Pp More encapsulations and translations could be supported, but they have little value unless someone can demonstrate that the .Nm cards will communicate with other manufacturers cards. Version 4 and firmware is not .Tn IEEE 802.11 compliant, but version 5 is. .Pp To communicate with .Tn Windows machines ensure that the .Tn Windows machine creates the BSS/IBSS. .Pp The driver currently panics on some errors that it should recover from. These will be removed RSN. diff --git a/share/man/man4/man4.i386/vx.4 b/share/man/man4/man4.i386/vx.4 index 12f4f70e8077..b9bb87e122fe 100644 --- a/share/man/man4/man4.i386/vx.4 +++ b/share/man/man4/man4.i386/vx.4 @@ -1,141 +1,142 @@ .\" .\" Copyright (c) 1996, Fred Gray .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by David Greenman. .\" 4. The name of the author may not be used to endorse or promote products .\" derived from this software without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt VX 4 i386 .Os .Sh NAME .Nm vx .Nd "3Com EtherLink III / Fast EtherLink III (3c59x) Ethernet driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following liness in your kernel configuration file: +driver into your kernel, place the following liness in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device vx" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_vx_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for the 3Com .Dq Vortex chipset. .Pp The medium selection can be influenced by the following link flags to the .Xr ifconfig 8 command: .Pp .Bl -tag -width LINK0X -compact .It Em link0 Use the AUI port. .It Em link1 Use the BNC port. .It Em link2 Use the UTP port. .El .Sh HARDWARE The .Nm driver supports the following cards: .Pp .Bl -bullet -compact .It 3Com 3c590 EtherLink III PCI .It 3Com 3c592 EtherLink III EISA .It 3Com 3c595 Fast EtherLink III PCI in 10 Mbps mode .It 3Com 3c597 Fast EtherLink III EISA in 10 Mbps mode .El .Sh DIAGNOSTICS .Bl -diag .It "vx%d: not configured; kernel is built for only %d devices." There are not enough devices in the kernel configuration file for the number of adapters present in the system. Add devices to the configuration file, rebuild the kernel, and reboot. .El .Pp All other diagnostics indicate either a hardware problem or a bug in the driver. .Sh CAVEATS Some early-revision 3c590 cards are defective and suffer from many receive overruns, which cause lost packets. The author has attempted to implement a test for it based on the information supplied by 3Com, but the test resulted mostly in spurious warnings. .Pp The performance of this driver is somewhat limited by the fact that it uses only polled-mode I/O and does not make use of the bus-mastering capability of the cards. .Sh SEE ALSO .Xr arp 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 2.1 . It was derived from the .Nm ep driver, from which it inherits most of its limitations. .Sh AUTHORS .An -nosplit The .Nm device driver and this manual page were written by .An Fred Gray Aq fgray@rice.edu , based on the work of .An Herb Peyerl and with the assistance of numerous others. .Sh BUGS The .Nm driver is known not to reset the adapter correctly following a warm boot on some systems. .Pp The .Nm driver has not been exhaustively tested with all the models of cards that it claims to support. diff --git a/share/man/man4/my.4 b/share/man/man4/my.4 index 0854627f9f75..c8e12e8cf9c4 100644 --- a/share/man/man4/my.4 +++ b/share/man/man4/my.4 @@ -1,93 +1,93 @@ .\" Copyright (c) 2003 Hiten M. Pandya .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHORS AND ITS AND CONTRIBUTORS .\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR THE CONTRIBUTORS .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt MY 4 .Os .Sh NAME .Nm my .Nd "Myson Technology Ethernet PCI driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration -file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device my" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_my_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for various NICs based on the Myson chipset. The Myson chipset is a variant of the DEC Tulip NIC chipset. .Pp The driver will work with almost any MII-compliant PHY, thus failure to positively identify the chip is not a fatal error. .Sh HARDWARE The .Nm driver provides support for various NICs based on the Myson chipset. Supported models include: .Pp .Bl -bullet -compact .It Myson MTD800 PCI Fast Ethernet chip .It Myson MTD803 PCI Fast Ethernet chip .It Myson MTD89X PCI Gigabit Ethernet chip .El .Sh SEE ALSO .Xr de 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr pci 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm driver first appeared in .Fx 4.6 . .Sh AUTHORS The .Nm driver was written by Myson Technology Inc. .Pp This manual page was written by .An Hiten M. Pandya Aq hmp@FreeBSD.org . .Sh BUGS The .Nm driver does not support Power Management Events (PME). diff --git a/share/man/man4/nge.4 b/share/man/man4/nge.4 index 1cae1858e98d..d7e18db15c81 100644 --- a/share/man/man4/nge.4 +++ b/share/man/man4/nge.4 @@ -1,233 +1,234 @@ .\" Copyright (c) 2001 Wind River Systems .\" Copyright (c) 1997, 1998, 1999, 2000, 2001 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt NGE 4 .Os .Sh NAME .Nm nge .Nd "National Semiconductor PCI Gigabit Ethernet adapter driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device nge" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_nge_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for various NICs based on the National Semiconductor DP83820 and DP83821 Gigabit Ethernet controller chips. .Pp The DP83820 supports TBI (ten bit interface) and GMII transceivers, which means it can be used with either copper or 1000baseX fiber applications. The DP83820 supports TCP/IP checksum offload and VLAN tagging/insertion as well as a 2048-bit multicast hash filter and up to 4 pattern match buffers. .Pp Most cards also use the DP83861 10/100/1000 copper gigabit transceiver chip, which supports autonegotiation of 10, 100 and 1000Mbps modes in full or half duplex. .Pp The DP83820 also supports jumbo frames, which can be configured via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the .Xr ifconfig 8 utility configures the adapter to receive and transmit jumbo frames. Using jumbo frames can greatly improve performance for certain tasks, such as file transfers and data streaming. .Pp The .Nm driver supports the following media types: .Bl -tag -width 10baseTXUTP .It Cm autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to .Xr rc.conf 5 . .It Cm 10baseT/UTP Set 10Mbps operation. The .Xr ifconfig 8 .Ic mediaopt option can also be used to select either .Cm full-duplex or .Cm half-duplex modes. .It Cm 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Xr ifconfig 8 .Ic mediaopt option can also be used to select either .Cm full-duplex or .Cm half-duplex modes. .It Cm 1000baseTX Set 1000baseTX operation over twisted pair. .Cm full-duplex and .Cm half-duplex modes are supported. .It Cm 1000baseSX Set 1000Mbps (Gigabit Ethernet) operation. Both .Cm full-duplex and .Cm half-duplex modes are supported. .El .Pp The .Nm driver supports the following media options: .Bl -tag -width full-duplex .It Cm full-duplex Force full duplex operation. .It Cm half-duplex Force half duplex operation. .El .Pp The .Nm driver also supports one special link option for 1000baseTX cards: .Bl -tag -width link0 .It Cm link0 With 1000baseTX cards, establishing a link between two ports requires that one port be configured as a master and the other a slave. With autonegotiation, the master/slave settings will be chosen automatically. However when manually selecting the link state, it is necessary to force one side of the link to be a master and the other a slave. The .Nm driver configures the ports as slaves by default. Setting the .Cm link0 flag with .Xr ifconfig 8 will set a port as a master instead. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports National Semiconductor DP83820 and DP83821 based Gigabit Ethernet adapters including: .Pp .Bl -bullet -compact .It SMC EZ Card 1000 (SMC9462TX) .It D-Link DGE-500T .It Asante FriendlyNet GigaNIX 1000TA and 1000TPC .It Addtron AEG320T .It LinkSys EG1032 (32-bit PCI) and EG1064 (64-bit PCI) .It Surecom Technology EP-320G-TX .It Netgear GA622T .It Netgear GA621 .It Ark PC SOHO-GA2500T (32-bit PCI) and SOHO-GA2000T (64-bit PCI) .It Trendware TEG-PCITX (32-bit PCI) and TEG-PCITX2 (64-bit PCI) .El .Sh DIAGNOSTICS .Bl -diag .It "nge%d: couldn't map memory" A fatal initialization error has occurred. .It "nge%d: couldn't map ports" A fatal initialization error has occurred. .It "nge%d: couldn't map interrupt" A fatal initialization error has occurred. .It "nge%d: no memory for softc struct!" The driver failed to allocate memory for per-device instance information during initialization. .It "nge%d: failed to enable memory mapping!" The driver failed to initialize PCI shared memory mapping. This might happen if the card is not in a bus-master slot. .It "nge%d: no memory for jumbo buffers!" The driver failed to allocate memory for jumbo frames during initialization. .It "nge%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr polling 4 , .Xr vlan 4 , .Xr ifconfig 8 .Rs .%T National Semiconductor DP83820 datasheet .%O http://www.national.com .Re .Rs .%T National Semiconductor DP83861 datasheet .%O http://www.national.com .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 4.4 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@bsdi.com . diff --git a/share/man/man4/nve.4 b/share/man/man4/nve.4 index 7c416e8ac6cc..07478bbd35c1 100644 --- a/share/man/man4/nve.4 +++ b/share/man/man4/nve.4 @@ -1,130 +1,131 @@ .\" Copyright (c) 2003 Quinton Dolan .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $Id: nvnet.4,v 1.1 2003/10/09 16:48:01 q Exp $ .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt NVE 4 .Os .Sh NAME .Nm nve .Nd "NVIDIA nForce MCP Networking Adapter device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device nve" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_nve_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for the NVIDIA nForce MCP and nForce2 MCP2 networking adapter that is embedded in the southbridge of most nForce and nForce2 motherboards. .Pp This driver is a reimplementation of the NVIDIA supported Linux .Nm nvnet driver and uses the same closed source API library to access the underlying hardware. There is currently no programming documentation available for this device, and therefore little is known about the internal architecture of the MAC engine itself. .Pp The .Nm driver supports the following media types: .Bl -tag -width ".Cm 10baseT/UTP" .It Cm autoselect Enable autoselection of the media type and options. .It Cm 10baseT/UTP Set 10Mbps operation. .It Cm 100baseTX Set 100Mbps (Fast Ethernet) operation. .El .Pp The .Nm driver supports the following media options: .Bl -tag -width ".Cm 10baseT/UTP" .It Cm full-duplex Set full duplex operation. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports the NVIDIA MCP onboard adapters of mainboards with the following chipsets: .Pp .Bl -bullet -compact .It nForce .It nForce2 .El .Sh DIAGNOSTICS .Bl -diag .It "nve%d: couldn't map memory" A fatal initialization error has occurred. .It "nve%d: couldn't map interrupt" A fatal initialization error has occurred. .It "nve%d: failed to allocate memory" There are not enough mbufs available for allocation. .It "nve%d: device timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm driver first appeared in .Fx 5.5 . .Sh AUTHORS .An -nosplit The .Nm driver was written by .An Quinton Dolan Aq q@onthenet.com.au and .An "David E. O'Brien" Aq obrien@FreeBSD.org . diff --git a/share/man/man4/pcn.4 b/share/man/man4/pcn.4 index cc8649ccc3d4..87220e036ef4 100644 --- a/share/man/man4/pcn.4 +++ b/share/man/man4/pcn.4 @@ -1,202 +1,203 @@ .\" Copyright (c) Berkeley Software Design, Inc. .\" Copyright (c) 1997, 1998, 1999, 2000 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt PCN 4 .Os .Sh NAME .Nm pcn .Nd "AMD PCnet/PCI Fast Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device pcn" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_pcn_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for PCI Ethernet adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO and PCnet/Home Ethernet controller chips. Supported NIC's include the Allied Telesyn AT-2700 familly. .Pp The PCnet/PCI chips include a 100Mbps Ethernet MAC and support both a serial and MII-compliant transceiver interface. They use a bus master DMA and a scatter/gather descriptor scheme. The AMD chips provide a mechanism for zero-copy receive, providing good performance in server environments. Receive address filtering is provided using a single perfect filter entry for the station address and a 64-bit multicast hash table. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width 10baseTXUTP .It autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to .Xr rc.conf 5 . .It 10baseT/UTP Set 10Mbps operation. The .Xr ifconfig 8 .Cm mediaopt option can also be used to select either .Sq full-duplex or .Sq half-duplex modes. .It 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Xr ifconfig 8 .Cm mediaopt option can also be used to select either .Sq full-duplex or .Sq half-duplex modes. .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width full-duplex .It full-duplex Force full duplex operation .It half-duplex Force half duplex operation. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO and PCnet/Home Fast Ethernet chips: .Pp .Bl -bullet -compact .It AMD Am53C974/Am79C970/Am79C974 PCnet-PCI .It AMD Am79C970A PCnet-PCI II .It AMD Am79C971 PCnet-FAST .It AMD Am79C972 PCnet-FAST+ .It AMD Am79C973/Am79C975 PCnet-FAST III .It AMD Am79C976 PCnet-PRO .It AMD PCnet/Home HomePNA .It Allied-Telesis LA-PCI .It Contec C-NET(98)S (PC-98) .It NEC SV-98/2-B05, B06 .El .Sh DIAGNOSTICS .Bl -diag .It "pcn%d: couldn't map ports/memory" A fatal initialization error has occurred. .It "pcn%d: couldn't map interrupt" A fatal initialization error has occurred. .It "pcn%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (e.g.\& a cable fault). .It "pcn%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .It "pcn%d: no memory for tx list" The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. .It "pcn%d: chip is in D3 power state -- setting to D0" This message applies only to adapters which support power management. Some operating systems place the controller in low power mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. If you see this message at boot time and the driver fails to attach the device as a network interface, you will have to perform a warm boot to have the device properly configured. .Pp Note that this condition only occurs when warm booting from another operating system. If you power down your system prior to booting .Fx , the card should be configured correctly. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Rs .%T AMD PCnet/FAST, PCnet/FAST+ and PCnet/Home datasheets .%O http://www.amd.com .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 4.3 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@osd.bsdi.com . diff --git a/share/man/man4/ral.4 b/share/man/man4/ral.4 index 7556bf7c6ea8..06f6c5646a5e 100644 --- a/share/man/man4/ral.4 +++ b/share/man/man4/ral.4 @@ -1,195 +1,196 @@ .\" Copyright (c) 2005 .\" Damien Bergamini .\" .\" Permission to use, copy, modify, and distribute this software for any .\" purpose with or without fee is hereby granted, provided that the above .\" copyright notice and this permission notice appear in all copies. .\" .\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES .\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR .\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Os .Dt RAL 4 .Sh NAME .Nm ral .Nd "Ralink Technology RT2500 IEEE 802.11 driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device ral" .Cd "device wlan" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_ral_load="YES" .Ed .Sh DESCRIPTION The .Nm driver supports PCI/CardBus wireless adapters based on the Ralink RT2500 chipset. .Pp The RT2500 chipset consists of two integrated chips, a RT2560 MAC/BBP and a radio transceiver (the model of which depends on the card revision). .Pp The RT2522, RT2523, RT2524, RT2525, RT2525e and RT2526 radio transceivers operate in the 2.4GHz band (802.11b/g) whereas the RT5222 is a dual-band radio transceiver that can operate in the 2.4GHz and 5.2GHz bands (802.11a). .Pp The transmit speed is user-selectable or can be adapted automatically by the driver depending on the received-signal strength. .Sh HARDWARE The following adapters should work: .Pp .Bl -column -compact ".Li Atlantis Land A02-PCM-W54" "Bus" .It Em Card Ta Em Bus .It Li "A-Link WL54H" Ta PCI .It Li "A-Link WL54PC" Ta CardBus .It Li "Amigo AWI-914W" Ta CardBus .It Li "Amigo AWI-922W" Ta mini-PCI .It Li "Amigo AWI-926W" Ta PCI .It Li "AMIT WL531C" Ta CardBus .It Li "AMIT WL531P" Ta PCI .It Li "AOpen AOI-831" Ta PCI .It Li "ASUS WL-107G" Ta CardBus .It Li "ASUS WL-130g" Ta PCI .It Li "Atlantis Land A02-PCI-W54" Ta PCI .It Li "Atlantis Land A02-PCM-W54" Ta CardBus .It Li "Belkin F5D7000 v3" Ta PCI .It Li "Belkin F5D7010 v2" Ta CardBus .It Li "Billionton MIWLGRL" Ta mini-PCI .It Li "Canyon CN-WF511" Ta PCI .It Li "Canyon CN-WF513" Ta CardBus .It Li "CC&C WL-2102" Ta CardBus .It Li "CNet CWC-854" Ta CardBus .It Li "CNet CWP-854" Ta PCI .It Li "Compex WL54G" Ta CardBus .It Li "Compex WLP54G" Ta PCI .It Li "Conceptronic C54RC" Ta CardBus .It Li "Conceptronic C54Ri" Ta PCI .It Li "Digitus DN-7001G-RA" Ta CardBus .It Li "Digitus DN-7006G-RA" Ta PCI .It Li "E-Tech WGPC02" Ta CardBus .It Li "E-Tech WGPI02" Ta PCI .It Li "Edimax EW-7108PCg" Ta CardBus .It Li "Edimax EW-7128g" Ta PCI .It Li "Eminent EM3036" Ta CardBus .It Li "Eminent EM3037" Ta PCI .It Li "Encore ENLWI-G-RLAM" Ta PCI .It Li "Encore ENPWI-G-RLAM" Ta CardBus .It Li "Fiberline WL-400P" Ta PCI .It Li "Fibreline WL-400X" Ta CardBus .It Li "Gigabyte GN-WIKG" Ta mini-PCI .It Li "Gigabyte GN-WMKG" Ta CardBus .It Li "Gigabyte GN-WPKG" Ta PCI .It Li "Hawking HWC54GR" Ta CardBus .It Li "Hawking HWP54GR" Ta PCI .It Li "iNexQ CR054g-009 (R03)" Ta PCI .It Li "JAHT WN-4054P" Ta CardBus .It Li "JAHT WN-4054PCI" Ta PCI .It Li "LevelOne WNC-0301 v2" Ta PCI .It Li "LevelOne WPC-0301 v2" Ta CardBus .It Li "Linksys WMP54G v4" Ta PCI .It Li "Micronet SP906GK" Ta PCI .It Li "Micronet SP908GK V3" Ta CardBus .It Li "Minitar MN54GCB-R" Ta CardBus .It Li "Minitar MN54GPC-R" Ta PCI .It Li "MSI CB54G2" Ta CardBus .It Li "MSI MP54G2" Ta mini-PCI .It Li "MSI PC54G2" Ta PCI .It Li "OvisLink EVO-W54PCI" Ta PCI .It Li "PheeNet HWL-PCIG/RA" Ta PCI .It Li "Pro-Nets CB80211G" Ta CardBus .It Li "Pro-Nets PC80211G" Ta PCI .It Li "Repotec RP-WB7108" Ta CardBus .It Li "Repotec RP-WP0854" Ta PCI .It Li "SATech SN-54C" Ta CardBus .It Li "SATech SN-54P" Ta PCI .It Li "Sitecom WL-112" Ta CardBus .It Li "Sitecom WL-115" Ta PCI .It Li "SparkLAN WL-685R" Ta CardBus .It Li "Surecom EP-9321-g" Ta PCI .It Li "Surecom EP-9321-g1" Ta PCI .It Li "Surecom EP-9428-g" Ta CardBus .It Li "Sweex LC500050" Ta CardBus .It Li "Sweex LC700030" Ta PCI .It Li "TekComm NE-9321-g" Ta PCI .It Li "TekComm NE-9428-g" Ta CardBus .It Li "Unex CR054g-R02" Ta PCI .It Li "Unex MR054g-R02" Ta CardBus .It Li "Zinwell ZWX-G160" Ta CardBus .It Li "Zinwell ZWX-G360" Ta mini-PCI .It Li "Zinwell ZWX-G361" Ta PCI .It Li "Zonet ZEW1500" Ta CardBus .It Li "Zonet ZEW1600" Ta PCI .El .Pp An up to date list can be found at .Pa http://damien.bergamini.free.fr/ral/list.html . .Sh EXAMPLES Join an existing BSS network (i.e., connect to an access point): .Pp .Dl "ifconfig ral0 inet 192.168.0.20 netmask 0xffffff00" .Pp Join a specific BSS network with network name .Dq Li my_net : .Pp .Dl "ifconfig ral0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net" .Pp Join a specific BSS network with 40-bit WEP encryption: .Bd -literal -offset indent ifconfig ral0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e wepmode on wepkey 0x1234567890 .Ed .Pp Join a specific BSS network with 104-bit WEP encryption: .Bd -literal -offset indent ifconfig ral0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e wepmode on wepkey 0x01020304050607080910111213 .Ed .Sh DIAGNOSTICS .Bl -diag .It "ral%d: device timeout" The driver will reset the hardware. This should not happen. .El .Sh SEE ALSO .Xr arp 4 , .Xr cardbus 4 , .Xr netintro 4 , .Xr pci 4 , .Xr wlan 4 , .Xr ifconfig 8 .Rs .%T "Ralink Technology" .%O http://www.ralinktech.com/ .Re .Sh HISTORY The .Nm driver first appeared in .Ox 3.7 . .Sh CAVEATS PCI .Nm adapters seem to require a PCI 2.2 compliant motherboard and will likely not work with PCI 2.1 only motherboard. .Sh AUTHORS The .Nm driver was written by .An Damien Bergamini Aq damien@FreeBSD.org . diff --git a/share/man/man4/re.4 b/share/man/man4/re.4 index e27e846a9b7c..bfabba095394 100644 --- a/share/man/man4/re.4 +++ b/share/man/man4/re.4 @@ -1,238 +1,239 @@ .\" Copyright (c) 2003 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2004 .Dt RE 4 .Os .Sh NAME .Nm re .Nd "RealTek 8139C+/8169/8169S/8110S PCI Ethernet adapter driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device re" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_re_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for various NICs based on the RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S PCI Ethernet controllers. .Pp NICs based on the 8139C+ are capable of 10 and 100Mbps speeds over CAT5 cable. NICs based on the 8169, 8169S and 8110S are capable of 10, 100 and 1000Mbps operation. .Pp All NICs supported by the .Nm driver have TCP/IP checksum offload and hardware VLAN tagging/insertion features, and use a descriptor-based DMA mechanism. They are also capable of TCP large send (TCP segmentation offload). .Pp The 8139C+ is a single-chip solution combining both a 10/100 MAC and PHY. The 8169 is a 10/100/1000 MAC only, requiring a GMII or TBI external PHY. The 8169S and 8110S are single-chip devices containing both a 10/100/1000 MAC and 10/100/1000 copper PHY. Standalone 10/100/1000 cards are available in both 32-bit PCI and 64-bit PCI models. The 8110S is designed for embedded LAN-on-motherboard applications. .Pp The 8169, 8169S and 8110S also support jumbo frames, which can be configured via the interface MTU setting. The MTU is limited to 7422, since the chip cannot transmit larger frames. Selecting an MTU larger than 1500 bytes with the .Xr ifconfig 8 utility configures the adapter to receive and transmit jumbo frames. .Pp The .Nm driver supports the following media types: .Bl -tag -width ".Cm 10baseT/UTP" .It Cm autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to .Xr rc.conf 5 . .It Cm 10baseT/UTP Set 10Mbps operation. The .Xr ifconfig 8 .Cm mediaopt option can also be used to select either .Cm full-duplex or .Cm half-duplex modes. .It Cm 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Xr ifconfig 8 .Cm mediaopt option can also be used to select either .Cm full-duplex or .Cm half-duplex modes. .It Cm 1000baseTX Set 1000baseTX operation over twisted pair. The RealTek gigE chips support 1000Mbps in .Cm full-duplex mode only. .\" .It Cm 1000baseSX .\" Set 1000Mbps (Gigabit Ethernet) operation. .\" Both .\" .Cm full-duplex .\" and .\" .Cm half-duplex .\" modes are supported. .El .Pp The .Nm driver supports the following media options: .Bl -tag -width ".Cm full-duplex" .It Cm full-duplex Force full duplex operation. .It Cm half-duplex Force half duplex operation. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports RealTek RTL8139C+, RTL8169, RTL8169S and RTL8110S based Fast Ethernet and Gigabit Ethernet adapters including: .Pp .Bl -bullet -compact .It Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+) .It Compaq Evo N1015v Integrated Ethernet (8139C+) .It Corega CG-LAPCIGT Gigabit Ethernet (8169S) .It Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S) .It LevelOne GNC-0105T (8169S) .It PLANEX COMMUNICATIONS Inc.\& GN-1200TC (8169S) .It Xterasys XN-152 10/100/1000 NIC (8169) .El .Sh DIAGNOSTICS .Bl -diag .It "re%d: couldn't map memory" A fatal initialization error has occurred. .It "re%d: couldn't map ports" A fatal initialization error has occurred. .It "re%d: couldn't map interrupt" A fatal initialization error has occurred. .It "re%d: no memory for softc struct!" The driver failed to allocate memory for per-device instance information during initialization. .It "re%d: failed to enable memory mapping!" The driver failed to initialize PCI shared memory mapping. This might happen if the card is not in a bus-master slot. .It "re%d: no memory for jumbo buffers!" The driver failed to allocate memory for jumbo frames during initialization. .It "re%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr polling 4 , .Xr vlan 4 , .Xr ifconfig 8 .Rs .%T RealTek Semiconductor RTL8139C+, RTL8169, RTL8169S and RTL8110S datasheets .%O http://www.realtek.com.tw/ .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 5.2 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@windriver.com . .Sh BUGS The Xterasys XN-152 32-bit PCI NIC, which uses the RTL8169 MAC and Marvell 88E1000 PHY, has a defect that causes DMA corruption if the board is plugged into a 64-bit PCI slot. The defect lies in the board design, not the chip itself: the PCI REQ64# and ACK64# lines should be pulled high, but they are not. The result is that the 8169 chip is tricked into performing 64-bit DMA transfers even though a 64-bit data path between the NIC and the bus does not actually exist. .Pp Unfortunately, it is not possible to correct this problem in software, however it is possible to detect it. When the .Nm driver is loaded, it will run a diagnostic routine designed to validate DMA operation by placing the chip in digital loopback mode and initiating a packet transmission. If the card functions properly, the transmitted data will be echoed back unmodified. If the echoed data is corrupt, the driver will print an error message on the console and abort the device attach. The user should insure the NIC is installed in a 32-bit PCI slot to avoid this problem. .Pp The RealTek 8169, 8169S and 8110S chips appear to only be capable of transmitting jumbo frames up to 7.5K in size. diff --git a/share/man/man4/rl.4 b/share/man/man4/rl.4 index a676d148be5e..85ff96db703b 100644 --- a/share/man/man4/rl.4 +++ b/share/man/man4/rl.4 @@ -1,297 +1,298 @@ .\" Copyright (c) 1997, 1998 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt RL 4 .Os .Sh NAME .Nm rl .Nd "RealTek 8129/8139 Fast Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device rl" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_rl_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for PCI Ethernet adapters and embedded controllers based on the RealTek 8129 and 8139 Fast Ethernet controller chips. .Pp The RealTek 8129/8139 series controllers use bus master DMA but do not use a descriptor-based data transfer mechanism. The receiver uses a single fixed size ring buffer from which packets must be copied into mbufs. For transmission, there are only four outbound packet address registers which require all outgoing packets to be stored as contiguous buffers. Furthermore, outbound packet buffers must be longword aligned or else transmission will fail. .Pp The 8129 differs from the 8139 in that the 8139 has an internal PHY which is controlled through special direct access registers whereas the 8129 uses an external PHY via an MII bus. The 8139 supports both 10 and 100Mbps speeds in either full or half duplex. The 8129 can support the same speeds and modes given an appropriate PHY chip. .Pp Note: support for the 8139C+ chip is provided by the .Xr re 4 driver. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It autoselect Enable autoselection of the media type and options. This is only supported if the PHY chip attached to the RealTek controller supports NWAY autonegotiation. The user can manually override the autoselected mode by adding media options to the .Pa /etc/rc.conf file. .It 10baseT/UTP Set 10Mbps operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .It 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It full-duplex Force full duplex operation .It half-duplex Force half duplex operation. .El .Pp Note that the 100baseTX media type is only available if supported by the adapter. For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE Adapters supported by the .Nm driver include: .Pp .Bl -bullet -compact .It Accton .Dq Cheetah EN1207D (MPX 5030/5038; RealTek 8139 clone) .It Allied Telesyn AT2550 .It Allied Telesyn AT2500TX .It Belkin F5D5000 .It BUFFALO (Melco INC.) LPC-CB-CLX (CardBus) .It Compaq HNE-300 .It CompUSA no-name 10/100 PCI Ethernet NIC .It Corega FEther CB-TXD .It Corega FEtherII CB-TXD .It D-Link DFE-528TX .It D-Link DFE-530TX+ .It D-Link DFE-538TX .It D-Link DFE-690TXD .It Edimax EP-4103DL CardBus .It Encore ENL832-TX 10/100 M PCI .It Farallon NetLINE 10/100 PCI .It Genius GF100TXR, .It GigaFast Ethernet EE100-AXP .It KTX-9130TX 10/100 Fast Ethernet .It LevelOne FPC-0106TX .It Longshine LCS-8038TX-R .It NDC Communications NE100TX-E .It Netronix Inc.\& EA-1210 NetEther 10/100 .It Nortel Networks 10/100BaseTX .It OvisLink LEF-8129TX .It OvisLink LEF-8139TX .It Peppercon AG ROL-F .It Planex FNW-3800-TX .It SMC EZ Card 10/100 PCI 1211-TX .It SOHO (PRAGMATIC) UE-1211C .El .Sh DIAGNOSTICS .Bl -diag .It "rl%d: couldn't map memory" A fatal initialization error has occurred. .It "rl%d: couldn't map interrupt" A fatal initialization error has occurred. .It "rl%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .It "rl%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .It "rl%d: no memory for tx list" The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. .It "rl%d: chip is in D3 power state -- setting to D0" This message applies only to adapters which support power management. Some operating systems place the controller in low power mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. If you see this message at boot time and the driver fails to attach the device as a network interface, you will have to perform second warm boot to have the device properly configured. .Pp Note that this condition only occurs when warm booting from another operating system. If you power down your system prior to booting .Fx , the card should be configured correctly. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr polling 4 , .Xr ifconfig 8 .Rs .%B The RealTek 8129, 8139 and 8139C+ datasheets .%O http://www.realtek.com.tw .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 3.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ctr.columbia.edu . .Sh BUGS Since outbound packets must be longword aligned, the transmit routine has to copy an unaligned packet into an mbuf cluster buffer before transmission. The driver abuses the fact that the cluster buffer pool is allocated at system startup time in a contiguous region starting at a page boundary. Since cluster buffers are 2048 bytes, they are longword aligned by definition. The driver probably should not be depending on this characteristic. .Pp The RealTek data sheets are of especially poor quality, and there is a lot of information missing particularly concerning the receiver operation. One particularly important fact that the data sheets fail to mention relates to the way in which the chip fills in the receive buffer. When an interrupt is posted to signal that a frame has been received, it is possible that another frame might be in the process of being copied into the receive buffer while the driver is busy handling the first one. If the driver manages to finish processing the first frame before the chip is done DMAing the rest of the next frame, the driver may attempt to process the next frame in the buffer before the chip has had a chance to finish DMAing all of it. .Pp The driver can check for an incomplete frame by inspecting the frame length in the header preceding the actual packet data: an incomplete frame will have the magic length of 0xFFF0. When the driver encounters this value, it knows that it has finished processing all currently available packets. Neither this magic value nor its significance are documented anywhere in the RealTek data sheets. diff --git a/share/man/man4/rue.4 b/share/man/man4/rue.4 index 4fe0947b02d1..3fc4373d3aea 100644 --- a/share/man/man4/rue.4 +++ b/share/man/man4/rue.4 @@ -1,155 +1,156 @@ .\" .\" Copyright (c) 2001-2003, Shunsuke Akiyama . .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt RUE 4 .Os .Sh NAME .Nm rue .Nd "RealTek RTL8150 USB to Fast Ethernet controller driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device uhci" .Cd "device ohci" .Cd "device usb" .Cd "device miibus" .Cd "device rue" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_rue_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for USB Ethernet adapters based on the RealTek RTL8150 USB to Fast Ethernet controller chip. .Pp The RTL8150 contains an integrated Fast Ethernet MAC, which supports both 10 and 100Mbps speeds in either full or half duplex. Although designed to interface with 100Mbps peripheral, the existing USB standard specifies a maximum transfer speed of 12Mbps. Users should therefore not expect to actually achieve 100Mbps speeds with this device. .Pp The .Nm driver supports the following media types: .Bl -tag -width ".Cm 10baseT/UTP" .It Cm autoselect Enable auto selection of the media type and options. The user can manually override the auto selected mode by adding media options to the .Pa /etc/rc.conf file. .It Cm 10baseT/UTP Set 10Mbps operation. The .Cm mediaopt option can also be used to select either .Cm full-duplex or .Cm half-duplex modes. .It Cm 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Cm mediaopt option can also be used to select either .Cm full-duplex or .Cm half-duplex modes. .El .Pp The .Nm driver supports the following media options: .Bl -tag -width ".Cm 10baseT/UTP" .It Cm full-duplex Force full duplex operation. .It Cm half-duplex Force half duplex operation. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports RealTek RTL8150 based USB Ethernet adapters including: .Pp .Bl -bullet -compact .It Buffalo (Melco Inc.) LUA-KTX .It Green House GH-USB100B .It LinkSys USB100M .It Billionton 10/100 FastEthernet USBKR2 .El .Sh DIAGNOSTICS .Bl -diag .It "rue%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. .It "rue%d: rx list init failed" The driver failed to allocate an mbuf for the transmitter ring. .It "rue%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Rs .%T "ReakTek RTL8150 data sheet" .%O ftp://ftp.realtek.com.tw/lancard/data_sheet/8150/ .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 5.1 . .Sh AUTHORS The .Nm driver was written by .An Shunsuke Akiyama Aq akiyama@FreeBSD.org . diff --git a/share/man/man4/sf.4 b/share/man/man4/sf.4 index a7b059b27294..a7f7af1f17c8 100644 --- a/share/man/man4/sf.4 +++ b/share/man/man4/sf.4 @@ -1,193 +1,194 @@ .\" Copyright (c) 1997, 1998, 1999 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt SF 4 .Os .Sh NAME .Nm sf -.Nd Adaptec AIC-6915 +.Nd "Adaptec AIC-6915" .Qq Starfire PCI Fast Ethernet adapter driver .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device sf" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_sf_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for Adaptec Duralink Fast Ethernet adapters based on the Adaptec AIC-6915 "Starfire" chipset. .Pp The AIC-6915 is a bus master controller with an MII interface. It supports high and low priority transmit and receive queues, TCP/IP checksum offload, multiple DMA descriptor formats and both polling and producer/consumer DMA models. The AIC-6915 receive filtering options include a 16 entry perfect filter, a 512-bit hash table for multicast addresses, a 512-bit hash table for priority address matching and VLAN filtering. An external MII-compliant transceiver is required for media interfacing. .Pp Multiport adapters consist of several AIC-6915 controllers connected via a PCI to PCI bridge. Each controller is treated as a separate interface by the .Nm driver. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to the .Pa /etc/rc.conf file. .It 10baseT/UTP Set 10Mbps operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .It 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It full-duplex Force full duplex operation .It half-duplex Force half duplex operation. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE Adapters supported by the .Nm driver include: .Pp .Bl -bullet -compact .It ANA-62011 64-bit single port 10/100baseTX adapter .It ANA-62022 64-bit dual port 10/100baseTX adapter .It ANA-62044 64-bit quad port 10/100baseTX adapter .It ANA-69011 32-bit single port 10/100baseTX adapter .It ANA-62020 64-bit single port 100baseFX adapter .El .Sh DIAGNOSTICS .Bl -diag .It "sf%d: couldn't map memory" A fatal initialization error has occurred. This may happen if the PCI BIOS not configured the device, which may be because the BIOS has been configured for a "Plug and Play" operating system. The "Plug and Play OS" setting in the BIOS should be set to "no" or "off" in order for PCI devices to work properly with .Fx . .It "sf%d: couldn't map ports" A fatal initialization error has occurred. This may happen if the PCI BIOS not configured the device, which may be because the BIOS has been configured for a "Plug and Play" operating system. The "Plug and Play OS" setting in the BIOS should be set to "no" or "off" in order for PCI devices to work properly with .Fx . .It "sf%d: couldn't map interrupt" A fatal initialization error has occurred. .It "sf%d: no memory for softc struct!" The driver failed to allocate memory for per-device instance information during initialization. .It "sf%d: failed to enable I/O ports/memory mapping!" The driver failed to initialize PCI I/O port or shared memory access. This might happen if the card is not in a bus-master slot. .It "sf%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr polling 4 , .Xr ifconfig 8 .Rs .%T The Adaptec AIC-6915 Programmer's Manual .%O http://download.adaptec.com/pdfs/user_guides/aic6915_pg.pdf .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 3.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ctr.columbia.edu . diff --git a/share/man/man4/sis.4 b/share/man/man4/sis.4 index 2f75e23a2ce4..e52f02cbfe8b 100644 --- a/share/man/man4/sis.4 +++ b/share/man/man4/sis.4 @@ -1,208 +1,209 @@ .\" Copyright (c) 1997, 1998, 1999 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt SIS 4 .Os .Sh NAME .Nm sis .Nd "SiS 900, SiS 7016 and NS DP83815 Fast Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device sis" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_sis_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for PCI Ethernet adapters and embedded controllers based on the Silicon Integrated Systems SiS 900 and SiS 7016 Fast Ethernet controller chips. .Pp This driver also supports adapters based on the National Semiconductor DP83815 (MacPhyter) PCI Ethernet controller chip. .Pp The SiS 900 is a 100Mbps Ethernet MAC and MII-compliant transceiver in a single package. It uses a bus master DMA and a scatter/gather descriptor scheme. The SiS 7016 is similar to the SiS 900 except that it has no internal PHY, requiring instead an external transceiver to be attached to its MII interface. The SiS 900 and SiS 7016 both have a 128-bit multicast hash filter and a single perfect filter entry for the station address. .Pp The NS DP83815 is also a 100Mbps Ethernet MAC with integrated PHY. The NatSemi chip and the SiS 900 share many of the same features and a fairly similar programming interface, hence both chips are supported by the same driver. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width 10baseTXUTP .It autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to .Xr rc.conf 5 . .It 10baseT/UTP Set 10Mbps operation. The .Xr ifconfig 8 .Cm mediaopt option can also be used to select either .Sq full-duplex or .Sq half-duplex modes. .It 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Xr ifconfig 8 .Cm mediaopt option can also be used to select either .Sq full-duplex or .Sq half-duplex modes. .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width full-duplex .It full-duplex Force full duplex operation .It half-duplex Force half duplex operation. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports Silicon Integrated Systems SiS 900 and SiS 7016 based Fast Ethernet adapters and embedded controllers, as well as Fast Ethernet adapters based on the National Semiconductor DP83815 (MacPhyter) chip. Supported adapters include: .Pp .Bl -bullet -compact .It @Nifty FNECHARD IFC USUP-TX .It MELCO LGY-PCI-TXC .It Netgear FA311-TX (DP83815) .It Netgear FA312-TX (DP83815) .It SiS 630, 635, and 735 motherboard chipsets .El .Sh DIAGNOSTICS .Bl -diag .It "sis%d: couldn't map ports/memory" A fatal initialization error has occurred. .It "sis%d: couldn't map interrupt" A fatal initialization error has occurred. .It "sis%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (e.g.\& a cable fault). .It "sis%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .It "sis%d: no memory for tx list" The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. .It "sis%d: chip is in D3 power state -- setting to D0" This message applies only to adapters which support power management. Some operating systems place the controller in low power mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. If you see this message at boot time and the driver fails to attach the device as a network interface, you will have to perform a warm boot to have the device properly configured. .Pp Note that this condition only occurs when warm booting from another operating system. If you power down your system prior to booting .Fx , the card should be configured correctly. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr polling 4 , .Xr ifconfig 8 .Rs .%T SiS 900 and SiS 7016 datasheets .%O http://www.sis.com.tw .Re .Rs .%T NatSemi DP83815 datasheet .%O http://www.national.com .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 3.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ee.columbia.edu . diff --git a/share/man/man4/sk.4 b/share/man/man4/sk.4 index 13abccabb2fa..1b25360be0df 100644 --- a/share/man/man4/sk.4 +++ b/share/man/man4/sk.4 @@ -1,254 +1,255 @@ .\" Copyright (c) 1997, 1998, 1999 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt SK 4 .Os .Sh NAME .Nm sk .Nd "SysKonnect SK-984x and SK-982x PCI Gigabit Ethernet adapter driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device sk" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_sk_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for the SysKonnect SK-984x and SK-982x series PCI Gigabit Ethernet adapters. .Pp The SysKonnect adapters consist of two main components: the XaQti Corp. XMAC II gigabit MAC and the SysKonnect GEnesis controller ASIC. The XMAC provides the gigabit MAC and PHY support while the GEnesis provides an interface to the PCI bus, DMA support, packet buffering and arbitration. The GEnesis can control up to two XMACs simultaneously, allowing dual-port NIC configurations. .Pp The SK-982x 1000baseT adapters also include a Broadcom BCM5400 1000baseTX PHY which is used in place of the XMAC's internal PHY. The Broadcom PHY is connected to the XMAC via its GMII port. .Pp The .Nm driver configures dual port SysKonnect adapters such that each XMAC is treated as a separate logical network interface. Both ports can operate independently of each other and can be connected to separate networks. The SysKonnect driver software currently only uses the second port on dual port adapters for failover purposes: if the link on the primary port fails, the SysKonnect driver will automatically switch traffic onto the second port. .Pp Also supported is the Marvell Semiconductor 88E1000* gigabit PHY. .Pp The XaQti XMAC II supports full and half duplex operation with autonegotiation. The XMAC also supports unlimited frame sizes. Support for jumbo frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the .Xr ifconfig 8 utility configures the adapter to receive and transmit jumbo frames. Using jumbo frames can greatly improve performance for certain tasks, such as file transfers and data streaming. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to the .Pa /etc/rc.conf file. .It 1000baseTX Set 1000baseTX operation over twisted pair. This is only available for SK-982x series adapters with 1000baseT ports. Both .Ar full-duplex and .Ar half-duplex modes are supported. .It 1000baseSX Set 1000Mbps (Gigabit Ethernet) operation. Both .Ar full-duplex and .Ar half-duplex modes are supported. .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It full-duplex Force full duplex operation .It half-duplex Force half duplex operation. .El .Pp The .Nm driver also supports one special link option for 1000baseTX cards: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It link0 With 1000baseTX cards, establishing a link between two ports requires that one port is configured as master and the other one as slave. With autonegotiation, the master/slave settings will be chosen automatically. However when manually selecting the link state, it is necessary to force one side of the link to be a master and the other a slave. The .Nm driver configures the ports as slaves by default. Setting the .Ar link0 flag with .Xr ifconfig 8 will set a port as a master instead. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE Adapters supported by the .Nm driver include: .Pp .Bl -bullet -compact .It 3Com 3C940 single port, 1000baseT adapter .It 3Com 3C2000-T single port, 1000baseT adapter .It Belkin F5D5005 single port, 1000baseT adapter .It D-Link DGE-530T single port, 1000baseT adapter .It Linksys EG1032 single port, 1000baseT adapter .It SK-9521 SK-NET GE-T single port, 1000baseT adapter .It SK-9821 SK-NET GE-T single port, 1000baseT adapter .It SK-9822 SK-NET GE-T dual port, 1000baseT adapter .It SK-9841 SK-NET GE-LX single port, single mode fiber adapter .It SK-9842 SK-NET GE-LX dual port, single mode fiber adapter .It SK-9843 SK-NET GE-SX single port, multimode fiber adapter .It SK-9844 SK-NET GE-SX dual port, multimode fiber adapter .It SMC 9452TX single port, 1000baseT adapter .El .Sh SYSCTL VARIABLES The following variable is available as both .Xr sysctl 8 variable and .Xr loader 8 tunable: .Bl -tag -width indent .It Va dev.skc.%d.int_mod .Pp This variable controls interrupt moderation. The accepted range is 10 to 10000, default value is 100 microseconds. The interface has to be brought down and up again before a change takes effect. .El .Sh DIAGNOSTICS .Bl -diag .It "sk%d: couldn't map memory" A fatal initialization error has occurred. .It "sk%d: couldn't map ports" A fatal initialization error has occurred. .It "sk%d: couldn't map interrupt" A fatal initialization error has occurred. .It "sk%d: no memory for softc struct!" The driver failed to allocate memory for per-device instance information during initialization. .It "sk%d: failed to enable memory mapping!" The driver failed to initialize PCI shared memory mapping. This might happen if the card is not in a bus-master slot. .It "sk%d: no memory for jumbo buffers!" The driver failed to allocate memory for jumbo frames during initialization. .It "sk%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr vlan 4 , .Xr ifconfig 8 .Rs .%T XaQti XMAC II datasheet .%O http://www.xaqti.com .Re .Rs .%T SysKonnect GEnesis programming manual .%O http://www.syskonnect.com .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 3.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ctr.columbia.edu . diff --git a/share/man/man4/sn.4 b/share/man/man4/sn.4 index 12598607ab66..72b869d919b3 100644 --- a/share/man/man4/sn.4 +++ b/share/man/man4/sn.4 @@ -1,99 +1,100 @@ .\" .\" Copyright (c) 2000 Warner Losh .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt SN 4 .Os .Sh NAME .Nm sn .Nd "Ethernet driver for SMC91Cxx based cards" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device sn" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_sn_load="YES" .Ed .Sh DESCRIPTION The .Nm device driver supports SMC91Cxx based ISA and PCMCIA cards. .Sh HARDWARE The .Nm driver supports SMC91Cxx based ISA and PCMCIA cards including: .Pp .Bl -bullet -compact .It 3Com Megahertz X-Jack Ethernet PC-Card XJ10BT .It 3Com Megahertz X-Jack Ethernet PC-Card XJ10BC .It Farallon EtherMac PC Card .It Motorola Mariner Ethernet/Modem PC Card .It Ositech Seven of Diamonds Ethernet PC Card .It Ositech Jack of Hearts Ethernet/Modem PC Card .It Psion Gold Card Netglobal Ethernet PC Card .It Psion Gold Card Netglobal 10/100 Fast Ethernet PC Card .It Psion Gold Card Netglobal 56k+10Mb Ethernet PC Card .It SMC EZEther PC Card (8020BT) .It SMC EZEther PC Card (8020T) .El .Pp The .Nm driver supports the SMC 91C90, SMC 91C92, SMC 91C94, SMC 91C95, SMC 91C96, SMC91C100 and SMC 91C100FD chips from SMC. .Sh SEE ALSO .Xr ed 4 , .Xr el 4 , .Xr ep 4 , .Xr ie 4 , .Xr intro 4 , .Xr ng_ether 4 , .Xr vx 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver appeared in .Fx 4.0 . diff --git a/share/man/man4/ste.4 b/share/man/man4/ste.4 index 94a938345eda..117b19446c6e 100644 --- a/share/man/man4/ste.4 +++ b/share/man/man4/ste.4 @@ -1,188 +1,189 @@ .\" Copyright (c) 1997, 1998, 1999 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt STE 4 .Os .Sh NAME .Nm ste .Nd "Sundance Technologies ST201 Fast Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device ste" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_ste_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for PCI Ethernet adapters and embedded controllers based on the Sundance Technologies ST201 PCI Fast Ethernet controller chip. .Pp The Sundance ST201 uses bus master DMA and is designed to be a 3Com Etherlink XL workalike. It uses the same DMA descriptor structure and is very similar in operation, however its register layout is different. The ST201 has a 64-bit multicast hash filter and a single perfect filter entry for the station address. It supports both 10 and 100Mbps speeds in either full or half duplex using an MII transceiver. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to the .Pa /etc/rc.conf file. .It 10baseT/UTP Set 10Mbps operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .It 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It full-duplex Force full duplex operation .It half-duplex Force half duplex operation. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports Sundance Technologies ST201 based Fast Ethernet adapters and embedded controllers including: .Pp .Bl -bullet -compact .It D-Link DFE-530TXS .It D-Link DFE-550TX .It D-Link DFE-580TX .El .Sh DIAGNOSTICS .Bl -diag .It "ste%d: couldn't map ports/memory" A fatal initialization error has occurred. .It "ste%d: couldn't map interrupt" A fatal initialization error has occurred. .It "ste%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .It "ste%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .It "ste%d: no memory for tx list" The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. .It "ste%d: chip is in D3 power state -- setting to D0" This message applies only to adapters which support power management. Some operating systems place the controller in low power mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. If you see this message at boot time and the driver fails to attach the device as a network interface, you will have to perform a second warm boot to have the device properly configured. .Pp Note that this condition only occurs when warm booting from another operating system. If you power down your system prior to booting .Fx , the card should be configured correctly. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr polling 4 , .Xr ifconfig 8 .Rs .%T Sundance ST201 data sheet .%O http://www.sundanceti.com .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 3.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ee.columbia.edu . diff --git a/share/man/man4/ti.4 b/share/man/man4/ti.4 index 915d16f53d92..50c49c78d8b0 100644 --- a/share/man/man4/ti.4 +++ b/share/man/man4/ti.4 @@ -1,339 +1,340 @@ .\" Copyright (c) 1997, 1998, 1999 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt TI 4 .Os .Sh NAME .Nm ti .Nd "Alteon Networks Tigon I and Tigon II Gigabit Ethernet driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device ti" .Cd "options TI_PRIVATE_JUMBOS" .Cd "options TI_JUMBO_HDRSPLIT" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_ti_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for PCI Gigabit Ethernet adapters based on the Alteon Networks Tigon Gigabit Ethernet controller chip. The Tigon contains an embedded R4000 CPU, gigabit MAC, dual DMA channels and a PCI interface unit. The Tigon II contains two R4000 CPUs and other refinements. Either chip can be used in either a 32-bit or 64-bit PCI slot. Communication with the chip is achieved via PCI shared memory and bus master DMA. The Tigon I and II support hardware multicast address filtering, VLAN tag extraction and insertion, and jumbo Ethernet frames sizes up to 9000 bytes. Note that the Tigon I chipset is no longer in active production: all new adapters should come equipped with Tigon II chipsets. .Pp While the Tigon chipset supports 10, 100 and 1000Mbps speeds, support for 10 and 100Mbps speeds is only available on boards with the proper transceivers. Most adapters are only designed to work at 1000Mbps, however the driver should support those NICs that work at lower speeds as well. .Pp Support for jumbo frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the .Xr ifconfig 8 utility configures the adapter to receive and transmit jumbo frames. Using jumbo frames can greatly improve performance for certain tasks, such as file transfers and data streaming. .Pp Header splitting support for Tigon 2 boards (this option has no effect for the Tigon 1) can be turned on with the .Dv TI_JUMBO_HDRSPLIT option. See .Xr zero_copy 9 for more discussion on zero copy receive and header splitting. .Pp The .Nm driver normally uses jumbo receive buffers allocated by the .Xr sendfile 2 buffer allocator, but can be configured to use its own private pool of jumbo buffers that are contiguous instead of buffers from the jumbo allocator, which are made up of multiple page sized chunks. To turn on private jumbos, use the .Dv TI_PRIVATE_JUMBOS option. .Pp Support for vlans is also available using the .Xr vlan 4 mechanism. See the .Xr vlan 4 man page for more details. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to the .Pa /etc/rc.conf file. .It 10baseT/UTP Set 10Mbps operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .It 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .It 1000baseSX Set 1000Mbps (Gigabit Ethernet) operation. Only full .Ar full-duplex mode is supported at this speed. .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It full-duplex Force full duplex operation .It half-duplex Force half duplex operation. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports Gigabit Ethernet adapters based on the Alteon Tigon I and II chips. The .Nm driver has been tested with the following adapters: .Pp .Bl -bullet -compact .It 3Com 3c985-SX Gigabit Ethernet adapter (Tigon 1) .It 3Com 3c985B-SX Gigabit Ethernet adapter (Tigon 2) .It Alteon AceNIC V Gigabit Ethernet adapter (1000baseSX) .It Alteon AceNIC V Gigabit Ethernet adapter (1000baseT) .It Digital EtherWORKS 1000SX PCI Gigabit adapter .It Netgear GA620 Gigabit Ethernet adapter (1000baseSX) .It Netgear GA620T Gigabit Ethernet adapter (1000baseT) .El .Pp The following adapters should also be supported but have not yet been tested: .Pp .Bl -bullet -compact .It Asante GigaNIX1000T Gigabit Ethernet adapter .It Asante PCI 1000BASE-SX Gigabit Ethernet adapter .It Farallon PN9000SX Gigabit Ethernet adapter .It NEC Gigabit Ethernet .It Silicon Graphics PCI Gigabit Ethernet adapter .El .Sh IOCTLS In addition to the standard .Xr socket 2 .Xr ioctl 2 calls implemented by most network drivers, the .Nm driver also includes a character device interface that can be used for additional diagnostics, configuration and debugging. With this character device interface, and a specially patched version of .Xr gdb 1 , the user can debug firmware running on the Tigon board. .Pp These ioctls and their arguments are defined in the .In sys/tiio.h header file. .Bl -tag -width ".Dv ALT_WRITE_TG_MEM" .It Dv TIIOCGETSTATS Return card statistics DMAed from the card into kernel memory approximately every 2 seconds. (That time interval can be changed via the .Dv TIIOCSETPARAMS ioctl.) The argument is .Vt "struct ti_stats" . .It Dv TIIOCGETPARAMS Get various performance-related firmware parameters that largely affect how interrupts are coalesced. The argument is .Vt "struct ti_params" . .It Dv TIIOCSETPARAMS Set various performance-related firmware parameters that largely affect how interrupts are coalesced. The argument is .Vt "struct ti_params" . .It Dv TIIOCSETTRACE Tell the NIC to trace the requested types of information. The argument is .Vt ti_trace_type . .It Dv TIIOCGETTRACE Dump the trace buffer from the card. The argument is .Vt "struct ti_trace_buf" . .It Dv ALT_ATTACH This ioctl is used for compatibility with Alteon's Solaris driver. They apparently only have one character interface for debugging, so they have to tell it which Tigon instance they want to debug. This ioctl is a noop for .Fx . .It Dv ALT_READ_TG_MEM Read the requested memory region from the Tigon board. The argument is .Vt "struct tg_mem" . .It Dv ALT_WRITE_TG_MEM Write to the requested memory region on the Tigon board. The argument is .Vt "struct tg_mem" . .It Dv ALT_READ_TG_REG Read the requested register on the Tigon board. The argument is .Vt "struct tg_reg" . .It Dv ALT_WRITE_TG_REG Write to the requested register on the Tigon board. The argument is .Vt "struct tg_reg" . .El .Sh FILES .Bl -tag -width ".Pa /dev/ti[0-255]" -compact .It Pa /dev/ti[0-255] Tigon driver character interface. .El .Sh DIAGNOSTICS .Bl -diag .It "ti%d: couldn't map memory" A fatal initialization error has occurred. .It "ti%d: couldn't map interrupt" A fatal initialization error has occurred. .It "ti%d: no memory for softc struct!" The driver failed to allocate memory for per-device instance information during initialization. .It "ti%d: failed to enable memory mapping!" The driver failed to initialize PCI shared memory mapping. This might happen if the card is not in a bus-master slot. .It "ti%d: no memory for jumbo buffers!" The driver failed to allocate memory for jumbo frames during initialization. .It "ti%d: bios thinks we're in a 64 bit slot, but we aren't" The BIOS has programmed the NIC as though it had been installed in a 64-bit PCI slot, but in fact the NIC is in a 32-bit slot. This happens as a result of a bug in some BIOSes. This can be worked around on the Tigon II, but on the Tigon I initialization will fail. .It "ti%d: board self-diagnostics failed!" The ROMFAIL bit in the CPU state register was set after system startup, indicating that the on-board NIC diagnostics failed. .It "ti%d: unknown hwrev" The driver detected a board with an unsupported hardware revision. The .Nm driver supports revision 4 (Tigon 1) and revision 6 (Tigon 2) chips and has firmware only for those devices. .It "ti%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .El .Sh SEE ALSO .Xr sendfile 2 , .Xr arp 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr vlan 4 , .Xr ifconfig 8 , .Xr zero_copy 9 .Sh HISTORY The .Nm device driver first appeared in .Fx 3.0 . .Sh AUTHORS .An -nosplit The .Nm driver was written by .An Bill Paul Aq wpaul@bsdi.com . The header splitting firmware modifications, character .Xr ioctl 2 interface and debugging support were written by .An Kenneth Merry Aq ken@FreeBSD.org . Initial zero copy support was written by .An Andrew Gallatin Aq gallatin@FreeBSD.org . diff --git a/share/man/man4/tl.4 b/share/man/man4/tl.4 index 88c736fccff3..1b556bccf9d1 100644 --- a/share/man/man4/tl.4 +++ b/share/man/man4/tl.4 @@ -1,188 +1,189 @@ .\" Copyright (c) 1997, 1998 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt TL 4 .Os .Sh NAME .Nm tl .Nd "Texas Instruments ThunderLAN Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device tl" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_tl_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for PCI Ethernet adapters based on the Texas Instruments ThunderLAN Ethernet controller chip. .Pp The ThunderLAN controller has a standard MII interface that supports up to 32 physical interface devices (PHYs). It also has a built-in 10baseT PHY hardwired at MII address 31, which may be used in some 10Mbps-only hardware configurations. In 100Mbps configurations, a National Semiconductor DP83840A or other MII-compliant PHY may be attached to the ThunderLAN's MII bus. If a DP83840A or equivalent is available, the ThunderLAN chip can operate at either 100Mbps or 10Mbps in either half-duplex or full-duplex modes. The ThunderLAN's built-in PHY and the DP83840A also support autonegotiation. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It autoselect Enable autoselection of the media type and options. Note that this option is only available on those PHYs that support autonegotiation. Also, the PHY will not advertise those modes that have been explicitly disabled using the following media options. .It 10baseT/UTP Set 10Mbps operation .It 100baseTX Set 100Mbps (Fast Ethernet) operation .It 10base5/AUI Enable AUI/BNC interface (useful only with the built-in PHY). .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It full-duplex Force full duplex operation .It half-duplex Force half duplex operation. .It hw-loopback Enable hardware loopback mode. .El .Pp Note that the 100baseTX media type is only available if supported by the PHY. For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports Texas Instruments ThunderLAN based Ethernet and Fast Ethernet adapters including a large number of Compaq PCI Ethernet adapters. Also supported are: .Pp .Bl -bullet -compact .It Olicom OC-2135/2138 10/100 TX UTP adapter .It Olicom OC-2325/OC-2326 10/100 TX UTP adapter .It Racore 8148 10baseT/100baseTX/100baseFX adapter .It Racore 8165 10/100baseTX adapter .El .Pp The .Nm driver also supports the built-in Ethernet adapters of various Compaq Prosignia servers and Compaq Deskpro desktop machines including: .Pp .Bl -bullet -compact .It Compaq Netelligent 10 .It Compaq Netelligent 10 T PCI UTP/Coax .It Compaq Netelligent 10/100 .It Compaq Netelligent 10/100 Dual-Port .It Compaq Netelligent 10/100 Proliant .It Compaq Netelligent 10/100 TX Embedded UTP .It Compaq Netelligent 10/100 TX UTP .It Compaq NetFlex 3P .It Compaq NetFlex 3P Integrated .It Compaq NetFlex 3P w/BNC .El .Sh DIAGNOSTICS .Bl -diag .It "tl%d: couldn't map memory" A fatal initialization error has occurred. .It "tl%d: couldn't map interrupt" A fatal initialization error has occurred. .It "tl%d: device timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .It "tl%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .It "tl%d: no memory for tx list" The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 2.2 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ctr.columbia.edu . diff --git a/share/man/man4/tx.4 b/share/man/man4/tx.4 index f91818358e95..8cb3a30f1e18 100644 --- a/share/man/man4/tx.4 +++ b/share/man/man4/tx.4 @@ -1,122 +1,123 @@ .\" .\" Copyright (c) 1998-2001 Semen Ustimenko (semenu@FreeBSD.org) .\" .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. .\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT, .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt TX 4 .Os .Sh NAME .Nm tx .Nd "SMC 83c17x Fast Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device tx" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_tx_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for the Ethernet adapters based on the SMC 83c17x (EPIC) chips. These are mostly SMC 9432 series cards. .Pp The .Nm driver supports the following media types (depending on card's capabilities): .Pp .Bl -tag -width ".Cm 10baseT/UTP" .It Cm autoselect Enable autonegotiation (default). .It Cm 100baseFX Set 100Mbps (Fast Ethernet) fiber optic operation. .It Cm 100baseTX Set 100Mbps (Fast Ethernet) twisted pair operation. .It Cm 10baseT/UTP Set 10Mbps on 10baseT port. .It Cm 10base2/BNC Set 10Mbps on 10base2 port. .El .Pp The .Nm driver supports the following media options: .Bl -tag -width ".Cm full-duplex" .It Cm full-duplex Set full-duplex operation. .El .Pp The .Nm driver supports oversized Ethernet packets (up to 1600 bytes). Refer to the .Xr ifconfig 8 man page on setting the interface's MTU. .Pp The old .Dq Li "ifconfig tx0 linkN" method of configuration is not supported. .Ss "VLAN (IEEE 802.1Q) support" The .Nm driver supports the VLAN operation (using .Xr vlan 4 interfaces) without decreasing the MTU on the .Xr vlan 4 interfaces. .Sh DIAGNOSTICS .Bl -diag .It "tx%d: device timeout %d packets" The device stops responding. Device and driver reset follows this error. .It "tx%d: PCI fatal error occurred (%s)" One of following errors occurred: PCI Target Abort, PCI Master Abort, Data Parity Error or Address Parity Error. Device and driver reset follows this error. .It "tx%d: cannot allocate mbuf header/cluster" Cannot allocate memory for received packet. Packet thrown away. .It "tx%d: can't stop %s DMA" While resetting, the driver failed to stop the device correctly. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh BUGS The auto-negotiation does not work very well. diff --git a/share/man/man4/txp.4 b/share/man/man4/txp.4 index 08b0f56936ba..366a81e7a229 100644 --- a/share/man/man4/txp.4 +++ b/share/man/man4/txp.4 @@ -1,155 +1,156 @@ .\" $OpenBSD: txp.4,v 1.8 2001/06/26 02:09:11 pjanzen Exp $ .\" .\" Copyright (c) 2001 Jason L. Wright (jason@thought.net) .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED .\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE .\" DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, .\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES .\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR .\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, .\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN .\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt TXP 4 .Os .Sh NAME .Nm txp .Nd "3Com 3XP Typhoon/Sidewinder (3CR990) Ethernet interface" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device txp" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_txp_load="YES" .Ed .Sh DESCRIPTION The .Nm interface provides access to the 10Mb/s and 100Mb/s Ethernet networks via the .Tn 3Com .Tn Typhoon/Sidewinder chipset. .Pp Basic Ethernet functions are provided as well as support for .Xr vlan 4 tag removal and insertion assistance, receive .Xr ip 4 , .Xr tcp 4 , and .Xr udp 4 checksum offloading, and transmit .Xr ip 4 checksum offloading. There is currently no support for transmit .Xr tcp 4 or .Xr udp 4 checksum offloading, .Xr tcp 4 segmentation, nor .Xr ipsec 4 acceleration. Note that hardware checksumming is only used when the interface is not in .Xr bridge 4 mode. .Pp Each of the host's network addresses is specified at boot time with an .Dv SIOCSIFADDR .Xr ioctl 2 . The .Nm interface employs the address resolution protocol described in .Xr arp 4 to dynamically map between Internet and Ethernet addresses on the local network. .Pp When a .Nm interface is brought up, by default, it will attempt to auto-negotiate the link speed and duplex mode. The speeds, in order of attempt, are: 100Mb/s Full Duplex, 100Mb/s Half Duplex, 10 Mb/s Full Duplex, and 10 Mb/s Half Duplex. .Pp The .Nm supports several media types, which are selected via the .Xr ifconfig 8 command. The supported media types are: .Bl -tag -width indent .It Cm media autoselect Attempt to autoselect the media type (default) .It Cm media 100baseTX mediaopt full-duplex Use 100baseTX, full duplex .It Cm media 100baseTX Op Cm mediaopt half-duplex Use 100baseTX, half duplex .It Cm media 10baseT mediaopt full-duplex Use 10baseT, full duplex .It Cm media 10baseT Op Cm mediaopt half-duplex Use 10baseT, half duplex .El .Sh HARDWARE The .Nm driver supports the following cards: .Pp .Bl -bullet -offset indent -compact .It 3Com 3CR990-TX-95 .It 3Com 3CR990-TX-97 .It 3Com 3cR990B-TXM .It 3Com 3CR990SVR95 .It 3Com 3CR990SVR97 .It 3Com 3cR990B-SRV .El .Sh SEE ALSO .Xr arp 4 , .Xr inet 4 , .Xr intro 4 , .Xr ip 4 , .Xr miibus 4 , .Xr tcp 4 , .Xr udp 4 , .Xr vlan 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm driver first appeared in .Ox 2.9 . diff --git a/share/man/man4/udav.4 b/share/man/man4/udav.4 index 0e2348f07712..b057dcc4dfc8 100644 --- a/share/man/man4/udav.4 +++ b/share/man/man4/udav.4 @@ -1,98 +1,99 @@ .\" $NetBSD$ .\" .\" Copyright (c) 2003 .\" Shingo WATANABE . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Shingo WATANABE. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt UDAV 4 .Os .Sh NAME .Nm udav .Nd "Davicom DM9601 USB Ethernet driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device uhci" .Cd "device ohci" .Cd "device usb" .Cd "device miibus" .Cd "device udav" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_udav_load="YES" .Ed .Sh HARDWARE The .Nm driver supports the following adapters: .Pp .Bl -bullet -compact .It Corega FEther USB-TXC .El .Sh DESCRIPTION The .Nm driver provides support for USB .Tn Ethernet adapters based on the Davicom DM9601 chipset. .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr usb 4 , .Xr ifconfig 8 .Rs .%T "Davicom DM9601 data sheet" .%O http://www.davicom.com.tw/big5/download/Data%20Sheet/DM9601-DS-P01-930914.pdf .Re .Sh HISTORY The .Nm device driver first appeared in .Nx 2.0 . .Sh AUTHORS The .Nm driver was written by .An Shingo WATANABE Aq nabe@nabechan.org . diff --git a/share/man/man4/ural.4 b/share/man/man4/ural.4 index 9df3b7a82a1e..ef13a4336dde 100644 --- a/share/man/man4/ural.4 +++ b/share/man/man4/ural.4 @@ -1,131 +1,132 @@ .\" Copyright (c) 2005 .\" Damien Bergamini .\" .\" Permission to use, copy, modify, and distribute this software for any .\" purpose with or without fee is hereby granted, provided that the above .\" copyright notice and this permission notice appear in all copies. .\" .\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES .\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR .\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Os .Dt URAL 4 .Sh NAME .Nm ural .Nd "Ralink Technology RT2500USB IEEE 802.11 driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device ehci" .Cd "device uhci" .Cd "device ohci" .Cd "device usb" .Cd "device ural" .Cd "device wlan" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_ural_load="YES" .Ed .Sh DESCRIPTION The .Nm driver supports USB 2.0 wireless adapters based on the RT2500USB chipset. .Pp The RT2500USB chipset consists of two integrated chips, a RT2570 MAC/BBP and a radio transceiver (the model of which depends on the card revision). .Pp The RT2522, RT2523, RT2524, RT2525, RT2525e and RT2526 radio transceivers operate in the 2.4GHz band (802.11b/g) whereas the RT5222 is a dual-band radio transceiver that can operate in the 2.4GHz and 5.2GHz bands (802.11a). .Sh HARDWARE The following adapters should work: .Pp .Bl -column -compact ".Li Atlantis Land A02-PCM-W54" "Bus" .It Em Card Ta Em Bus .It Li "AMIT WL532U" Ta USB .It Li "ASUS WL-167g" Ta USB .It Li "Buffalo WLI-U2-KG54-AI" Ta USB .It Li "CNet CWD-854" Ta USB .It Li "Compex WLU54G" Ta USB .It Li "Conceptronic C54RU" Ta USB .It Li "D-Link DWL-G122 b1" Ta USB .It Li "E-Tech WGUS02" Ta USB .It Li "Gigabyte GN-WBKG" Ta USB .It Li "Linksys WUSB54G v4" Ta USB .It Li "Linksys WUSB54GP v4" Ta USB .It Li "MSI MS-6861" Ta USB .It Li "MSI MS-6865" Ta USB .It Li "MSI MS-6869" Ta USB .It Li "Repotec RP-WU0402" Ta USB .It Li "Surecom EP-9001-g" Ta USB .El .Pp An up to date list can be found at .Pa http://damien.bergamini.free.fr/ral/list.html . .Sh EXAMPLES Join an existing BSS network (i.e., connect to an access point): .Pp .Dl "ifconfig ural0 inet 192.168.0.20 netmask 0xffffff00" .Pp Join a specific BSS network with network name .Dq Li my_net : .Pp .Dl "ifconfig ural0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net" .Pp Join a specific BSS network with 40-bit WEP encryption: .Bd -literal -offset indent ifconfig ural0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e wepmode on wepkey 0x1234567890 .Ed .Pp Join a specific BSS network with 104-bit WEP encryption: .Bd -literal -offset indent ifconfig ural0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e wepmode on wepkey 0x01020304050607080910111213 .Ed .Sh DIAGNOSTICS .Bl -diag .It "ural%d: device timeout" The driver will reset the hardware. This should not happen. .El .Sh SEE ALSO .Xr arp 4 , .Xr netintro 4 , .Xr usb 4 , .Xr wlan 4 , .Xr ifconfig 8 .Rs .%T "Ralink Technology" .%O http://www.ralinktech.com/ .Re .Sh HISTORY The .Nm driver first appeared in .Ox 3.7 . .Sh CAVEATS .Pp The .Nm driver does not support automatic adaptation of the transmit speed. .Sh AUTHORS The .Nm driver was written by .An Damien Bergamini Aq damien@FreeBSD.org . diff --git a/share/man/man4/vge.4 b/share/man/man4/vge.4 index 9959135f8211..dc3f64a91376 100644 --- a/share/man/man4/vge.4 +++ b/share/man/man4/vge.4 @@ -1,210 +1,211 @@ .\" Copyright (c) 2004 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt VGE 4 .Os .Sh NAME .Nm vge .Nd "VIA Networking Technologies VT6122 PCI Gigabit Ethernet adapter driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device vge" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_vge_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for various NICs and embedded Ethernet interfaces based on the VIA Networking Technologies VT6122 Gigabit Ethernet controller chips. .Pp The VT6122 is a 33/66Mhz 64-bit PCI device which combines a tri-speed MAC with an integrated 10/100/1000 copper PHY. (Some older cards use an external PHY.) The MAC supports TCP/IP hardware checksums (IPv4 only), TCP large send, VLAN tag insertion and stripping, as well as VLAN filtering, a 64-entry CAM filter and a 64-entry VLAN filter, 64-bit multicast hash filter, 4 separate transmit DMA queues, flow control and jumbo frames up to 16K in size. The VT6122 has a 16K receive FIFO and 48K transmit FIFO. .Pp The .Nm driver takes advantage of the VT6122's checksum offload and VLAN tagging features, as well as the jumbo frame and CAM filter support. The CAM filter is used for multicast address filtering to provide 64 perfect multicast address filter support. If it is necessary for the interface to join more than 64 multicast groups, the driver will switch over to using the hash filter. .Pp The jumbo frame support can be enabled by setting the interface MTU to any value larger than the default of 1500 bytes, up to a maximum of 9000 bytes. The receive and transmit checksum offload support can be toggled on and off using the .Xr ifconfig 8 utility. .Pp The .Nm driver supports the following media types: .Bl -tag -width ".Cm 10baseT/UTP" .It Cm autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to .Xr rc.conf 5 . .It Cm 10baseT/UTP Set 10Mbps operation. The .Xr ifconfig 8 .Cm mediaopt option can also be used to select either .Cm full-duplex or .Cm half-duplex modes. .It Cm 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Xr ifconfig 8 .Cm mediaopt option can also be used to select either .Cm full-duplex or .Cm half-duplex modes. .It Cm 1000baseTX Set 1000baseTX operation over twisted pair. The .Xr ifconfig 8 .Cm mediaopt option can also be used to select either .Cm full-duplex or .Cm half-duplex modes. .El .Pp The .Nm driver supports the following media options: .Bl -tag -width ".Cm full-duplex" .It Cm full-duplex Force full duplex operation. .It Cm half-duplex Force half duplex operation. .El .Pp The .Nm driver also supports one special link option for 1000baseTX cards: .Bl -tag -width ".Cm link0" .It Cm link0 With 1000baseTX cards, establishing a link between two ports requires that one port be configured as a master and the other a slave. With autonegotiation, the master/slave settings will be chosen automatically. However when manually selecting the link state, it is necessary to force one side of the link to be a master and the other a slave. The .Nm driver configures the ports as slaves by default. Setting the .Cm link0 flag with .Xr ifconfig 8 will set a port as a master instead. .El .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports VIA Networking VT3119 and VT6122 based Gigabit Ethernet adapters including: .Pp .Bl -bullet -compact .It VIA Networking LAN-on-motherboard Gigabit Ethernet .It ZyXEL GN650-T 64-bit PCI Gigabit Ethernet NIC (ZX1701) .It ZyXEL GN670-T 32-bit PCI Gigabit Ethernet NIC (ZX1702) .El .Sh DIAGNOSTICS .Bl -diag .It "vge%d: couldn't map memory" A fatal initialization error has occurred. .It "vge%d: couldn't map ports" A fatal initialization error has occurred. .It "vge%d: couldn't map interrupt" A fatal initialization error has occurred. .It "vge%d: failed to enable memory mapping!" The driver failed to initialize PCI shared memory mapping. This might happen if the card is not in a bus-master slot. .It "vge%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr polling 4 , .Xr vlan 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 5.3 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@windriver.com . diff --git a/share/man/man4/vlan.4 b/share/man/man4/vlan.4 index 3a094cfeedf7..f117648f61af 100644 --- a/share/man/man4/vlan.4 +++ b/share/man/man4/vlan.4 @@ -1,207 +1,208 @@ .\" .\" Copyright (c) 2001 Yar Tikhiy .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt VLAN 4 .Os .Sh NAME .Nm vlan .Nd "IEEE 802.1Q VLAN network interface" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device vlan" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_vlan_load="YES" .Ed .Sh DESCRIPTION The .Nm driver demultiplexes frames tagged according to the IEEE 802.1Q standard into logical .Nm network interfaces, which allows routing/bridging between multiple VLANs through a single switch trunk port. .Pp Each .Nm interface is created at runtime using interface cloning. This is most easily done with the .Xr ifconfig 8 .Cm create command or using the .Va cloned_interfaces variable in .Xr rc.conf 5 . .Pp To function, a .Nm interface must be assigned a parent interface and numeric VLAN tag using .Xr ifconfig 8 . A single parent can be assigned to multiple .Nm interfaces provided they have different tags. The parent interface is likely to be an Ethernet card connected to a properly configured switch port. The VLAN tag should match one of those set up in the switched network. .Sh HARDWARE The .Nm driver supports efficient operation over parent interfaces that can provide help in processing VLANs. Such interfaces are automatically recognized by their capabilities. Depending on the level of sophistication found in a physical interface, it may do full VLAN processing or just be able to receive and transmit frames exceeding the maximum Ethernet frame size by the length of a 802.1Q header. The capabilities may be user-controlled by the respective parameters to .Xr ifconfig 8 , .Cm vlanhwtag and .Cm vlanmtu . However, a physical interface is not obliged to react to them: It may have either capability enabled permanently without a way to turn it off. The whole issue is very specific to a particular device and its driver. .Pp By now, the list of physical interfaces able of full VLAN processing in the hardware is limited to the following devices: .Xr bge 4 , .Xr em 4 , .Xr ixgb 4 , .Xr nge 4 , .Xr re 4 , .Xr ti 4 , .Xr txp 4 , and .Xr vge 4 . .Pp The rest of the Ethernet interfaces can run VLANs using software emulation in the .Nm driver. However, most of them lack the capability of transmitting and receiving oversized frames. Assigning such an interface as the parent to .Nm will result in a reduced MTU on the corresponding .Nm interfaces. In the modern Internet, this is likely to cause .Xr tcp 4 connectivity problems due to massive, inadequate .Xr icmp 4 filtering that breaks the Path MTU Discovery mechanism. .Pp The interfaces that support oversized frames are as follows: .Bl -tag -width ".Xr fxp 4 " -offset indent .It Xr bfe 4 supports long frames for .Nm natively. .It Xr dc 4 supports long frames for .Nm natively. .It Xr de 4 requires defining .Dv BIG_PACKET in the .Pa /usr/src/sys/pci/if_de.c source file and rebuilding the kernel or module. The hack works only for the 21041, 21140, and 21140A chips. .It Xr fxp 4 supports long frames for .Nm natively. .It Xr hme 4 supports long frames for .Nm natively. .It Xr rl 4 supports long frames for .Nm natively. .It Xr sis 4 supports long frames for .Nm natively. .It Xr ste 4 supports long frames for .Nm natively. .It Xr tl 4 has support for long frames. .It Xr tx 4 supports long frames for .Nm natively. .It Xr xl 4 supports long frames only if the card is built on a newer chip (Cyclone and above). .El .Pp The .Nm driver automatically recognizes devices that natively support oversized frames for .Nm use and calculates the appropriate frame MTU based on the capabilities of the parent interface. The other interfaces listed above can handle oversized frames, but they do not advertise this ability of theirs. The MTU setting on .Nm can be corrected manually if used in conjunction with such parent interface. .Sh SEE ALSO .Xr kqueue 2 , .Xr miibus 4 , .Xr ifconfig 8 .Sh BUGS No 802.1Q features except VLAN tagging are implemented. .Pp .Dv EVFILT_NETDEV events on a .Nm interface will be sent through .Xr kqueue 2 only if the parent interface uses .Xr miibus 4 for link state notification. diff --git a/share/man/man4/vr.4 b/share/man/man4/vr.4 index 0bcee70afbe9..60e7e83ee9ae 100644 --- a/share/man/man4/vr.4 +++ b/share/man/man4/vr.4 @@ -1,207 +1,208 @@ .\" Copyright (c) 1997, 1998 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt VR 4 .Os .Sh NAME .Nm vr .Nd "VIA Technologies Rhine I/II/III Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device vr" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_vr_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for PCI Ethernet adapters and embedded controllers based on the VIA Technologies VT3043 Rhine I, VT86C100A Rhine II, and VT6105/VT6105M Rhine III Fast Ethernet controller chips. .Pp The VIA Rhine chips use bus master DMA and have a descriptor layout designed to resemble that of the DEC 21x4x .Dq tulip chips. The register layout is different however and the receive filter in the Rhine chips is much simpler and is programmed through registers rather than by downloading a special setup frame through the transmit DMA engine. Transmit and receive DMA buffers must be longword aligned. The Rhine chips are meant to be interfaced with external physical layer devices via an MII bus. They support both 10 and 100Mbps speeds in either full or half duplex. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It autoselect Enable autoselection of the media type and options. The user can manually override the autoselected mode by adding media options to the .Pa /etc/rc.conf file. .It 10baseT/UTP Set 10Mbps operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .It 100baseTX Set 100Mbps (Fast Fthernet) operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It full-duplex Force full duplex operation .It half-duplex Force half duplex operation. .El .Pp Note that the 100baseTX media type is only available if supported by the adapter. For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports VIA Technologies Rhine I, Rhine II, and Rhine III based Fast Ethernet adapters including: .Pp .Bl -bullet -compact .It D-Link DFE530-TX .It Hawking Technologies PN102TX .It AOpen/Acer ALN-320 .El .Sh DIAGNOSTICS .Bl -diag .It "vr%d: couldn't map memory" A fatal initialization error has occurred. .It "vr%d: couldn't map interrupt" A fatal initialization error has occurred. .It "vr%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .It "vr%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .It "vr%d: no memory for tx list" The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. .It "vr%d: chip is in D3 power state -- setting to D0" This message applies only to adapters which support power management. Some operating systems place the controller in low power mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. If you see this message at boot time and the driver fails to attach the device as a network interface, you will have to perform second warm boot to have the device properly configured. .Pp Note that this condition only occurs when warm booting from another operating system. If you power down your system prior to booting .Fx , the card should be configured correctly. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr polling 4 , .Xr ifconfig 8 .Rs .%T The VIA Technologies VT86C100A data sheet .%O http://www.via.com.tw .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 3.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ctr.columbia.edu . .Sh BUGS The .Nm driver always copies transmit mbuf chains into longword-aligned buffers prior to transmission in order to pacify the Rhine chips. If buffers are not aligned correctly, the chip will round the supplied buffer address and begin DMAing from the wrong location. This buffer copying impairs transmit performance on slower systems but cannot be avoided. On faster machines (e.g.\& a Pentium II), the performance impact is much less noticeable. diff --git a/share/man/man4/wb.4 b/share/man/man4/wb.4 index d7284945ca4c..2c38352789be 100644 --- a/share/man/man4/wb.4 +++ b/share/man/man4/wb.4 @@ -1,199 +1,200 @@ .\" Copyright (c) 1997, 1998 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt WB 4 .Os .Sh NAME .Nm wb .Nd "Winbond W89C840F Fast Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device wb" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_wb_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for PCI Ethernet adapters and embedded controllers based on the Winbond W89C840F Fast Ethernet controller chip. The 840F should not be confused with the 940F, which is an NE2000 clone and only supports 10Mbps speeds. .Pp The Winbond controller uses bus master DMA and is designed to be a DEC 'tulip' workalike. It differs from the standard DEC design in several ways: the control and status registers are spaced 4 bytes apart instead of 8, and the receive filter is programmed through registers rather than by downloading a special setup frame via the transmit DMA engine. Using an external PHY, the Winbond chip supports both 10 and 100Mbps speeds in either full or half duplex. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It autoselect Enable autoselection of the media type and options. This is only supported if the PHY chip attached to the Winbond controller supports NWAY autonegotiation. The user can manually override the autoselected mode by adding media options to the .Pa /etc/rc.conf file. .It 10baseT/UTP Set 10Mbps operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .It 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It full-duplex Force full duplex operation .It half-duplex Force half duplex operation. .El .Pp Note that the 100baseTX media type is only available if supported by the adapter. For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports Winbond W89C840F based Fast Ethernet adapters and embedded controllers including: .Pp .Bl -bullet -compact .It Trendware TE100-PCIE .El .Sh DIAGNOSTICS .Bl -diag .It "wb%d: couldn't map memory" A fatal initialization error has occurred. .It "wb%d: couldn't map interrupt" A fatal initialization error has occurred. .It "wb%d: watchdog timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .It "wb%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .It "wb%d: no memory for tx list" The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. .It "wb%d: chip is in D3 power state -- setting to D0" This message applies only to adapters which support power management. Some operating systems place the controller in low power mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. If you see this message at boot time and the driver fails to attach the device as a network interface, you will have to perform second warm boot to have the device properly configured. .Pp Note that this condition only occurs when warm booting from another operating system. If you power down your system prior to booting .Fx , the card should be configured correctly. .El .Sh SEE ALSO .Xr arp 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 3.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ctr.columbia.edu . .Sh BUGS The Winbond chip seems to behave strangely in some cases when the link partner switches modes. If for example both sides are set to 10Mbps half-duplex, and the other end is changed to 100Mbps full-duplex, the Winbond's receiver suddenly starts writing trash all over the RX descriptors. The .Nm driver handles this by forcing a reset of both the controller chip and attached PHY. This is drastic, but it appears to be the only way to recover properly from this condition. diff --git a/share/man/man4/wi.4 b/share/man/man4/wi.4 index 1285695798a8..f1c195d79fe8 100644 --- a/share/man/man4/wi.4 +++ b/share/man/man4/wi.4 @@ -1,436 +1,437 @@ .\" Copyright (c) 1997, 1998, 1999 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" $OpenBSD: wi.4tbl,v 1.14 2002/04/29 19:53:50 jsyn Exp $ .\" .Dd July 16, 2005 .Dt WI 4 .Os .Sh NAME .Nm wi .Nd "Lucent Hermes, Intersil PRISM and Spectrum24 IEEE 802.11 driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device wi" .Cd "device wlan" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_wi_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for wireless network adapters based around the Lucent Hermes, Intersil PRISM-II, Intersil PRISM-2.5, Intersil Prism-3, and Symbol Spectrum24 chipsets. All five chipsets provide a similar interface to the driver. .Pp Supported features include 802.11 and 802.3 frames, power management, BSS, IBSS, WDS and old-style Lucent ad-hoc operation modes. Cards based on the Intersil PRISM chips also support a host-based access point mode which allows a card to act as a normal access point (with some assistance from the .Nm driver). The Lucent Hermes and Symbol Spectrum24 chipsets do not contain this functionality. The PRISM family of chips do not support the WDS functionality. All host/device interaction is via programmed I/O, even on those cards that support a DMA interface. .Pp The .Nm driver encapsulates all IP and ARP traffic as 802.11 frames, however it can receive either 802.11 or 802.3 frames. Transmit speed is selectable between 1Mbps, 2Mbps, 5.5 Mbps and 11Mbps depending on your hardware. Most hardware supports 11Mbps where the signal quality allows, but falls back to slower speeds when it does not. Except for the Lucent WaveLAN Bronze cards, all cards supported by the .Nm driver support WEP for encryption. To enable encryption, use .Xr ifconfig 8 as shown below. .Pp By default, the .Nm driver configures the card for BSS operation (aka infrastructure mode). This mode requires the use of an access point (base station). .Pp The .Nm driver also supports a point-to-point mode where stations can communicate amongst themselves without the aid of an access point. Note that there are two possible point-to-point modes. One mode, referred to as .Dq "ad-hoc demo mode" , or .Dq "legacy Lucent ad-hoc mode" , predates the IEEE 802.11 specification and so may not interoperate with cards from different vendors. The standardized point-to-point mode is called IBSS (or confusingly just ad-hoc mode), but is not supported by cards with very old firmware revisions. If your cards supports IBSS mode, it is recommended that you use it in preference to the .Dq "ad-hoc demo mode" in new installations. .Pp Cards supported by the driver based on the Intersil PRISM family of chips also have a host-based access point mode which allows the card to act as an access point (base station). Access points are different than operating in IBSS mode. They operate in BSS mode. They allow for easier roaming and bridge all Ethernet traffic such that machines connected via an access point appear to be on the local Ethernet segment. .Pp For more information on configuring this device, see .Xr ifconfig 8 . .Pp Cards supported by the .Nm driver come in a variety of packages, though the most common are of the PCMCIA type. In many cases, the PCI version of a wireless card is simply a PCMCIA card bundled with a PCI adapter. The PCI adapters come in two flavors: true PCMCIA bridges and dumb PCMCIA bridges. A true PCMCIA bridge (such as those sold by Lucent) will attach as a real PCMCIA controller. The wireless card will then attach to the PCMCIA bus. Wireless cards in PCMCIA slots may be inserted and ejected on the fly. .Pp A dumb bridge, on the other hand, does not show up as a true PCMCIA bus. The wireless card will simply appear to the host as a normal PCI device and will not require any PCMCIA support. Cards in this type of adapter should only be removed when the machine is powered down. .Pp The following cards are among those supported by the .Nm driver: .Pp .Bl -column -compact "Linksys Instant Wireless WPC11 2.5" "Spectrum24" "PCI or PCMCIA" .Em "Card Chip Bus" 3Com AirConnect 3CRWE737A Spectrum24 PCMCIA 3Com AirConnect 3CRWE777A Prism-II PCI Accton airDirect WN3301 PCMCIA ACTIONTEC HWC01170 Prism-2.5 PCMCIA Adaptech ANW-8030 Prism-3 PCMCIA Addtron AWP-100 Prism-II PCMCIA Adtec Adlink/340C Prism-II PCMCIA Airvast WN 100 Prism-3 PCMCIA Airway 802.11 Adapter PCMCIA Agere Orinoco Hermes PCMCIA Allied Telesis WR211PCM Prism-II PCMCIA ArTem OnAir Prism? PCMCIA Asus WL100 Prism-2.5 PCMCIA Avaya Wireless Prism-II PCMCIA Bay eMobility 11B Prism-2.5? PCMCIA Blue Concentric Circle WL-379F Prism-II CF BreezeNet Wireless Prism-II PCMCIA Buffalo WLI-PCM-S11 Prism-II PCMCIA Buffalo WLI-PCM-L11G Hermes PCMCIA Buffalo WLI-CF-S11G Prism-II CF Buffalo WLI2-CF-S11G Prism 2.5 CF Cabletron RoamAbout Hermes PCMCIA Compaq Agency NC5004 Prism-II PCMCIA Compaq WL100 Prism-II PCMCIA Compaq WL110 Hermes PCMCIA Compaq WL200 Prism-II PCMCIA Contec FLEXLAN/FX-DS110-PCC Prism-II PCMCIA Corega PCC-11 Prism-II PCMCIA Corega PCCA-11 Prism-II PCMCIA Corega PCCB-11 Prism-II PCMCIA Corega CGWLPCIA11 Prism-II PCI Dell TrueMobile 1150 Hermes PCMCIA Dlink Air 660 Prism-II PCMCIA Dlink DWL520 Prism-2.5 PCI Dlink DWL650 Prism-2.5 PCMCIA ELECOM Air@Hawk/LD-WL11/PCC PCMCIA ELSA MC-11 PCMCIA ELSA XI300 Prism-II PCMCIA ELSA XI800 Prism-II CF EMTAC A2424i Prism-II PCMCIA Ericsson Wireless LAN CARD C11 Spectrum24 PCMCIA Farallon Skyline Prism-II PCMCIA Gemtek WL-311 Prism-2.5 PCMCIA Hawking Technology WE110P Prism-2.5 PCMCIA Home Wireless Networks Prism-II PCMCIA IBM High Rate Wireless Hermes PCMCIA ICOM SL-1100 Prism-II PCMCIA I-O DATA WN-B11/PCM Prism-II PCMCIA Intel PRO/Wireless 2011 Spectrum24 PCMCIA Intersil Prism II Prism-II PCMCIA Intersil Mini-PCI Prism-2.5 PCI Intersil ISL37100P Prism-3 PCMCIA Intersil ISL37110P Prism-3 PCMCIA Intersil ISL37300P Prism-3 PCMCIA Laneed Wireless PCMCIA Linksys Instant Wireless WPC11 Prism-II PCMCIA Linksys Instant Wireless WPC11 2.5 Prism-2.5 PCMCIA Linksys Instant Wireless WPC11 3.0 Prism-3 PCMCIA Linksys WCF11 Prism-3 PCMCIA Linksys WCF12 Prism-3 CF Lucent WaveLAN Hermes PCMCIA Melco Airconnect Prism-II PCMCIA Microsoft MN-520 WLAN Prism-II PCMCIA NANOSPEED ROOT-RZ2000 Prism-II PCMCIA NCR WaveLAN/IEEE 802.11 PCMCIA NDC/Sohoware NCP130 Prism-II PCI NEC CMZ-RT-WP Prism-II PCMCIA NEC PK-WL001 Lucent PCMCIA NEC PC-WL/11C Prism-II PCMCIA Netgear MA311 Prism-2.5 PCI Netgear MA401 Prism-II/2.5 PCMCIA Netgear MA401RA Prism-II PCMCIA Netgear MA701 Prism-II CF NOKIA C020 WLAN Prism-II PCMCIA NOKIA C110 WLAN Prism-2.5 PCMCIA NTT-ME 11Mbps Wireless LAN Prism-II PCMCIA Planex GeoWave/GW-NS110 Prism-II PCMCIA Planex GW-NS11H Prism-II PCMCIA Proxim Harmony Prism-II PCMCIA Proxim RangeLAN-DS Prism-II PCMCIA Samsung MagicLAN SWL-2000N Prism-II PCMCIA SENAO SL-2511CD Prism-3 PCMCIA Siemens SpeedStream SS1021 Prism-II PCMCIA SMC 2602 EZ Connect (3.3V) Prism-II PCI or PCMCIA SMC 2632 EZ Connect Prism-II PCMCIA Socket Low Power WLAN-CF Prism-II CF Sony PCWA-C100 Lucent PCMCIA Sony PEGA-WL110 Prism-2.5 PCMCIA Symbol Spectrum24 Spectrum24 PCMCIA Symbol LA-4100 Spectrum24 CF TDK LAK-CD011WL Prism-II PCMCIA Toshiba Wireless LAN Card Prism-II PCMCIA U.S.\& Robotics Wireless Card 2410 Prism-II PCMCIA YIS YWL-11B Prism-II PCMCIA .El .Pp Several vendors sell PCI adapters built around the PLX Technology 9050 or 9052 chip. The following such adapters are supported or expected to work: .Pp .Bl -item -compact .It 3Com AirConnect 3CRWE777A (3.3V) .It Belkin F5D6000 (a rebadged WL11000P) .It Eumitcom WL11000P .It Global Sun Technology GL24110P (untested) .It Global Sun Technology GL24110P02 .It LinkSys WDT11 (a rebadged GL24110P02) .It Netgear MA301 .It US Robotics 2415 (rebadged WL11000P) .It Wisecom Wireless LAN PCI Adapter .El .Pp The following adapters have the same model numbers as those listed above, but might not work if the actual card is after the change away from the Prism family: .Pp .Bl -item -compact .It DLink DWL520 .El .Sh EXAMPLES Join an existing BSS network (ie: connect to an access point): .Pp .Dl "ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00" .Pp Join a specific BSS network with network name .Dq Li my_net : .Pp .Dl "ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net" .Pp Join a specific BSS network with WEP encryption: .Bd -literal -offset indent ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e wepmode on wepkey 0x8736639624 .Ed .Pp Join a Lucent legacy demo ad-hoc network with network name .Dq Li my_net : .Bd -literal -offset indent ifconfig wi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e media DS/11Mbps mediaopt adhoc,link0 .Ed .Pp Join/create an IBSS network with network name .Dq Li my_net : .Bd -literal -offset indent ifconfig wi0 inet 192.168.0.22 netmask 0xffffff00 ssid my_net \e media DS/11Mbps mediaopt adhoc .Ed .Pp Create a host-based access point (Prism only): .Bd -literal -offset indent ifconfig wi0 inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e media DS/11Mbps mediaopt hostap .Ed .Pp Create a host-based access point with WEP enabled (Prism only): .Bd -literal -offset indent ifconfig wi0 inet 192.168.0.10 netmask 0xffffff00 ssid my_ap \e wepmode on wepkey 0x1234567890 media DS/11Mbps \e mediaopt hostap .Ed .Pp Create a host-based wireless bridge to fxp0 (Prism only): .Bd -literal -offset indent Add BRIDGE to the kernel config. ifconfig wi0 inet up ssid my_ap media DS/11Mbps mediaopt hostap sysctl net.link.ether.bridge.enable=1 sysctl net.link.ether.bridge.config="wi0 fxp0" sysctl net.inet.ip.check_interface=0 .Ed .Pp This will give you the same functionality as an access point. .Sh DIAGNOSTICS .Bl -diag .It "wi%d: init failed" The WaveLAN card failed to become ready after an initialization command was issued. .It "wi%d: failed to allocate %d bytes on NIC" The driver was unable to allocate memory for transmit frames in the NIC's on-board RAM. This can also be an indication of an incorrectly configured interrupt. .It "wi%d: device timeout" The WaveLAN card failed to generate an interrupt to acknowledge a transmit command. .El .Sh SEE ALSO .Xr an 4 , .Xr arp 4 , .Xr ath 4 , .Xr card 4 , .Xr netintro 4 , .Xr pccard 4 , .Xr pccbb 4 , .Xr pcic 4 , .Xr wlan 4 , .Xr ifconfig 8 , .Xr wicontrol 8 .Rs .%T HCF Light programming specification .%O http://www.wavelan.com .Re .Sh HISTORY The .Nm device driver first appeared in .Fx 3.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ctr.columbia.edu . This man page comes from .Ox . .Sh CAVEATS Different regulatory domains have different default channels for adhoc mode. See .Xr ifconfig 8 for information on how to change the channel. See .Xr wicontrol 8 for information on different regulatory domains. .Pp The Intersil Prism family of chips' host-based access point mode has bugs for station firmware versions prior to 0.8.3. The driver currently precludes hostap functionality with older station firmware. The best version of the station firmware for the Prism family of chips seems to be 1.4.9. Some users of Prism-II and 2.5 based cards report that station firmware version 1.3.4 works better for them in hostap than 1.4.9. Older versions of the Prism station firmware have a number of issues with hostap mode. The IBSS/adhoc mode appears to work well on station firmware 1.3.1 and later. The IBSS/adhoc mode appears to have problems for some people with older versions of station firmware. .Pp Lucent cards prior to firmware version 6.0.6 do not support IBSS mode. These cards support only the pre-802.11 mode known as .Dq "demo ad-hoc mode" which does not interoperate with stations in IBSS mode. .Pp Prism cards prior to version 0.8.0 do not support IBSS mode. .Pp Symbol cards prior to version 2.50.00 do not support IBSS mode. .Sh BUGS Not all the new messages are documented here, and many of them are indications of transient errors that are not indications of serious problems. .Pp WL200 PCI wireless cards are based on a Cirrus Logic CL-PD6729 bridge chips glued to an Intersil Prism-II PCMCIA chipset w/o the PC Card form factor being present. These chips are special and require special care to use properly. One must set .Va hw.pcic.pd6729_intr_path Ns = Ns Qq Li 2 in .Pa /boot/loader.conf . This tells the PC Card system to use PCI interrupts for this odd beast. It is not possible to know automatically which kind of interrupts to use. OLDCARD devices .Xr ( pcic 4 and .Xr card 4 ) support this device. NEWCARD devices .Xr ( pccbb 4 and .Xr pccard 4 ) do not support it at this time. diff --git a/share/man/man4/xe.4 b/share/man/man4/xe.4 index 332206c6a26e..e2db31629620 100644 --- a/share/man/man4/xe.4 +++ b/share/man/man4/xe.4 @@ -1,169 +1,170 @@ .\" .\" Copyright (c) 2003 Tom Rhodes .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt XE 4 .Os .Sh NAME .Nm xe .Nd "Xircom PCMCIA Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following line in your kernel configuration file: +driver into your kernel, place the following line in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device xe" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_xe_load="YES" .Ed .Sh DESCRIPTION The .Nm driver supports .Tn PCMCIA Ethernet adapters based on Xircom CE2- and CE3-class hardware. This includes devices made by Xircom along with various .Tn OEM manufacturers. .Pp Please note that the .Nm driver only supports .Tn PCMCIA cards and their Ethernet functions. .Nm does not support the on-board modem device located on some version of the Ethernet/modem combo cards. In particular, Xircom RealPort2 cards are not supported by this driver. .Pp The .Nm driver supports the following media types: .Bl -tag -width ".Cm autoselect" .It Cm autoselect Enable autoselection of media type and options. .It Cm 10Base2/BNC Select 10Mbps operation on a BNC coaxial connector. .It Cm 10BaseT/UTP Select 10Mbps operation on a RJ-45 connector. .It Cm 100BaseTX Select 100Mbps operation. .El .Pp Note that 100BaseTX operation is not available on CE2-class cards, while the 10Base2/BNC mode is only available on CE2-class cards. Full-duplex operation is currently not supported. For more information on configuring network interface devices, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports the following cards: .Pp .Bl -bullet -compact .It Xircom CreditCard Ethernet (PS-CE2-10) .It Xircom CreditCard Ethernet + Modem 28 (PS-CEM-28) .It Xircom CreditCard Ethernet + Modem 33 (CEM33) .It Xircom CreditCard 10/100 (CE3, CE3B) .It Xircom CreditCard Ethernet 10/100 + Modem 56 (CEM56) .It Xircom RealPort Ethernet 10 (RE10) .It Xircom RealPort Ethernet 10/100 (RE100) .It Xircom RealPort Ethernet 10/100 + Modem 56 (REM56, REM56G) .It Accton Fast EtherCard-16 (EN2226) .It Compaq Microcom CPQ550 Ethernet/Modem PC Card .It Compaq Netelligent 10/100 PC Card (CPQ-10/100) .It Intel EtherExpress Pro/100 PC Card Mobile Adapter 16 (Pro/100 M16A) .It Intel EtherExpress Pro/100 LAN/Modem PC Card Adapter (Pro/100 M16B) .El .Pp Other similar devices using the same hardware may also be supported. .Sh DIAGNOSTICS .Bl -diag .It "xe%d: Cannot allocate ioport" .It "xe%d: Cannot allocate irq" A fatal initialization error occurred while attempting to allocate system resources for the card. .It "xe%d: Unable to fix your %s combo card" A fatal initialization error occurred while attempting to attach an Ethernet/modem combo card. .It "xe%d: watchdog timeout: resetting card" The card failed to generate an interrupt acknowledging a transmitted packet. May indicate a .Tn PCMCIA configuration problem. .It "xe%d: no carrier" The card has lost all contact with the network; this usually indicates a cable problem. .El .Sh SEE ALSO .Xr pccard 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm driver first appeared in .Fx 3.3 . .Sh AUTHORS .An -nosplit The .Nm device driver was written by .An Scott Mitchell Aq rsm@FreeBSD.org . This manual page was written by .An Scott Mitchell Aq rsm@FreeBSD.org , and .An Tom Rhodes Aq trhodes@FreeBSD.org . .Sh BUGS Supported devices will fail to attach on some machines using the .Tn NEWCARD .Tn PC Card framework. .Pp Automatic media selection is usually unreliable. diff --git a/share/man/man4/xl.4 b/share/man/man4/xl.4 index ceba6f56e45f..d7f628a27925 100644 --- a/share/man/man4/xl.4 +++ b/share/man/man4/xl.4 @@ -1,267 +1,268 @@ .\" Copyright (c) 1997, 1998 .\" Bill Paul . All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by Bill Paul. .\" 4. Neither the name of the author nor the names of any co-contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF .\" THE POSSIBILITY OF SUCH DAMAGE. .\" .\" $FreeBSD$ .\" .Dd July 16, 2005 .Dt XL 4 .Os .Sh NAME .Nm xl .Nd "3Com Etherlink XL and Fast Etherlink XL Ethernet device driver" .Sh SYNOPSIS To compile support for the .Nm -driver into your kernel, place the following lines in your kernel configuration file: +driver into your kernel, place the following lines in your +kernel configuration file: .Bd -ragged -offset indent .Cd "device miibus" .Cd "device xl" .Ed .Pp Alternatively, to load the .Nm driver at boot time, place the following line in .Xr loader.conf 5 : .Bd -literal -offset indent if_xl_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides support for PCI Ethernet adapters and embedded controllers based on the 3Com "boomerang," "cyclone," "hurricane" and "tornado" bus-master Etherlink XL chips. .Pp The Etherlink XL chips support built-in 10baseT, 10base2 and 10base5 transceivers as well as an MII bus for externally attached PHY transceivers. The 3c905 series typically uses a National Semiconductor NS 83840A 10/100 PHY for 10/100 Mbps support in full or half-duplex. The 3c905B adapters have built-in autonegotiation logic mapped onto the MII for compatibility with previous drivers. Fast Etherlink XL adapters such as the 3c905-TX and 3c905B-TX are capable of 10 or 100Mbps data rates in either full or half duplex and can be manually configured for any supported mode or automatically negotiate the highest possible mode with a link partner. .Pp The .Nm driver supports the following media types: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It autoselect Enable autoselection of the media type and options. Note that this option is only available with the 3c905 and 3c905B adapters with external PHYs or built-in autonegotiation logic. For 3c900 adapters, the driver will choose the mode specified in the EEPROM. The user can change this by adding media options to the .Pa /etc/rc.conf file. .It 10baseT/UTP Set 10Mbps operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .It 100baseTX Set 100Mbps (Fast Ethernet) operation. The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .It 10base5/AUI Enable AUI transceiver (available only on COMBO cards). .It 10base2/BNC Enable BNC coax transceiver (available only on COMBO cards). .El .Pp The .Nm driver supports the following media options: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It full-duplex Force full duplex operation .It half-duplex Force half duplex operation. .El .Pp Note that the 100baseTX media type is only available if supported by the adapter. For more information on configuring this device, see .Xr ifconfig 8 . .Sh HARDWARE The .Nm driver supports the following hardware: .Pp .Bl -bullet -compact .It 3Com 3c900-TPO .It 3Com 3c900-COMBO .It 3Com 3c905-TX .It 3Com 3c905-T4 .It 3Com 3c900B-TPO .It 3Com 3c900B-TPC .It 3Com 3c900B-FL .It 3Com 3c900B-COMBO .It 3Com 3c905B-T4 .It 3Com 3c905B-TX .It 3Com 3c905B-FX .It 3Com 3c905B-COMBO .It 3Com 3c905C-TX .It 3Com 3c980, 3c980B, and 3c980C server adapters .It 3Com 3cSOHO100-TX OfficeConnect adapters .It 3Com 3c450 HomeConnect adapters .It 3Com 3c555, 3c556 and 3c556B mini-PCI adapters .It 3Com 3C3SH573BT, 3C575TX, 3CCFE575BT, 3CXFE575BT, 3CCFE575CT, 3CXFE575CT, 3CCFEM656, 3CCFEM656B, and 3CCFEM656C, 3CXFEM656, 3CXFEM656B, and 3CXFEM656C CardBus adapters .It 3Com 3c905-TX, 3c905B-TX 3c905C-TX, 3c920B-EMB, and 3c920B-EMB-WNM embedded adapters .El .Pp Both the 3C656 family of CardBus cards and the 3C556 family of MiniPCI cards have a built-in proprietary modem. Neither the .Nm driver nor any other .Fx driver supports this modem. .Sh DIAGNOSTICS .Bl -diag .It "xl%d: couldn't map memory" A fatal initialization error has occurred. .It "xl%d: couldn't map interrupt" A fatal initialization error has occurred. .It "xl%d: device timeout" The device has stopped responding to the network, or there is a problem with the network connection (cable). .It "xl%d: no memory for rx list" The driver failed to allocate an mbuf for the receiver ring. .It "xl%d: no memory for tx list" The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. .It "xl%d: command never completed!" Some commands issued to the 3c90x ASIC take time to complete: the driver is supposed to wait until the 'command in progress' bit in the status register clears before continuing. In rare instances, this bit may not clear. To avoid getting caught in an infinite wait loop, the driver only polls the bit for a finite number of times before giving up, at which point it issues this message. This message may be printed during driver initialization on slower machines. If you see this message but the driver continues to function normally, the message can probably be ignored. .It "xl%d: chip is in D3 power state -- setting to D0" This message applies only to 3c905B adapters, which support power management. Some operating systems place the 3c905B in low power mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The 3c905B loses all of its PCI configuration in the D3 state, so if the BIOS does not set it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be enough to return the driver to a fully operational condition. If you see this message at boot time and the driver fails to attach the device as a network interface, you will have to perform second warm boot to have the device properly configured. .Pp Note that this condition only occurs when warm booting from another operating system. If you power down your system prior to booting .Fx , the card should be configured correctly. .It "xl%d: WARNING: no media options bits set in the media options register!" This warning may appear when using the driver on some Dell Latitude docking stations with built-in 3c905-TX adapters. For whatever the reason, the 'MII available' bit in the media options register on this particular equipment is not set, even though it should be (the 3c905-TX always uses an external PHY transceiver). The driver will attempt to guess the proper media type based on the PCI device ID word. The driver makes a lot of noise about this condition because the author considers it a manufacturing defect. .El .Sh SEE ALSO .Xr arp 4 , .Xr cardbus 4 , .Xr miibus 4 , .Xr netintro 4 , .Xr ng_ether 4 , .Xr pccard 4 , .Xr polling 4 , .Xr ifconfig 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 3.0 . .Sh AUTHORS The .Nm driver was written by .An Bill Paul Aq wpaul@ctr.columbia.edu .