FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F8.1.0 2009-06-26T11:45:06Z 2009-06-26T11:45:06Z Robert Watson rwatson@FreeBSD.org 2009-06-26T11:45:06Z urn:sha1:eb956cd041f956275522092d6ba66671356ff84f IF_ADDR_UNLOCK() across network device drivers when accessing the per-interface multicast address list, if_multiaddrs. This will allow us to change the locking strategy without affecting our driver programming interface or binary interface. For two wireless drivers, remove unnecessary locking, since they don't actually access the multicast address list. Approved by: re (kib) MFC after: 6 weeks 2009-06-11T17:14:28Z Andriy Gapon avg@FreeBSD.org 2009-06-11T17:14:28Z urn:sha1:c0e55e3b65ffb5b5aa0f4c0f76f4ed62c6d25993 with common issue of having void return type instead of int Reviewed by: imp, current@ Approved by: jhb (mentor) 2009-05-21T04:00:31Z Sam Leffler sam@FreeBSD.org 2009-05-21T04:00:31Z urn:sha1:c3e8a587239e9b925acbef2f0a89ef3b5f4b881b 2009-05-20T22:28:55Z Warner Losh imp@FreeBSD.org 2009-05-20T22:28:55Z urn:sha1:68fc5ce70be924d656e19ec679f3c19a4b90dc7c 2009-05-20T20:00:40Z Sam Leffler sam@FreeBSD.org 2009-05-20T20:00:40Z urn: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 2009-05-20T17:29:21Z Warner Losh imp@FreeBSD.org 2009-05-20T17:29:21Z urn:sha1:00b4e54ae7b69db140f2168049138a443fd3190f 2009-05-02T15:14:18Z Andrew Thompson thompsa@FreeBSD.org 2009-05-02T15:14:18Z urn: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 2009-03-30T21:53:27Z Sam Leffler sam@FreeBSD.org 2009-03-30T21:53:27Z urn: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 2009-03-30T21:29:25Z Sam Leffler sam@FreeBSD.org 2009-03-30T21:29:25Z urn:sha1:cf1c8d5f9c2c703715953cffdce44eb2769cbbb1 2009-03-29T17:59:14Z Sam Leffler sam@FreeBSD.org 2009-03-29T17:59:14Z urn: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