Lines Matching +full:on +full:- +full:device
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
63 IEEE 802.11 device drivers are written to use the infrastructure provided
70 Most drivers depend on the
72 layer for protocol services but devices that off-load functionality
73 may bypass the layer to connect directly to the device.
77 device driver implements a virtual radio API that is exported to
79 underlying device.
97 and device.
131 detachment on behalf of the caller.
181 functions are device-independent handlers for
206 sub-type, for the device
215 sub-type.
218 The virtual radio architecture splits state between a single per-device
224 at device attach and during vap creation but otherwise should treat them
225 as read-only.
230 layer as adjunct data to a device's
240 and should be extended with any driver-private state.
244 data structures and should be exploited to maintain driver-private state
255 Long-lasting references to a node are counted to guard against
258 (either explicitly for transmit or implicitly on receive).
265 fill-in and/or override to take control of certain operations.
275 The driver is expected to allocate and setup any device-private
279 structure must be pre-initialized with state required to setup the
282 .Bl -tag -width ic_channels
284 Backpointer to the physical device's ifnet.
286 Device/driver capabilities; see below for a complete description.
288 Table of channels the device is capable of operating on.
304 .Bl -tag -width ic_channels
308 Drivers that support multi-bssid operation may honor the requested BSSID
331 The default method drops the frame and generates a message on the console.
343 Update driver/device state for association to a new AP (in station mode)
385 The default method ages frames on the power-save queue (in AP mode)
386 and pending frames in the receive reorder queues (for stations using A-MPDU).
424 Start scanning on a channel.
433 Drivers that off-load scan work to firmware typically use this method
434 to trigger per-channel scan activity.
436 Handle reaching the minimum dwell time on a channel when scanning.
437 This event is triggered when one or more stations have been found on
456 Check if transmit A-MPDU should be enabled for the specified station and AC.
457 The default method checks a per-AC traffic rate against a per-vap
458 threshold to decide if A-MPDU should be enabled.
459 This method also rate-limits ADDBA requests so that requests are not
462 Request A-MPDU transmit aggregation.
466 for handling transmit A-MPDU.
469 needed for doing transmit A-MPDU.
471 Shutdown an A-MPDU transmit stream for the specified station and AC.
476 Prepare to receive A-MPDU data from the specified station for the TID.
478 Terminate receipt of A-MPDU data from the specified station for the TID.
485 .Bl -enum
489 for capturing raw 802.11 packets that pass through the device.
493 Do any final device setup like enabling interrupts.
504 worry about being re-entered.
507 on the ifnet it allocated for the physical device.
509 Driver/device capabilities are specified using several sets of flags
530 .Bl -tag -width IEEE80211_C_8023ENCAP
532 Device is capable of operating in station (aka Infrastructure) mode.
534 Device requires 802.3-encapsulated frames be passed for transmit.
539 Device supports Atheros Fast-Frames.
541 Device supports Atheros Dynamic Turbo mode.
543 Device is capable of operating in adhoc/IBSS mode.
545 Device supports dynamic power-management (aka power save) in station mode.
547 Device is capable of operating as an Access Point in Infrastructure mode.
549 Device is capable of operating in Adhoc Demo mode.
550 In this mode the device is used purely to send/receive raw 802.11 frames.
552 Device supports software retry of transmitted frames.
554 Device support dynamic transmit power changes on transmitted frames;
557 Device supports short slot time operation (for 802.11g).
559 Device supports short preamble operation (for 802.11g).
561 Device is capable of operating in monitor mode.
563 Device supports radar detection and/or DFS.
566 but the device must be capable of detecting radar events.
568 Device is capable of operating in MeshBSS (MBSS) mode
571 Device supports WPA1 operation.
573 Device supports WPA2/802.11i operation.
575 Device supports frame bursting.
577 Device supports WME/WMM operation
581 Device supports transmit/receive of 4-address frames.
583 Device supports background scanning.
585 Device supports transmit of fragmented 802.11 frames.
587 Device is capable of operating in TDMA mode.
593 will fall-back to software support when a device is not capable
595 This can be done on a per-key basis.
602 .Bl -tag -width IEEE80211_C_8023ENCAP
604 Device supports hardware WEP cipher.
606 Device supports hardware TKIP cipher.
608 Device supports hardware AES-OCB cipher.
610 Device supports hardware AES-CCM cipher.
612 Device supports hardware Michael for use with TKIP.
623 .Bl -tag -width IEEE80211_C_8023ENCAP
625 Device supports 20/40 channel width operation.
627 Device supports dynamic SM power save operation.
629 Device supports static SM power save operation.
631 Device supports Greenfield preamble.
633 Device supports Short Guard Interval on 20MHz channels.
635 Device supports Short Guard Interval on 40MHz channels.
637 Device supports Space Time Block Convolution (STBC) for transmit.
639 Device supports 1 spatial stream for STBC receive.
641 Device supports 1-2 spatial streams for STBC receive.
643 Device supports 1-3 spatial streams for STBC receive.
645 Device supports A-MSDU frames up to 7935 octets.
647 Device supports A-MSDU frames up to 3839 octets.
649 Device supports use of DSSS/CCK on 40MHz channels.
651 Device supports PSMP.
653 Device is intolerant of 40MHz wide channel use.
655 Device supports L-SIG TXOP protection.
657 Device supports A-MPDU aggregation.
658 Note that any 802.11n compliant device must support A-MPDU receive
661 of A-MPDU frames.
663 Device supports A-MSDU aggregation.
664 Note that any 802.11n compliant device must support A-MSDU receive
667 of A-MSDU frames.
669 Device supports High Throughput (HT) operation.
674 Device supports MIMO Power Save operation.
676 Device supports Reduced Inter Frame Spacing (RIFS).
707 .An -nosplit