- Jul 19, 2014
-
-
Rafał Miłecki authored
This is needed to properly handle early 802.11n devices like BCM4321. Signed-off-by:
Rafał Miłecki <zajec5@gmail.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Vladimir Kondratiev authored
New register area defined in the firmware Signed-off-by:
Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com> Signed-off-by:
-
Vladimir Kondratiev authored
Firmware sets this register with the offset of the firmware trace area within the peripheral memory region. Critical for the firmware trace to work Signed-off-by:
-
Vladimir Kondratiev authored
Use single data source for all information regarding the firmware memory map. With this change "ucode_xxx" regions disappears since they are in fact part of larger "upper area" region Signed-off-by:
-
Vladimir Kondratiev authored
If copy_from_user() fails, buffer allocated for parameters would leak Signed-off-by:
-
Vladimir Kondratiev authored
Variable 'ctx' declarad again in the inner loop. Should use one from outer loop instead. Signed-off-by:
-
Vladimir Kondratiev authored
Signed-off-by:
-
Vladimir Kondratiev authored
New hardware release appears; it require some changes to properly support it. Introduce struct wil_board and "board" attribute in wil6210_priv; keep hardware variant information in this structure. fill it on probe(). Used in the reset flow. Signed-off-by:
-
-
John W. Linville authored
Merge branch 'for-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next
-
- Jul 16, 2014
-
-
Bing Zhao authored
The unwanted frame types are already handled in 'default' case of the switch/case below. The str_ptr is allocated but it can be leaked if the length check fails in the REQUEST/RESP cases. Fix it by allocating sta_ptr after the length checks. Reported-by:
Paul Stewart <pstew@chromium.org> Signed-off-by:
Bing Zhao <bzhao@marvell.com> Signed-off-by:
Avinash Patil <patila@marvell.com> Signed-off-by:
-
Rafał Miłecki authored
They are encoded the same way as in older SPROMs. Signed-off-by:
-
Rafał Miłecki authored
Signed-off-by:
-
Xose Vazquez Perez authored
Cc: Daniel Drake <dsd@laptop.org> Cc: Ulrich Kunitz <kune@deine-taler.de> Cc: John W. Linville <linville@tuxdriver.com> Cc: linux-wireless@vger.kernel.org Signed-off-by:
Xose Vazquez Perez <xose.vazquez@gmail.com> Signed-off-by:
-
Rafał Miłecki authored
Signed-off-by:
-
Arend van Spriel authored
The function brcmf_p2p_detach() was only called in error flow of the brcmf_cfg80211_attach() routine, but it also needs to be called upon brcmf_cfg80211_detach(). Reviewed-by:
Hante Meuleman <meuleman@broadcom.com> Reviewed-by:
Pieter-Paul Giesberts <pieterpg@broadcom.com> Signed-off-by:
Arend van Spriel <arend@broadcom.com> Signed-off-by:
-
Arend van Spriel authored
Instead of waiting for IFF_UP of the primary net device to determine the band and channel information of the wiphy structure, this is now done during driver initialization in brcmf_cfg80211_attach(). The channel information is obtained from the device and the 2G band is updated when 40MHz bandwidth is enabled for that band. Before this change the band and channel objects were common between multiple brcmfmac devices in the system, which make that information rather unreliable. That is also fixed with this reworked implementation. Reviewed-by:
Franky (Zhenhui) Lin <frankyl@broadcom.com> Reviewed-by:
Daniel (Deognyoun) Kim <dekim@broadcom.com> Signed-off-by:
-
Arend van Spriel authored
Just reordering the functions in preparation of subsequent changes. Signed-off-by:
-
Arend van Spriel authored
Introducing a new source module that will be responsible for identifying features and quirks related to the device being handled. Reviewed-by:
-
Arend van Spriel authored
Preparing for another patch move the functions in separate commit. Reviewed-by:
-
Daniel Kim authored
This patch makes firmware path a module parameter so that firmware and nvram files can be loaded from the specified path. Signed-off-by:
-
Arend van Spriel authored
Reworked the debugfs functions in the driver making it easier for other driver parts to add a debugfs entry and keeping the information they want to expose in debugfs private, ie. not in a header. This is accomplished by providing the function brcmf_debugfs_add_entry() in which the caller provides a read function in which they provide the content. The debugfs function will take care of creating the debugfs entry and cleaning up upon removal. Reviewed-by:
-
Arend van Spriel authored
The use of seq_file simplifies the debugfs code. Simpler is better. Reviewed-by:
-
Hante Meuleman authored
This patch cleans up used broadcom IDs, device IDs for all the bus layers and uses consistent naming for all IDs. Reviewed-by:
-
Bing Zhao authored
This patch fixes this typo. Reported-by:
-
Bing Zhao authored
sta_ptr is used only in an 'if' branch in this function. Move it to the smaller scope where it is used. Reported-by:
-
Bing Zhao authored
The unit of this timeout is in seconds. Reported-by:
-
Bing Zhao authored
The 'else if' branch never gets the chance as its condition matches 'if' branch's. Reported-by:
David Binderman <dcb314@hotmail.com> Signed-off-by:
Amitkumar Karwar <akarwar@marvell.com> Signed-off-by:
-
Amitkumar Karwar authored
Sometimes pending internal scan commands are delayed to give preference to Tx traffic. 'scan_processing' flag has been checked at the beginning of delay timer routine to know if in the meantime scan operation has been cancelled. There is a corner case where pending scan commands are emptied after scan_processing flag check is passed. In this case wrong pointer returned by list_first_entry() is passed to list_del() which causes system hang. This patch fixes the issue by adding list_empty() check. Signed-off-by:
-
Amitkumar Karwar authored
This patch fixes a bug in which rx_reorder_tbl_ptr is accessed without holding spinlock at few places. Signed-off-by:
-
Xose Vazquez Perez authored
0x0b05 0x17e8 RT5372 USB 2.0 bgn 2x2 ASUS USB-N14 0x0411 0x0253 RT5572 USB 2.0 abgn 2x2 BUFFALO WLP-U2-300D 0x0df6 0x0078 RT???? Sitecom N300 Cc: Ivo van Doorn <IvDoorn@gmail.com> Cc: Helmut Schaa <helmut.schaa@googlemail.com> Cc: John W. Linville <linville@tuxdriver.com> Cc: users@rt2x00.serialmonkey.com Cc: linux-wireless@vger.kernel.org Signed-off-by:
-
Eliad Peller authored
The *_bit operations expect unsigned longs. Instead of casting the pointers, simply define various bitmaps as unsigned long (instead of u32). Signed-off-by:
Eliad Peller <eliad@wizery.com> Signed-off-by:
-
Eliad Peller authored
In some corner cases with specific timings, we might try dequeueing tx before we got information about the link status (e.g. due to recovery during tx). Instead of NULL dereference, assume all the links in this case have low priorities. Signed-off-by:
-
Arik Nemtsov authored
Each 18xx chip contains only 2 real MAC addresses usable for WLAN, forcing us to use the LAA bit approach to obtain a third MAC address. Signed-off-by:
Arik Nemtsov <arik@wizery.com> Signed-off-by:
-
Arik Nemtsov authored
Sending the FW a channel switch command on a disconnected vif may result in a beacon loss event. Avoid this corner case. Signed-off-by:
-
Eliad Peller authored
All the smart config code is in place now, so register the relevant vendor commands. Signed-off-by:
-
Eliad Peller authored
we don't have any actual limitation in the driver, so increase it arbitrarily to 30 seconds. The long ROC is needed for the smart config.flow. Signed-off-by:
-
Eliad Peller authored
add defintions and handling for smart config events (SMART_CONFIG_SYNC_EVENT_ID and SMART_CONFIG_DECODE_EVENT_ID) parse the relevant info and send it to userspace as vendor event. Signed-off-by:
-
Eliad Peller authored
userspace can ask to perform various smart config actions via custom vendor commands. Signed-off-by:
-
Eliad Peller authored
These commands configures the fw to set key, enter smart config mode, and exit it. Add relevant hw ops as well. Signed-off-by:
-
