1. 23 7月, 2013 5 次提交
    • L
      ath: wil6210: Fix build error · 5d21608a
      Larry Finger 提交于
      Building driver wil6210 in 3.10 and 3.11 kernels yields the following errors:
      
        CC [M]  drivers/net/wireless/ath/wil6210/debugfs.o
      drivers/net/wireless/ath/wil6210/debugfs.c: In function 'wil_print_ring':
      drivers/net/wireless/ath/wil6210/debugfs.c:163:11: error: pointer targets in passing argument 5 of 'hex_dump_to_buffer' differ in signedness [-Werror=pointer-sign]
                 false);
                 ^
      In file included from include/linux/kernel.h:13:0,
                       from include/linux/cache.h:4,
                       from include/linux/time.h:4,
                       from include/linux/stat.h:18,
                       from include/linux/module.h:10,
                       from drivers/net/wireless/ath/wil6210/debugfs.c:17:
      include/linux/printk.h:361:13: note: expected 'char *' but argument is of type 'unsigned char *'
       extern void hex_dump_to_buffer(const void *buf, size_t len,
                   ^
      drivers/net/wireless/ath/wil6210/debugfs.c: In function 'wil_txdesc_debugfs_show':
      drivers/net/wireless/ath/wil6210/debugfs.c:429:10: error: pointer targets in passing argument 5 of 'hex_dump_to_buffer' differ in signedness [-Werror=pointer-sign]
                sizeof(printbuf), false);
                ^
      In file included from include/linux/kernel.h:13:0,
                       from include/linux/cache.h:4,
                       from include/linux/time.h:4,
                       from include/linux/stat.h:18,
                       from include/linux/module.h:10,
                       from drivers/net/wireless/ath/wil6210/debugfs.c:17:
      include/linux/printk.h:361:13: note: expected 'char *' but argument is of type 'unsigned char *'
       extern void hex_dump_to_buffer(const void *buf, size_t len,
                   ^
      cc1: all warnings being treated as errors
      make[5]: *** [drivers/net/wireless/ath/wil6210/debugfs.o] Error 1
      make[4]: *** [drivers/net/wireless/ath/wil6210] Error 2
      make[3]: *** [drivers/net/wireless/ath] Error 2
      make[2]: *** [drivers/net/wireless] Error 2
      make[1]: *** [drivers/net] Error 2
      make: *** [drivers] Error 2
      
      These errors are fixed by changing the type of the buffer from "unsigned char *" to "char *".
      Reported-by: NThomas Fjellstrom <thomas@fjellstrom.ca>
      Tested-by: NThomas Fjellstrom <thomas@fjellstrom.ca>
      Signed-off-by: NLarry Finger <Larry.Finger@lwfinger.net>
      Cc: Stable <stable@vger.kernel.org>  [3.10]
      Cc: Thomas Fjellstrom <thomas@fjellstrom.ca>
      Signed-off-by: NVladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      5d21608a
    • S
      cw1200: Fix OOPS in monitor mode · 16ec75b5
      Solomon Peachy 提交于
      In monitor mode, priv->vif is NULL, but at one point in the receive path we
      blindly attempt to dereference it.  Add a test to prevent this.
      Signed-off-by: NSolomon Peachy <pizza@shaftnet.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      16ec75b5
    • O
      ath9k_htc: reboot firmware if it was loaded · 4928bd2e
      Oleksij Rempel 提交于
      Currently ath9k_htc will reboot firmware only if interface was
      ever started. Which lead to the problem in case where interface
      was never started but module need to be reloaded.
      
      This patch will partially fix bug "ath9k_htc: Target is unresponsive"
      https://github.com/qca/open-ath9k-htc-firmware/issues/1
      
      Reproduction case:
      - plug adapter
      - make sure nothing will touch it. Stop Networkmanager or blacklist mac address of this adapter.
      - rmmod ath9k_htc; sleep 1; modprobe ath9k_htc
      Signed-off-by: NOleksij Rempel <linux@rempel-privat.de>
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      4928bd2e
    • O
      ath9k_htc: do some initial hardware configuration · dc2a87f5
      Oleksij Rempel 提交于
      Currently we configure harwdare and clock, only after
      interface start. In this case, if we reload module or
      reboot PC without configuring adapter, firmware will freeze.
      There is no software way to reset adpter.
      
      This patch add initial configuration and set it in
      disabled state, to avoid this freeze. Behaviour of this patch
      should be similar to: ifconfig wlan0 up; ifconfig wlan0 down.
      
      Bug: https://github.com/qca/open-ath9k-htc-firmware/issues/1Tested-by: NBo Shi <cnshibo@gmail.com>
      Signed-off-by: NOleksij Rempel <linux@rempel-privat.de>
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      dc2a87f5
    • D
      mwifiex: fix IRQ enable/disable · 232fde06
      Daniel Drake 提交于
      During tear down (e.g. mwifiex_sdio_remove during system suspend),
      mwifiex left IRQs enabled for a significant period of time when it was
      unable to handle them correctly. This caused interrupt storms and
      interfered with the bluetooth interface on the same SDIO card.
      
      Solve this by disabling interrupts at the point when they can no longer
      be handled correctly, which is at the start of mwifiex_remove_card().
      
      For cleanliness, we now enable interrupts in the mwifiex_add_card() path,
      to be symmetrical with the disabling of interrupts. We also couple the
      registration of the sdio IRQ handler with the actual enable/disable of
      interrupts at the hardware level.
      
      I also removed a write to this register in mwifiex_init_sdio which seemed
      pointless and won't cause any ill effects now that we only register
      the SDIO IRQ handler when we are ready to accept interrupts.
      
      Includes some corrections from Amitkumar Karwar.
      Signed-off-by: NDaniel Drake <dsd@laptop.org>
      Acked-by: NBing Zhao <bzhao@marvell.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      232fde06
  2. 19 7月, 2013 4 次提交
    • S
      ath9k_hw: Fix multicast search for AR9002 family · 64b6f46f
      Sujith Manoharan 提交于
      The multicast search bit is disabled for the AR9003
      family, but this is required for AR9002 too. Fix this in
      the INI override routine.
      Signed-off-by: NSujith Manoharan <c_manoha@qca.qualcomm.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      64b6f46f
    • L
      rtlwifi: Fix build errors for unusual cases · 6f334c2b
      Larry Finger 提交于
      The present build configuration for the rtlwifi family of drivers will
      fail under two known conditions:
      
      (1) If rtlwifi is selected without selecting any of the dependent drivers,
          there are errors in the build.
      (2) If the PCI drivers are built into the kernel and the USB drivers are modules,
          or vice versa, there are missing globals.
      
      The first condition is fixed by never building rtlwifi unless at least one
      of the device drivers is selected. The second failure is fixed by splitting
      the PCI and USB codes out of rtlwifi, and creating their own mini drivers.
      If the drivers that use them are modules, they will also be modules.
      
      Although a number of files are touched by this patch, only Makefile and Kconfig
      have undergone significant changes. The only modifications to the other files
      were to export entry points needed by the new rtl_pci and rtl_usb units, or to
      rename two variables that had names that were likely to cause namespace collisions.
      
      Reported-by: Fengguang Wu <fengguang.wu@intel.com>  [Condition 1]
      Reported-by: Ben Hutchings <bhutchings@solarflare.com> [Condition 2]
      Signed-off-by: NLarry Finger <Larry.Finger@lwfinger.net>
      Cc: Ben Hutchings <bhutchings@solarflare.com>
      Cc: Fengguang Wu <fengguang.wu@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      6f334c2b
    • B
      ath5k: fix extra set bit in multicast mask · f287cbd0
      Bob Copeland 提交于
      Bit 32 was always set which looks to have been accidental,
      according to git history.
      Signed-off-by: NBob Copeland <me@bobcopeland.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      f287cbd0
    • G
      rt2x00: RT2X00 should depend on HAS_DMA · 6a084839
      Geert Uytterhoeven 提交于
      If NO_DMA=y:
      
      drivers/built-in.o: In function `rt2x00queue_unmap_skb':
      drivers/net/wireless/rt2x00/rt2x00queue.c:129: undefined reference to `dma_unmap_single'
      drivers/net/wireless/rt2x00/rt2x00queue.c:133: undefined reference to `dma_unmap_single'
      drivers/built-in.o: In function `rt2x00queue_map_txskb':
      drivers/net/wireless/rt2x00/rt2x00queue.c:112: undefined reference to `dma_map_single'
      drivers/net/wireless/rt2x00/rt2x00queue.c:115: undefined reference to `dma_mapping_error'
      drivers/built-in.o: In function `rt2x00queue_alloc_rxskb':
      drivers/net/wireless/rt2x00/rt2x00queue.c:93: undefined reference to `dma_map_single'
      drivers/net/wireless/rt2x00/rt2x00queue.c:95: undefined reference to `dma_mapping_error'
      Signed-off-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      Cc: linux-wireless@vger.kernel.org
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      6a084839
  3. 18 7月, 2013 3 次提交
  4. 16 7月, 2013 8 次提交
  5. 04 7月, 2013 3 次提交
  6. 29 6月, 2013 2 次提交
  7. 28 6月, 2013 15 次提交
反馈
建议
客服 返回
顶部