Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Don't use BUS_DMA_ALLOCNOW as that causes the attachment to fail on | rpaulo | 2009-10-22 | 1 | -1/+1 |
| | | | | | | Cambria boards. MFC after: 2 months | ||||
* | Replace 'can not' with 'cannot' so that we use 'cannot' everywhere. | rpaulo | 2009-09-23 | 1 | -1/+1 |
| | |||||
* | Call mwl_rxdma_cleanup() if there was an error setting up the RX DMA. | rpaulo | 2009-09-18 | 1 | -1/+3 |
| | |||||
* | must also plumb static wep keys to the local sta db in sta mode; not | sam | 2009-09-04 | 1 | -0/+4 |
| | | | | | | | sure when this became necessary and might be caused by some missing code to do auto-configuration of DWDS usage Noticed by: Felix Feng <unixwind@gmail.com> | ||||
* | Implementation of the upcoming Wireless Mesh standard, 802.11s, on the | rpaulo | 2009-07-11 | 1 | -4/+13 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | net80211 wireless stack. This work is based on the March 2009 D3.0 draft standard. This standard is expected to become final next year. This includes two main net80211 modules, ieee80211_mesh.c which deals with peer link management, link metric calculation, routing table control and mesh configuration and ieee80211_hwmp.c which deals with the actually routing process on the mesh network. HWMP is the mandatory routing protocol on by the mesh standard, but others, such as RA-OLSR, can be implemented. Authentication and encryption are not implemented. There are several scripts under tools/tools/net80211/scripts that can be used to test different mesh network topologies and they also teach you how to setup a mesh vap (for the impatient: ifconfig wlan0 create wlandev ... wlanmode mesh). A new build option is available: IEEE80211_SUPPORT_MESH and it's enabled by default on GENERIC kernels for i386, amd64, sparc64 and pc98. Drivers that support mesh networks right now are: ath, ral and mwl. More information at: http://wiki.freebsd.org/WifiMesh Please note that this work is experimental. Also, please note that bridging a mesh vap with another network interface is not yet supported. Many thanks to the FreeBSD Foundation for sponsoring this project and to Sam Leffler for his support. Also, I would like to thank Gateworks Corporation for sending me a Cambria board which was used during the development of this project. Reviewed by: sam Approved by: re (kensmith) Obtained from: projects/mesh11s | ||||
* | Revamp 802.11 action frame handling: | sam | 2009-07-05 | 2 | -5/+9 |
| | | | | | | | | | | | | | | o add a new facility for components to register send+recv handlers o ieee80211_send_action and ieee80211_recv_action now use the registered handlers to dispatch operations o rev ieee80211_send_action api to enable passing arbitrary data o rev ieee80211_recv_action api to pass the 802.11 frame header as it may be difficult to locate o update existing IEEE80211_ACTION_CAT_BA and IEEE80211_ACTION_CAT_HT handling o update mwl for api rev Reviewed by: rpaulo Approved by: re (kensmith) | ||||
* | Update to 3.6.2.2 firmware (latest w/o host-based power save support): | sam | 2009-06-29 | 5 | -130/+292 |
| | | | | | | | | | | | o new tx ack queue (not used right now) o proxy-sta related changes (no proxy sta in driver) o explicit dwds ena/dis (needed only with proxy sta) o cleanup BA policy handling o new ampdu aggressive mode support o CFEnd use now controllable Approved by: re (kensmith) | ||||
* | track HT flags move to iv_flags_ht | sam | 2009-06-07 | 1 | -7/+7 |
| | |||||
* | driver for Marvell 88W8363 Wireless LAN controller | sam | 2009-06-01 | 8 | -0/+10625 |