src/sys/dev/bwi, branch release/8.1.0

MFC r206367, r206358, r206370, r206371, r206372, r206398, r206415,

2010-05-11T11:08:15Z

r206416, r206417, r206418, r206418: net80211 ratectl framework.

In bwi_newstate, only zero the bssid when we stop a STA. And only

2009-06-02T16:48:10Z

when we've not stopped the card. It hangs the system when we touch the CSR after bwistop. This fixes the hanging on kldunload.

Move the unlock to after the ifdef (maybe the right fix is to remove

2009-06-01T16:29:03Z

the ifdef) since it calls bwi_start_locked, which expects to the lock to be held...

Make sure that we drain the LED blinking callout on detach.

2009-06-01T16:27:13Z

Submitted by: Paul B. Mahol

Add a comment about what may be happening when we get certain

2009-06-01T16:22:01Z

messages. No change to actual code.

fix typo

2009-05-30T01:33:05Z

validate tx rate(s) in the raw xmit path

2009-05-29T23:41:31Z

Tested by: "Paul B. Mahol" (rum, bwi)

Overhaul monitor mode handling:

2009-05-20T20:00:40Z

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

Remove unnecessary comments. 11A read/write is the same: its just the

2009-05-18T15:46:34Z

classic indirect register dance. Submitted by: ddkprog at yahoo not com

Fix a typo from the original driver. We need to write ctrl2 into RF

2009-05-18T15:31:26Z

register 0x52, not ctrl1. This appears to be a mistake in the bcm reverse engineering page, and has been corrected there. Tracing through the code, this is more in keeping with the "documented" register. Sephe thinks it looks interesting and may be worth fixing. :) Submitted by: ddkprog at yahoo com Reviewed by: Sepherosa Ziehau