1. 18 Mar, 2013 1 commit
  2. 13 Mar, 2013 32 commits
  3. 11 Mar, 2013 7 commits
    • Sunguk Lee's avatar
      Bluetooth: Device 0cf3:3008 should map AR 3012 · 94a32d10
      Sunguk Lee authored
      T:  Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  3 Spd=12   MxCh= 0
      D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
      P:  Vendor=0cf3 ProdID=3008 Rev= 0.01
      S:  Manufacturer=Atheros Communications
      S:  Product=Bluetooth USB Host Controller
      S:  SerialNumber=Alaska Day 2006
      C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
      I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
      E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
      E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
      E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
      I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
      E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
      E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
      I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
      E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
      E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
      I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
      E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
      E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
      I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
      E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
      E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
      I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
      E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
      E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
      I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
      E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms
      E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms
      Signed-off-by: default avatarSunguk Lee <d3m3vilurr@gmail.com>
      Signed-off-by: default avatarGustavo Padovan <gustavo.padovan@collabora.co.uk>
      94a32d10
    • Jonas Gorski's avatar
      mwl8k: don't overwrite regulatory settings on fw reload · c3f251a3
      Jonas Gorski authored
      Currently the caps are parsed on every firmware reload, causing any
      channel flags to be cleared.
      When there is a firmware to interface mode mismatch, the triggered
      firmware reload causes a reset of the regulatory settings, causing all
      channels to become available:
      
      root@openrouter:/# iw phy phy0 info
      Wiphy phy0
              Band 1:
      		(...)
                      Frequencies:
                              * 2412 MHz [1] (0.0 dBm)
                              * 2417 MHz [2] (0.0 dBm)
                              * 2422 MHz [3] (0.0 dBm)
                              * 2427 MHz [4] (0.0 dBm)
                              * 2432 MHz [5] (0.0 dBm)
                              * 2437 MHz [6] (0.0 dBm)
                              * 2442 MHz [7] (0.0 dBm)
                              * 2447 MHz [8] (0.0 dBm)
                              * 2452 MHz [9] (0.0 dBm)
                              * 2457 MHz [10] (0.0 dBm)
                              * 2462 MHz [11] (0.0 dBm)
                              * 2467 MHz [12] (0.0 dBm)
                              * 2472 MHz [13] (0.0 dBm)
                              * 2484 MHz [14] (0.0 dBm)
      		(...)
      
      To prevent this, only parse the caps on the first firmware load during
      hardware probe, and store them locally to know we have already parsed
      them.
      Signed-off-by: default avatarJonas Gorski <jogo@openwrt.org>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      c3f251a3
    • Andrei Epure's avatar
    • Stephen Hemminger's avatar
      iwlegacy: fix sparse warnings · 60c46bf8
      Stephen Hemminger authored
      Make local functions and tables static. Make ops table
      Mark 3945 ops as read_mostly.
      Signed-off-by: default avatarStephen Hemminger <stephen@networkplumber.org>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      60c46bf8
    • Michal Pecio's avatar
      orinoco_usb: don't release nonexistent firmware · 4363b577
      Michal Pecio authored
      Initialize fw_entry to NULL to prevent cleanup code from passing
      bogus pointer to release_firmware() when priv allocation fails.
      Signed-off-by: default avatarMichal Pecio <michal.pecio@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      4363b577
    • John W. Linville's avatar
      Merge tag 'nfc-next-3.10-1' of git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-next · 720d3f16
      John W. Linville authored
      Samuel Ortiz <sameo@linux.intel.com> says:
      
      This is the first NFC pull request for 3.10.
      
      The 2 features we have with this one are:
      
      - An LLCP Service Name Lookup (SNL) netlink interface for querying LLCP
        service availability from user space.
        Along the way, Thierry also improved the existing SNL interface for
        aggregating SNL responses.
      
      - An initial LLCP socket options implementation, for setting the Receive
        Window (RW) and the Maximum Information Unit Extension (MIUX) per socket.
        This is need for the LLCP validation tests.
      
      We also have a microread MEI build failure here: I am not sending this one to
      3.9 because the MEI bus code is not there yet, so it won't break for anyone
      else than me.
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      720d3f16
    • John W. Linville's avatar
      Merge tag 'nfc-fixes-3.9-1' of git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-fixes · de121989
      John W. Linville authored
      Samuel Ortiz <sameo@linux.intel.com> says:
      
      This is the first NFC pull request for 3.9 fixes
      
      With this one we have:
      
      - A fix for properly decreasing socket ack log.
      - A timer and works cleanup upon NFC device removal.
      - A monitoroing socket cleanup round from llcp_socket_release.
      - A proper error report to pending sockets upon NFC device removal.
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      de121989