src/sys/dev/ipw, branch release/8.1.0FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=release%2F8.1.02010-05-18T17:43:53ZMFC r207926:2010-05-18T17:43:53ZBernhard Schmidtbschmidt@FreeBSD.org2010-05-18T17:43:53Zurn:sha1:a6d4f1ab384825cb1e725c954cc6ebc7cafe68dd
Enable 5.5 and 11Mbit TX rates.
Reviewed by: sam
Approved by: rpaulo (mentor)
MFC r206763-206767:2010-04-30T17:08:27ZBernhard Schmidtbschmidt@FreeBSD.org2010-04-30T17:08:27Zurn:sha1:4ac642e5506bea99cacad46707641a39af201238
r206763:
Fix comment about ipw_assoc and remove some whitespaces; no functional
changes.
r206764:
Pass correct RSSI to ieee80211_input*().
r206765:
- Make ipw usable again by moving directly into ASSOC state.
- No need to manually switch to RUN state, assoc response takes care
of that.
r206766:
Use iv_appie_wpa, with this commit WPA works again.
r206767:
Remove IPW_LOCK_DECL and fix various LORs.
Approved by: rpaulo (mentor)
For ic_opmode switch cases, provide a default label with a printf saying2009-07-10T15:28:33ZRui Paulorpaulo@FreeBSD.org2009-07-10T15:28:33Zurn:sha1:820e6a1f383e0f43a4245e1275bd5e29c523b97b
this opmode is not supported.
Approved by: re (kib)
Overhaul monitor mode handling:2009-05-20T20:00:40ZSam Lefflersam@FreeBSD.org2009-05-20T20:00:40Zurn:sha1:5463c4a485ef2a317cc554b7699984484ec0983d
o replace DLT_IEEE802_11 support in net80211 with DLT_IEEE802_11_RADIO
and remove explicit bpf support from wireless drivers; drivers now
use ieee80211_radiotap_attach to setup shared data structures that
hold the radiotap header for each packet tx/rx
o remove rx timestamp from the rx path; it was used only by the tdma support
for debugging and was mostly useless due to it being 32-bits and mostly
unavailable
o track DLT_IEEE80211_RADIO bpf attachments and maintain per-vap and
per-com state when there are active taps
o track the number of monitor mode vaps
o use bpf tap and monitor mode vap state to decide when to collect radiotap
state and dispatch frames; drivers no longer explicitly directly check
bpf state or use bpf calls to tap frames
o handle radiotap state updates on channel change in net80211; drivers
should not do this (unless they bypass net80211 which is almost always
a mistake)
o update various drivers to be more consistent/correct in handling radiotap
o update ral to include TSF in radiotap'd frames
o add promisc mode callback to wi
Reviewed by: cbzimmer, rpaulo, thompsa
Abort any scan on a fatal firmware. ic_scan_curchan is overridden to perform2009-05-10T02:44:19ZAndrew Thompsonthompsa@FreeBSD.org2009-05-10T02:44:19Zurn:sha1:e1d2045e3fc583a96ccba6d0da14c26a596136ae
the scan in firmware and this relies on the firmware to wake up the scan task
on completion.
Drain the tasks before the interface stop call in case a restart was queued.2009-05-08T13:44:33ZAndrew Thompsonthompsa@FreeBSD.org2009-05-08T13:44:33Zurn:sha1:b569d2132edd3ddc62bbb4f16debb64c87965179Create a taskqueue for each wireless interface which provides a serialised2009-05-02T15:14:18ZAndrew Thompsonthompsa@FreeBSD.org2009-05-02T15:14:18Zurn:sha1:5efea30f039c48ddcdddc0d12150b656f4a2e7b8
sleepable context for net80211 driver callbacks. This removes the need for USB
and firmware based drivers to roll their own code to defer the chip programming
for state changes, scan requests, channel changes and mcast/promisc updates.
When a driver callback completes the hardware state is now guaranteed to have
been updated and is in sync with net80211 layer.
This nukes around 1300 lines of code from the wireless device drivers making
them more readable and less race prone.
The net80211 layer has been updated as follows
- all state/channel changes are serialised on the taskqueue.
- ieee80211_new_state() always queues and can now be called from any context
- scanning runs from a single taskq function and executes to completion. driver
callbacks are synchronous so the channel, phy mode and rx filters are
guaranteed to be set in hardware before probe request frames are
transmitted.
Help and contributions from Sam Leffler.
Reviewed by: sam
Drain the driver tasks on the same taskqueue in which they were enqueued.2009-04-17T16:07:13ZAndrew Thompsonthompsa@FreeBSD.org2009-04-17T16:07:13Zurn:sha1:0c512ce8eeec3f685cb9131d356a0125d5d19bb0Hoist 802.11 encapsulation up into net80211:2009-03-30T21:53:27ZSam Lefflersam@FreeBSD.org2009-03-30T21:53:27Zurn:sha1:339ccfb3918a44878a6c005a3db37155e4d1d142
o call ieee80211_encap in ieee80211_start so frames passed down to drivers
are already encapsulated
o remove ieee80211_encap calls in drivers
o fixup wi so it recreates the 802.3 head it requires from the 802.11
header contents
o move fast-frame aggregation from ath to net80211 (conditional on
IEEE80211_SUPPORT_SUPERG):
- aggregation is now done in ieee80211_start; it is enabled when the
packets/sec exceeds ieee80211_ffppsmin (net.wlan.ffppsmin) and frames
are held on a staging queue according to ieee80211_ffagemax
(net.wlan.ffagemax) to wait for a frame to combine with
- drivers must call back to age/flush the staging queue (ath does this
on tx done, at swba, and on rx according to the state of the tx queues
and/or the contents of the staging queue)
- remove fast-frame-related data structures from ath
- add ieee80211_ff_node_init and ieee80211_ff_node_cleanup to handle
per-node fast-frames state (we reuse 11n tx ampdu state)
o change ieee80211_encap calling convention to include an explicit vap
so frames coming through a WDS vap are recognized w/o setting M_WDS
With these changes any device able to tx/rx 3Kbyte+ frames can use fast-frames.
Reviewed by: thompsa, rpaulo, avatar, imp, sephe
Eliminate ic_myaddr so changing the mac address of a device works correctly:2009-03-29T17:59:14ZSam Lefflersam@FreeBSD.org2009-03-29T17:59:14Zurn:sha1:29aca940805022fa5b7d02641f5309e67ab1f765
o remove ic_myaddr from ieee80211com
o change ieee80211_ifattach to take the mac address of the physical device
and use that to setup the lladdr.
o replace all references to ic_myaddr in drivers by IF_LLADDR
o related cleanups (e.g. kill dead code)
PR: kern/133178
Reviewed by: thompsa, rpaulo