提交 · f99725777e0f57e71f37191eee5f10071ed7b423 · openanolis / cloud-kernel

25 1月, 2012 40 次提交

ath5k: claim support for IBSS RSN · f9972577

由 Antonio Quartulli 提交于 1月 14, 2012

Disable group keys programming when using IBSS RSN. Keys will be managed using
software. In this way IBSS RSN can correctly work.
Signed-off-by: NAntonio Quartulli <ordex@autistici.org>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

f9972577

carl9170: remove eeprom data injection option · 6ae4bb66

由 Christian Lamparter 提交于 1月 13, 2012

In the early days, this was a quite useful software
feature for testing different regdomains and chain
configurations without adding debugfs cruft into
the driver. Nowadays, the driver's phy code seems
to be stable and there's no need for it anymore.
Therefore I decided to removed altogether.
Signed-off-by: NChristian Lamparter <chunkeey@googlemail.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

6ae4bb66

mac80211: remove useless DA checking in ieee80211_rx_mgmt_probe_resp() · f1249700

由 Antonio Quartulli 提交于 1月 13, 2012

Actually the DA field has already been checked along the rx path (in
prepare_for_handlers()) and this check is therefore useless at this point.
Signed-off-by: NAntonio Quartulli <ordex@autistici.org>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

f1249700

mwifiex: derive priv from net_device instead of wiphy · f540f9f3

由 Yogesh Ashok Powar 提交于 1月 11, 2012

Currently mwifiex_private pointers are derived from wiphy
structures. This will always work as long as there is only
one net_device associated with one wiphy. In scenarios where
there are multiple net_devices associated with single
wiphy, one should use net_device to derive the priv.
Signed-off-by: NYogesh Ashok Powar <yogeshp@marvell.com>
Signed-off-by: NAvinash Patil <patila@marvell.com>
Signed-off-by: NBing Zhao <bzhao@marvell.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

f540f9f3

mwifiex: use bss_type and bss_num to retrieve priv · 9da9a3b2

由 Yogesh Ashok Powar 提交于 1月 11, 2012

Current implementation, for retrieving priv from adapter,
uses bss_index. In multi interface environment supporting
different types, bss_index may not be unique.

Use bss_type along with bss_num to retrieve the priv.
bss_index is removed with this change.
Signed-off-by: NYogesh Ashok Powar <yogeshp@marvell.com>
Signed-off-by: NKiran Divekar <dkiran@marvell.com>
Signed-off-by: NBing Zhao <bzhao@marvell.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

9da9a3b2

bcma: Enable logging of SPROM offset · cebcab9e

由 Larry Finger 提交于 1月 11, 2012

The SPROM location has been relocated again for some devices. This patch
will log the offset when CONFIG_BCMA_DEBUG has been selected.
Signed-off-by: NLarry Finger <Larry.Finger@lwfinger.net>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

cebcab9e

mac80211: Fix the maximum transmit power with power constraint · a48b13ac

由 Hong Wu 提交于 1月 11, 2012

The local maximum transmit power for a channel is defined as the maximum
regulatory transmission power minus the local power constraint specified
for the channel in the Power Constraint element. (7.3.2.15 IEEE80211 2007)
Signed-off-by: NHong Wu <hong.wu@dspg.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

a48b13ac

wireless: Save original maximum regulatory transmission power for the... · eccc068e

由 Hong Wu 提交于 1月 11, 2012

wireless: Save original maximum regulatory transmission power for the calucation of the local maximum transmit power

The local maximum transmit power is the maximum power a wireless device
allowed to transmit. If Power Constraint is presented, the local maximum
power equals to the maximum allowed power defined in regulatory domain
minus power constraint.

The maximum transmit power is maximum power a wireless device capable of
transmitting, and should be used in Power Capability element (7.3.2.16
IEEE802.11 2007).

The transmit power from a wireless device should not greater than the
local maximum transmit power.

The maximum transmit power was not calculated correctly in the current
Linux wireless/mac80211 when Power Constraint is presented.
Signed-off-by: NHong Wu <hong.wu@dspg.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

eccc068e

carl9170: claim to support IBSS RSN. · e2d75c13

由 Nicolas Cavallari 提交于 1月 11, 2012

On carl9170, HW encryption is disabled on IBSS; the mac80211
software-based encryption is used instead. As mac80211 supports IBSS
RSN (per-STA GTK), claim its support in the carl9170 PHY.
Signed-off-by: NNicolas Cavallari <cavallar@lri.fr>
Acked-by: NChristian Lamparter <chunkeey@googlemail.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

e2d75c13

mac80211: In IBSS the DA field of auth frames is different from BSSID · efa6a09d

由 Antonio Quartulli 提交于 1月 09, 2012

In case of authentication frame exchange between two IBSS STAs, the
DA field must contain the destinatioin address (instead of the BSSID).
Signed-off-by: NAntonio Quartulli <ordex@autistici.org>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

efa6a09d

mac80211: refactor __ieee80211_get_channel_mode · e9980e6d

由 Johannes Berg 提交于 1月 09, 2012

Use a switch statement instead of a list of if
statements. Also include AP_VLAN in the list
and skip them since the AP interface will also
be looked at.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

e9980e6d

drivers/net/wireless/mwifiex/scan.c: convert GFP_KERNEL to GFP_ATOMIC · 75ac9a28

由 Julia Lawall 提交于 1月 09, 2012

The function is called with locks held and thus should not use GFP_KERNEL.

The semantic patch that makes this report is available
in scripts/coccinelle/locks/call_kern.cocci.

More information about semantic patching is available at
http://coccinelle.lip6.fr/Signed-off-by: NJulia Lawall <julia.lawall@lip6.fr>
Acked-by: NBing Zhao <bzhao@marvell.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

75ac9a28

NFC: Increase NCI deactivate timeout · 11ee5158

由 Ilan Elias 提交于 1月 08, 2012

Increase NCI deactivate timeout from 5 sec to 30 sec.
NCI deactivate procedure might take a long time,
depending on the local and remote parameters.
Signed-off-by: NIlan Elias <ilane@ti.com>
Acked-by: NSamuel Ortiz <sameo@linux.intel.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

11ee5158

NFC: Complete NCI deactivate in deactivate_ntf · bd7e01bc

由 Ilan Elias 提交于 1月 08, 2012

If a target was active, complete the NCI deactivate request
only in deactivate_ntf. Otherwise, complete it at deactivate_rsp.
Deactivate_ntf represents the actual disconnection event (sent from
the NCI controller).
Signed-off-by: NIlan Elias <ilane@ti.com>
Acked-by: NSamuel Ortiz <sameo@linux.intel.com>
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>

bd7e01bc

rtl8192se: Update copyright dates · ca742cd9