- 15 Nov, 2011 3 commits
-
-
Stanislaw Gruszka authored
Make code shorter. Signed-off-by:Stanislaw Gruszka <sgruszka@redhat.com>
-
Stanislaw Gruszka authored
iwl_legacy prefix result in long function names, what cause that we have frequent line split and not readable code. Also iwl_foo symbols are duplicated in iwlwifi driver, what is annoying when editing kernel tree with cscope. Signed-off-by: -
Stanislaw Gruszka authored
This is not useful. Signed-off-by:
-
- 11 Nov, 2011 37 commits
-
-
Johannes Berg authored
The warning is spurious -- if !sta we always exit without using the unassigned qos variable, and if we do find the sta we assign it. Signed-off-by:
Johannes Berg <johannes.berg@intel.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
John W. Linville authored
CC [M] drivers/net/wireless/libertas/cfg.o drivers/net/wireless/libertas/cfg.c: In function ‘lbs_ret_scan’: drivers/net/wireless/libertas/cfg.c:636:24: warning: ignoring return value of ‘cfg80211_inform_bss’, declared with attribute warn_unused_result drivers/net/wireless/libertas/cfg.c: In function ‘lbs_join_post’: drivers/net/wireless/libertas/cfg.c:1766:21: warning: ignoring return value of ‘cfg80211_inform_bss’, declared with attribute warn_unused_result Signed-off-by: -
John W. Linville authored
CC [M] drivers/net/wireless/brcm80211/brcmsmac/srom.o drivers/net/wireless/brcm80211/brcmsmac/srom.c: In function ‘_initvars_srom_pci’: drivers/net/wireless/brcm80211/brcmsmac/srom.c:641:6: warning: ‘val’ may be used uninitialized in this function Signed-off-by: -
Franky Lin authored
Referenced struct returned by cfg80211_inform_bss must be released with cfg80211_put_bss to avoid memory leak. Reviewed-by:
Arend van Spriel <arend@broadcom.com> Signed-off-by:
Franky Lin <frankyl@broadcom.com> Signed-off-by:
-
Franky Lin authored
all the devices supported or will be supported by brcmfmac do not have a PCMCIA bus core. So remove the corresponding code. Reviewed-by:
Pieter-Paul Giesberts <pieterpg@broadcom.com> Reviewed-by: Arend van Spriel <arend@broadcom.com Signed-off-by:
-
Arend van Spriel authored
In several places in dhd_sdio.c a skb packet queue was being emptied and the packets freed. This warrants to have a function in place to do this. Reviewed-by:
Alwin Beukers <alwin@broadcom.com> Signed-off-by:
-
Arend van Spriel authored
The function brcmu_pkt_buf_free_skb() was following the next pointer to free all linked packets. However, it is only called with unlinked packets so this can be removed. Reviewed-by:
-
Arend van Spriel authored
The functions brcmu_pkttotlen() is only used in brcmfmac driver so it has been moved there. It also does not use the sk_buff next pointer anymore but walks a skb queue to determine the total length. Reviewed-by:
-
Alwin Beukers authored
Combined mac configuration for promiscious mode and monitor mode, and removed unused monitor mode flag in pub structure. Reviewed-by:
-
Arend van Spriel authored
Instead of dealing with sk_buff prev pointers the queue functions now make use of the sk_buff_head functions provided by the kernel. Reported-by:
Johannes Berg <johannes@sipsolutions.net> Reviewed-by:
-
Arend van Spriel authored
The function brcmu_pkttotlen calculates the total length of a sk_buff chain following the next pointer. In brcmsmac this is not needed as in each place where it was used the provided sk_buff had a NULL pointer as next field value. Reviewed-by:
-
Franky Lin authored
sdio_chip.c is dedicated to sdio bus chip. No need to retrieve id for bus core Reviewed-by:
-
Franky Lin authored
This patch is part of the series of adding new backplane support Reviewed-by:
-
Franky Lin authored
This patch is part of the series of adding new backplane support Reviewed-by:
-
Franky Lin authored
This patch is part of the series adding new backplane support Reviewed-by:
-
Franky Lin authored
New type of backplane interconnect support is needed for bcm4330 Reviewed-by:
-
Alwin Beukers authored
Reported-by:
-
Arend van Spriel authored
The macro definition D11_PHY_HDR_LEN was defined in d11.h and pub.h. It has been removed from pub.h. Reviewed-by:
Roland Vossen <rvossen@broadcom.com> Reviewed-by:
-
Arend van Spriel authored
The brcmsmac had own definitions for the access categories. The mac80211 header provides these as well as they are used in the conf_tx callback. As the definitions did not match the driver configured the tx parameters to the wrong queue. Reviewed-by:
-
Arend van Spriel authored
There were a couple of code segments left that were placed under a macro definition that was not applicable or not used in the brcmsmac driver. These pieces of code have been removed. Reviewed-by:
-
Arend van Spriel authored
This fixes issue when using OTP memory. It was introduced by following commit: commit 028f78d4 Author: Arend van Spriel <arend@broadcom.com> Date: Fri Oct 21 16:16:35 2011 +0200 brcm80211: smac: change buffer endianess convert function interface Signed-off-by:
-
Don Fry authored
The nvm_device_type is eeprom related and does not need to be part of the iwl_priv structure. Move it and eliminate access to the iwl_priv structure. Signed-off-by:
Don Fry <donald.h.fry@intel.com> Signed-off-by:
Wey-Yi Guy <wey-yi.w.guy@intel.com> Signed-off-by:
-
Don Fry authored
Make the eeprom routines less dependent on the iwl_priv structure. Don't use the priv when bus structure is sufficient. Signed-off-by:
-
Venkataraman, Meenakshi authored
iwlwifi tries to avoid using antenna B in BT combo devices when BT is active. A bug in the rate-scaling algorithm was causing the combo device to never attempt MIMO rates. Fix the algorithm to opportunistically try MIMO rates when BT traffic is low. Signed-off-by:
Meenakshi Venkataraman <meenakshi.venkataraman@intel.com> Signed-off-by:
-
Emmanuel Grumbach authored
Users complain that the traffic gets stalled sometimes. This will allow easier debugging. Signed-off-by:
Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by:
-
Emmanuel Grumbach authored
This bit was used only once. Use IWL_DL_INFO instead. Signed-off-by:
-
Johannes Berg authored
Due to the P2P context always having the associated bit set when we got to this code, we were splitting up the remain-on-channel durations unconditionally. This isn't needed -- if the P2P context is in P2P device type mode it doesn't impose restrictions on timing to skip it in that case. Signed-off-by:
-
Johannes Berg authored
The device expects TU but we get ms, so convert. Signed-off-by:
-
Emmanuel Grumbach authored
Warning introduced by c847474b7dfdda304d0d8ffcc5a9db546b1cb3e9 iwlwifi: check status before send command Signed-off-by:
-
Wey-Yi Guy authored
Check the status before sending host command, if any of the condition match, cancel the host command before queue Signed-off-by:
-
Wey-Yi Guy authored
"echo" host command has no data, set the length to 0 Signed-off-by:
-
Wey-Yi Guy authored
The core suspend function is part of agn, iwl_mac80211 should only handle mac80211 I/F operations. Signed-off-by:
-
Wey-Yi Guy authored
The station related mac80211 callback functions should belong to _mac80211 Signed-off-by:
-
Wey-Yi Guy authored
iwlagn_mac_hw_scan should belong to _mac80211 callback. Signed-off-by:
-
Wey-Yi Guy authored
Move more mac80211 related functions to _mac80211 file Signed-off-by:
-
Johannes Berg authored
In P2P device mode, the device needs to have valid QoS parameters. We currently have those because we program parameters from any virtual interface into all contexts, but not only do we want to get rid of this -- it is also unpredictable since on the BSS context we might have any parameters, and there it might even be programmed for HT. Explicitly program default QoS parameters into the PAN context for P2P (the defaults are 11g but with QoS disabled) to make device behaviour predictable. This also helps when in a follow-up patch we will use TX QoS parameters from mac80211 only for the context they were meant for -- without this first that would completely break P2P device discovery. Signed-off-by:
-
Johannes Berg authored
Eliad added the ability to configure AC parameters per virtual interface; make use of this in iwlwifi and set the parameters in the right context. Since storage and uploading to the device is already per context, this is sufficient. Signed-off-by:
-
