Wed Jul 22 17:34:56 2009 UTC ()
The HAL is no longer a kernel blob, reflect this.


(alc)
diff -r1.20 -r1.21 src/share/man/man4/ath.4
cvs diff -r1.20 -r1.21 src/share/man/man4/ath.4 (switch to unified diff)

--- src/share/man/man4/ath.4 2007/12/01 19:57:08 1.20
+++ src/share/man/man4/ath.4 2009/07/22 17:34:56 1.21
@@ -1,322 +1,321 @@ @@ -1,322 +1,321 @@
1.\" $NetBSD: ath.4,v 1.20 2007/12/01 19:57:08 wiz Exp $ 1.\" $NetBSD: ath.4,v 1.21 2009/07/22 17:34:56 alc Exp $
2.\" 2.\"
3.\" Copyright (c) 2002, 2003 Sam Leffler, Errno Consulting 3.\" Copyright (c) 2002, 2003 Sam Leffler, Errno Consulting
4.\" All rights reserved. 4.\" All rights reserved.
5.\"" 5.\""
6.\" Redistribution and use in source and binary forms, with or without 6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions 7.\" modification, are permitted provided that the following conditions
8.\" are met: 8.\" are met:
9.\" 1. Redistributions of source code must retain the above copyright 9.\" 1. Redistributions of source code must retain the above copyright
10.\" notice, this list of conditions and the following disclaimer, 10.\" notice, this list of conditions and the following disclaimer,
11.\" without modification. 11.\" without modification.
12.\" 2. Redistributions in binary form must reproduce at minimum a disclaimer 12.\" 2. Redistributions in binary form must reproduce at minimum a disclaimer
13.\" similar to the "NO WARRANTY" disclaimer below ("Disclaimer") and any 13.\" similar to the "NO WARRANTY" disclaimer below ("Disclaimer") and any
14.\" redistribution must be conditioned upon including a substantially 14.\" redistribution must be conditioned upon including a substantially
15.\" similar Disclaimer requirement for further binary redistribution. 15.\" similar Disclaimer requirement for further binary redistribution.
16.\" 3. Neither the names of the above-listed copyright holders nor the names 16.\" 3. Neither the names of the above-listed copyright holders nor the names
17.\" of any contributors may be used to endorse or promote products derived 17.\" of any contributors may be used to endorse or promote products derived
18.\" from this software without specific prior written permission. 18.\" from this software without specific prior written permission.
19.\" 19.\"
20.\" NO WARRANTY 20.\" NO WARRANTY
21.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 21.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
22.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 22.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
23.\" LIMITED TO, THE IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTIBILITY 23.\" LIMITED TO, THE IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTIBILITY
24.\" AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL 24.\" AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
25.\" THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR SPECIAL, EXEMPLARY, 25.\" THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR SPECIAL, EXEMPLARY,
26.\" OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 26.\" OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
27.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 27.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
28.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER 28.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
29.\" IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 29.\" IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
30.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF 30.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
31.\" THE POSSIBILITY OF SUCH DAMAGES. 31.\" THE POSSIBILITY OF SUCH DAMAGES.
32.\" 32.\"
33.\" 33.\"
34.\" Note: This man page was taken by Perry Metzger almost entirely 34.\" Note: This man page was taken by Perry Metzger almost entirely
35.\" from the "ath" and "ath_hal" man pages in FreeBSD. I claim no 35.\" from the "ath" and "ath_hal" man pages in FreeBSD. I claim no
36.\" copyright because there was nearly no original work performed in 36.\" copyright because there was nearly no original work performed in
37.\" doing so. Maintainers should check the FreeBSD originals for 37.\" doing so. Maintainers should check the FreeBSD originals for
38.\" updates against the following two revisions and incorporate them 38.\" updates against the following two revisions and incorporate them
39.\" if needed: 39.\" if needed:
40.\" 40.\"
41.\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/ath.4,v 1.16 2004/02/18 08:30:08 maxim Exp $ 41.\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/ath.4,v 1.16 2004/02/18 08:30:08 maxim Exp $
42.\" parts from $FreeBSD: /repoman/r/ncvs/src/share/man/man4/ath_hal.4,v 1.7 2004/01/07 20:49:51 blackend Exp $ 42.\" parts from $FreeBSD: /repoman/r/ncvs/src/share/man/man4/ath_hal.4,v 1.7 2004/01/07 20:49:51 blackend Exp $
43.\" 43.\"
44.Dd October 14, 2006 44.Dd October 14, 2006
45.Dt ATH 4 45.Dt ATH 4
46.Os 46.Os
47.Sh NAME 47.Sh NAME
48.Nm ath 48.Nm ath
49.Nd Atheros IEEE 802.11 driver 49.Nd Atheros IEEE 802.11 driver
50.Sh SYNOPSIS 50.Sh SYNOPSIS
51.Cd "ath* at pci? dev ? function ?" 51.Cd "ath* at pci? dev ? function ?"
52.Cd "ath* at cardbus? function ?" 52.Cd "ath* at cardbus? function ?"
53.Sh DESCRIPTION 53.Sh DESCRIPTION
54The 54The
55.Nm 55.Nm
56driver provides support for wireless network adapters based on 56driver provides support for wireless network adapters based on
57the Atheros AR5210, AR5211, AR5212, and AR5213 chips. 57the Atheros AR5210, AR5211, AR5212, and AR5213 chips.
58Chip-specific support is provided by the Atheros Hardware Access Layer 58Chip-specific support is provided by the Atheros Hardware Access Layer
59(HAL), which is currently available only in binary form for selected 59(HAL).
60architectures. 
61.Pp 60.Pp
62Supported features include 802.11 and 802.3 frames, power management, BSS, 61Supported features include 802.11 and 802.3 frames, power management, BSS,
63IBSS, and host-based access point operation modes. 62IBSS, and host-based access point operation modes.
64All host/device interaction is via DMA. 63All host/device interaction is via DMA.
65.Pp 64.Pp
66The 65The
67.Nm 66.Nm
68driver encapsulates all IP and ARP traffic as 802.11 frames, however 67driver encapsulates all IP and ARP traffic as 802.11 frames, however
69it can receive either 802.11 or 802.3 frames. 68it can receive either 802.11 or 802.3 frames.
70Transmit speed and operating mode is selectable 69Transmit speed and operating mode is selectable
71depending on your hardware. 70depending on your hardware.
72.Pp 71.Pp
73AR5210-based devices support 802.11a operation with transmit speeds 72AR5210-based devices support 802.11a operation with transmit speeds
74of 6 Mbps, 9 Mbps, 12 Mbps, 18 Mbps, 24 Mbps, 36 Mbps, 48 Mbps, and 54 Mbps. 73of 6 Mbps, 9 Mbps, 12 Mbps, 18 Mbps, 24 Mbps, 36 Mbps, 48 Mbps, and 54 Mbps.
75.Pp 74.Pp
76AR5211-based devices support 802.11a and 802.11b operation with transmit 75AR5211-based devices support 802.11a and 802.11b operation with transmit
77speeds as above for 802.11a operation and 76speeds as above for 802.11a operation and
781Mbps, 2Mbps, 5.5 Mbps and 11Mbps for 802.11b operation. 771Mbps, 2Mbps, 5.5 Mbps and 11Mbps for 802.11b operation.
79.Pp 78.Pp
80AR5212-based and AR5213-based devices support 802.11a, 802.11b, and 79AR5212-based and AR5213-based devices support 802.11a, 802.11b, and
81802.11g operation with transmit speeds appropriate to each. 80802.11g operation with transmit speeds appropriate to each.
82.Pp 81.Pp
83All chips also support an Atheros Turbo Mode (TM) that operates in the 82All chips also support an Atheros Turbo Mode (TM) that operates in the
84802.11a frequency range with 2x the transmit speeds. 83802.11a frequency range with 2x the transmit speeds.
85(This mode is, however, only interoperable with other Atheros-based devices.) 84(This mode is, however, only interoperable with other Atheros-based devices.)
86.Pp 85.Pp
87The actual transmit speed used is dependent on signal quality and the 86The actual transmit speed used is dependent on signal quality and the
88.Dq rate control 87.Dq rate control
89algorithm employed by the driver. 88algorithm employed by the driver.
90All chips support WEP encryption. 89All chips support WEP encryption.
91AR5211 and AR5212 support the AES, TKIP, and Michael cryptographic 90AR5211 and AR5212 support the AES, TKIP, and Michael cryptographic
92operations required for WPA but at this time the driver does not support them. 91operations required for WPA but at this time the driver does not support them.
93To enable encryption, use 92To enable encryption, use
94.Xr ifconfig 8 . 93.Xr ifconfig 8 .
95.Pp 94.Pp
96By default, the 95By default, the
97.Nm 96.Nm
98driver configures the card for BSS operation (aka infrastructure 97driver configures the card for BSS operation (aka infrastructure
99mode). 98mode).
100This mode requires the use of an access point (base station). 99This mode requires the use of an access point (base station).
101.Pp 100.Pp
102The 101The
103.Nm 102.Nm
104driver also supports the standard IBSS point-to-point mode 103driver also supports the standard IBSS point-to-point mode
105where stations can communicate amongst themselves without the 104where stations can communicate amongst themselves without the
106aid of an access point. 105aid of an access point.
107.Pp 106.Pp
108The driver may also be configured to operate in hostap mode. 107The driver may also be configured to operate in hostap mode.
109In this mode a host may function as an access point (base station). 108In this mode a host may function as an access point (base station).
110Access points are different than operating in IBSS mode. 109Access points are different than operating in IBSS mode.
111They operate in BSS mode. 110They operate in BSS mode.
112They allow for easier roaming and bridge all Ethernet traffic such 111They allow for easier roaming and bridge all Ethernet traffic such
113that machines connected via an access point appear to be on the local 112that machines connected via an access point appear to be on the local
114Ethernet segment. 113Ethernet segment.
115.Pp 114.Pp
116The mode of operation is chosen by specifying the appropriate mediaopt 115The mode of operation is chosen by specifying the appropriate mediaopt
117value to ifconfig. 116value to ifconfig.
118The 117The
119.Fl m 118.Fl m
120flag to ifconfig will list the available options. 119flag to ifconfig will list the available options.
121.Pp 120.Pp
122For more information on configuring this device, see 121For more information on configuring this device, see
123.Xr ifconfig 8 . 122.Xr ifconfig 8 .
124.Pp 123.Pp
125Devices supported by the 124Devices supported by the
126.Nm 125.Nm
127driver come in either CardBus or mini-PCI packages. 126driver come in either CardBus or mini-PCI packages.
128Wireless cards in CardBus slots may be inserted and ejected on the fly. 127Wireless cards in CardBus slots may be inserted and ejected on the fly.
129.Pp 128.Pp
130The following cards are among those supported by the 129The following cards are among those supported by the
131.Nm 130.Nm
132driver: 131driver:
133.Pp 132.Pp
134.Bl -column -compact "Samsung SWL-5200N" "AR5212" "CardBus" "a/b/g" 133.Bl -column -compact "Samsung SWL-5200N" "AR5212" "CardBus" "a/b/g"
135.Em "Card Chip Bus Standard" 134.Em "Card Chip Bus Standard"
1363Com 3CRPAG175 AR5212 CardBus a/b/g 1353Com 3CRPAG175 AR5212 CardBus a/b/g
137Airlink AWLH4030 AR5212 PCI b/g 136Airlink AWLH4030 AR5212 PCI b/g
138Aztech WL830PC AR5212 CardBus b/g 137Aztech WL830PC AR5212 CardBus b/g
139Belkin F6D3000 AR5212 PCI a/b/g 138Belkin F6D3000 AR5212 PCI a/b/g
140D-Link DWL-A520 AR5210 PCI a 139D-Link DWL-A520 AR5210 PCI a
141D-Link DWL-A650 AR5210 CardBus a 140D-Link DWL-A650 AR5210 CardBus a
142D-Link DWL-AB650 AR5211 CardBus a/b 141D-Link DWL-AB650 AR5211 CardBus a/b
143D-Link DWL-AG520 AR5212 PCI a/b/g 142D-Link DWL-AG520 AR5212 PCI a/b/g
144D-Link DWL-AG650 AR5212 CardBus a/b/g 143D-Link DWL-AG650 AR5212 CardBus a/b/g
145D-Link DWL-AG660 AR521? CardBus a/b/g 144D-Link DWL-AG660 AR521? CardBus a/b/g
146D-Link DWL-G520 AR5212 PCI b/g 145D-Link DWL-G520 AR5212 PCI b/g
147D-Link DWL-G650B AR5212 CardBus b/g 146D-Link DWL-G650B AR5212 CardBus b/g
148Elecom LD-WL54 AR5211 CardBus a 147Elecom LD-WL54 AR5211 CardBus a
149Elecom LD-WL54AG AR5212 CardBus a/b/g 148Elecom LD-WL54AG AR5212 CardBus a/b/g
150Fujitsu E5454 AR5212 CardBus a/b/g 149Fujitsu E5454 AR5212 CardBus a/b/g
151Fujitsu E5454 AR5212 CardBus a/b/g 150Fujitsu E5454 AR5212 CardBus a/b/g
152Fujitsu FMV-JW481 AR5212 CardBus a/b/g 151Fujitsu FMV-JW481 AR5212 CardBus a/b/g
153HP NC4000 AR5212 PCI a/b/g 152HP NC4000 AR5212 PCI a/b/g
154I/O Data WN-A54 AR5212 CardBus a 153I/O Data WN-A54 AR5212 CardBus a
155I/O Data WN-AB AR5212 CardBus a/b 154I/O Data WN-AB AR5212 CardBus a/b
156I/O Data WN-AG AR5212 CardBus a/b/g 155I/O Data WN-AG AR5212 CardBus a/b/g
157Linksys WMP55AG AR5212 PCI a/b/g 156Linksys WMP55AG AR5212 PCI a/b/g
158Linksys WPC51AB AR5211 CardBus a/b 157Linksys WPC51AB AR5211 CardBus a/b
159Linksys WPC55AG AR5212 CardBus a/b/g 158Linksys WPC55AG AR5212 CardBus a/b/g
160NEC PA-WL/54AG AR5212 CardBus a/b/g 159NEC PA-WL/54AG AR5212 CardBus a/b/g
161Netgear WAB501 AR5211 CardBus a/b 160Netgear WAB501 AR5211 CardBus a/b
162Netgear WAG311 AR5212 PCI a/b/g 161Netgear WAG311 AR5212 PCI a/b/g
163Netgear WAG511 AR5212 CardBus a/b/g 162Netgear WAG511 AR5212 CardBus a/b/g
164Netgear WG311 AR5212 PCI b/g 163Netgear WG311 AR5212 PCI b/g
165Netgear WG511T AR5212 CardBus b/g 164Netgear WG511T AR5212 CardBus b/g
166Orinoco 8470WD AR5212 CardBus a/b/g 165Orinoco 8470WD AR5212 CardBus a/b/g
167Orinoco 8480 AR5212 CardBus a/b/g 166Orinoco 8480 AR5212 CardBus a/b/g
168Planex GW-NS54AG AR5212 CardBus a/b/g 167Planex GW-NS54AG AR5212 CardBus a/b/g
169Proxim Skyline 4030 AR5210 CardBus a 168Proxim Skyline 4030 AR5210 CardBus a
170Proxim Skyline 4032 AR5210 PCI a 169Proxim Skyline 4032 AR5210 PCI a
171Samsung SWL-5200N AR5212 CardBus a/b/g 170Samsung SWL-5200N AR5212 CardBus a/b/g
172SMC SMC2735W AR5210 CardBus a 171SMC SMC2735W AR5210 CardBus a
173Sony PCWA-C300S AR5212 CardBus b/g 172Sony PCWA-C300S AR5212 CardBus b/g
174Sony PCWA-C500 AR5210 CardBus a 173Sony PCWA-C500 AR5210 CardBus a
175Sony PCWA-C700 AR5212 CardBus a/b 174Sony PCWA-C700 AR5212 CardBus a/b
176Ubiquiti SRC AR5213 CardBus a/b/g 175Ubiquiti SRC AR5213 CardBus a/b/g
177.El 176.El
178.Pp 177.Pp
179An up to date list can be found at 178An up to date list can be found at
180.Pa http://customerproducts.atheros.com/customerproducts . 179.Pa http://customerproducts.atheros.com/customerproducts .
181.Sh DIAGNOSTICS 180.Sh DIAGNOSTICS
182.Bl -diag 181.Bl -diag
183.It "ath%d: unable to attach hardware; HAL status %u" 182.It "ath%d: unable to attach hardware; HAL status %u"
184The Atheros Hardware Access Layer was unable to configure the hardware 183The Atheros Hardware Access Layer was unable to configure the hardware
185as requested. 184as requested.
186The status code is explained in the HAL include file 185The status code is explained in the HAL include file
187.Pa contrib/sys/dev/ic/athhal.h . 186.Pa contrib/sys/dev/ic/athhal.h .
188.It "ath%d: failed to allocate descriptors: %d" 187.It "ath%d: failed to allocate descriptors: %d"
189The driver was unable to allocate contiguous memory for the transmit 188The driver was unable to allocate contiguous memory for the transmit
190and receive descriptors. 189and receive descriptors.
191This usually indicates system memory is scarce and/or fragmented. 190This usually indicates system memory is scarce and/or fragmented.
192.It "ath%d: unable to setup a data xmit queue!" 191.It "ath%d: unable to setup a data xmit queue!"
193The request to the HAL to setup the transmit queue for normal 192The request to the HAL to setup the transmit queue for normal
194data frames failed. 193data frames failed.
195This should not happen. 194This should not happen.
196.It "ath%d: unable to setup a beacon xmit queue!" 195.It "ath%d: unable to setup a beacon xmit queue!"
197The request to the HAL to setup the transmit queue for 802.11 beacon frames 196The request to the HAL to setup the transmit queue for 802.11 beacon frames
198failed. 197failed.
199This should not happen. 198This should not happen.
200.It "ath%d: 802.11 address: %s" 199.It "ath%d: 802.11 address: %s"
201The MAC address programmed in the EEPROM is displayed. 200The MAC address programmed in the EEPROM is displayed.
202.It "ath%d: hardware error; resetting" 201.It "ath%d: hardware error; resetting"
203An unrecoverable error in the hardware occurred. 202An unrecoverable error in the hardware occurred.
204Errors of this sort include unrecoverable DMA errors. 203Errors of this sort include unrecoverable DMA errors.
205The driver will reset the hardware and continue. 204The driver will reset the hardware and continue.
206.It "ath%d: rx FIFO overrun; resetting" 205.It "ath%d: rx FIFO overrun; resetting"
207The receive FIFO in the hardware overflowed before the data could be 206The receive FIFO in the hardware overflowed before the data could be
208transferred to the host. 207transferred to the host.
209This typically occurs because the hardware ran short of receive 208This typically occurs because the hardware ran short of receive
210descriptors and had no place to transfer received data. 209descriptors and had no place to transfer received data.
211The driver will reset the hardware and continue. 210The driver will reset the hardware and continue.
212.It "ath%d: unable to reset hardware; hal status %u" 211.It "ath%d: unable to reset hardware; hal status %u"
213The Atheros Hardware Access Layer was unable to reset the hardware 212The Atheros Hardware Access Layer was unable to reset the hardware
214as requested. 213as requested.
215The status code is explained in the HAL include file 214The status code is explained in the HAL include file
216.Pa contrib/sys/dev/ic/athhal.h . 215.Pa contrib/sys/dev/ic/athhal.h .
217This should not happen. 216This should not happen.
218.It "ath%d: unable to start recv logic" 217.It "ath%d: unable to start recv logic"
219The driver was unable to restart frame reception. 218The driver was unable to restart frame reception.
220This should not happen. 219This should not happen.
221.It "ath%d: device timeout" 220.It "ath%d: device timeout"
222A frame dispatched to the hardware for transmission did not complete in time. 221A frame dispatched to the hardware for transmission did not complete in time.
223The driver will reset the hardware and continue. 222The driver will reset the hardware and continue.
224This should not happen. 223This should not happen.
225.It "ath%d: bogus xmit rate 0x%x" 224.It "ath%d: bogus xmit rate 0x%x"
226An invalid transmit rate was specified for an outgoing frame. 225An invalid transmit rate was specified for an outgoing frame.
227The frame is discarded. 226The frame is discarded.
228This should not happen. 227This should not happen.
229.It "ath%d: ath_chan_set: unable to reset channel %u (%u MHz)" 228.It "ath%d: ath_chan_set: unable to reset channel %u (%u MHz)"
230The Atheros Hardware Access Layer was unable to reset the hardware 229The Atheros Hardware Access Layer was unable to reset the hardware
231when switching channels during scanning. 230when switching channels during scanning.
232This should not happen. 231This should not happen.
233.It "ath%d: unable to allocate channel table" 232.It "ath%d: unable to allocate channel table"
234The driver was unable to allocate memory for the table used to hold 233The driver was unable to allocate memory for the table used to hold
235the set of available channels. 234the set of available channels.
236.It "ath%d: unable to collect channel list from hal" 235.It "ath%d: unable to collect channel list from hal"
237A problem occurred while querying the HAL to find the set of available 236A problem occurred while querying the HAL to find the set of available
238channels for the device. 237channels for the device.
239This should not happen. 238This should not happen.
240.It "ath%d: %s: %dM -\*[Gt] %dM (%d ok, %d err, %d retr)" 239.It "ath%d: %s: %dM -\*[Gt] %dM (%d ok, %d err, %d retr)"
241The driver's rate control algorithm changed the current rate for transmitting 240The driver's rate control algorithm changed the current rate for transmitting
242frames. 241frames.
243This message is temporarily enabled for normal use to help in diagnosing 242This message is temporarily enabled for normal use to help in diagnosing
244and improving the rate control algorithm. 243and improving the rate control algorithm.
245The message indicates the new and old transmit rates and the statistics 244The message indicates the new and old transmit rates and the statistics
246it used to decide on this change. 245it used to decide on this change.
247.It "ath%d: failed to enable memory mapping" 246.It "ath%d: failed to enable memory mapping"
248The driver was unable to enable memory-mapped I/O to the PCI device registers. 247The driver was unable to enable memory-mapped I/O to the PCI device registers.
249This should not happen. 248This should not happen.
250.It "ath%d: failed to enable bus mastering" 249.It "ath%d: failed to enable bus mastering"
251The driver was unable to enable the device as a PCI bus master for doing DMA. 250The driver was unable to enable the device as a PCI bus master for doing DMA.
252This should not happen. 251This should not happen.
253.It "ath%d: cannot map register space" 252.It "ath%d: cannot map register space"
254The driver was unable to map the device registers into the host address space. 253The driver was unable to map the device registers into the host address space.
255This should not happen. 254This should not happen.
256.It "ath%d: could not map interrupt" 255.It "ath%d: could not map interrupt"
257The driver was unable to allocate an IRQ for the device interrupt. 256The driver was unable to allocate an IRQ for the device interrupt.
258This should not happen. 257This should not happen.
259.It "ath%d: could not establish interrupt" 258.It "ath%d: could not establish interrupt"
260The driver was unable to install the device interrupt handler. 259The driver was unable to install the device interrupt handler.
261This should not happen. 260This should not happen.
262.El 261.El
263.Sh SEE ALSO 262.Sh SEE ALSO
264.Xr arp 4 , 263.Xr arp 4 ,
265.Xr cardbus 4 , 264.Xr cardbus 4 ,
266.Xr ifmedia 4 , 265.Xr ifmedia 4 ,
267.Xr netintro 4 , 266.Xr netintro 4 ,
268.Xr pci 4 , 267.Xr pci 4 ,
269.Xr ifconfig 8 268.Xr ifconfig 8
270.Sh HISTORY 269.Sh HISTORY
271The 270The
272.Nm 271.Nm
273device driver first appeared in 272device driver first appeared in
274.Fx 5.2 . 273.Fx 5.2 .
275It was ported to 274It was ported to
276.Nx 2.0 . 275.Nx 2.0 .
277.Sh AUTHORS 276.Sh AUTHORS
278.An -nosplit 277.An -nosplit
279The 278The
280.Nm 279.Nm
281driver was originally written by 280driver was originally written by
282.An Sam Leffler , 281.An Sam Leffler ,
283and was ported to 282and was ported to
284.Nx 283.Nx
285by 284by
286.An David Young . 285.An David Young .
287.Sh CAVEATS 286.Sh CAVEATS
288Different regulatory domains have different default channels for adhoc 287Different regulatory domains have different default channels for adhoc
289mode. 288mode.
290See 289See
291.Xr ifconfig 8 290.Xr ifconfig 8
292for information on how to change the channel. 291for information on how to change the channel.
293Different regulatory domains may not be able to communicate with each 292Different regulatory domains may not be able to communicate with each
294other with 802.11a as different regulatory domains do not necessarily 293other with 802.11a as different regulatory domains do not necessarily
295have overlapping channels. 294have overlapping channels.
296.Pp 295.Pp
297Revision A1 of the D-LINK DWL-G520 and DWL-G650 are based on an 296Revision A1 of the D-LINK DWL-G520 and DWL-G650 are based on an
298Intersil PrismGT chip and are not supported by this driver. 297Intersil PrismGT chip and are not supported by this driver.
299.Pp 298.Pp
300Revision v2 of the Netgear WG311 is based on a Texas Instruments ACX111 299Revision v2 of the Netgear WG311 is based on a Texas Instruments ACX111
301and is not supported by this driver. 300and is not supported by this driver.
302.Pp 301.Pp
303Revision v3 of the Netgear WG311 is based on a Marvell Libertas 302Revision v3 of the Netgear WG311 is based on a Marvell Libertas
30488W8335 and is not supported by this driver. 30388W8335 and is not supported by this driver.
305.Pp 304.Pp
306The HAL module is constructed from a binary component and 305The HAL module is constructed from a binary component and
307operating system-dependent source code. 306operating system-dependent source code.
308Redistribution and use in source and binary forms, without 307Redistribution and use in source and binary forms, without
309modification, are permitted provided that the conditions 308modification, are permitted provided that the conditions
310set forth in 309set forth in
311.Pa src/contrib/sys/dev/ic/athhal-COPYRIGHT 310.Pa src/contrib/sys/dev/ic/athhal-COPYRIGHT
312are observed. 311are observed.
313.Sh BUGS 312.Sh BUGS
314Performance in lossy environments is suboptimal. 313Performance in lossy environments is suboptimal.
315The algorithm used to select the rate for transmitted packets is 314The algorithm used to select the rate for transmitted packets is
316very simplistic. 315very simplistic.
317There is no software retransmit; only hardware retransmit is used. 316There is no software retransmit; only hardware retransmit is used.
318Contributors are encouraged to replace the existing rate control algorithm 317Contributors are encouraged to replace the existing rate control algorithm
319with a better one (hint: all the information needed is available to the driver). 318with a better one (hint: all the information needed is available to the driver).
320.Pp 319.Pp
321The driver does not fully enable power-save operation of the chip; 320The driver does not fully enable power-save operation of the chip;
322consequently power use is suboptimal. 321consequently power use is suboptimal.