1. 22 9月, 2011 2 次提交
  2. 19 9月, 2011 1 次提交
  3. 06 9月, 2011 1 次提交
    • J
      ath6kl: Fix AP mode connect event parsing and TIM updates · 572e27c0
      Jouni Malinen 提交于
      This cleans up the connect event parsing by defining a union in
      struct wmi_connect_event to match with the three possible sets of
      fields that the target uses depending on which type of connect
      event is being indicated. In addition, two AP cases are now
      separated from ath6kl_connect_event() so that correct field names
      can be used to make it actually possible to understand what the
      code is doing.
      
      The bug hiding in the previous mess was in parsing the AID incorrectly
      when processing the new station connecting event in AP mode. The fix
      here for that is also fixing TIM updates for PS buffering to use the
      correct AID.
      Signed-off-by: NJouni Malinen <jouni@qca.qualcomm.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      572e27c0
  4. 05 9月, 2011 2 次提交
  5. 02 9月, 2011 3 次提交
  6. 01 9月, 2011 1 次提交
  7. 31 8月, 2011 6 次提交
  8. 10 8月, 2011 3 次提交
    • K
      ath6kl: fix function name conflicts with ath9k · ad226ec2
      Kalle Valo 提交于
      Stephen reported that compilation fails if both ath6kl and ath9k are
      compiled in:
      
      drivers/net/wireless/ath/ath6kl/built-in.o: In function `htc_start':
      (.opd+0x600): multiple definition of `htc_start'
      drivers/net/wireless/ath/ath9k/built-in.o:(.opd+0x3e40): first defined here
      drivers/net/wireless/ath/ath6kl/built-in.o: In function `.htc_stop':
      (.text+0x7b40): multiple definition of `.htc_stop'
      drivers/net/wireless/ath/ath9k/built-in.o:(.text+0x67b34): first defined he=
      re
      drivers/net/wireless/ath/ath6kl/built-in.o: In function `.htc_start':
      (.text+0x7d18): multiple definition of `.htc_start'
      drivers/net/wireless/ath/ath9k/built-in.o:(.text+0x67ba0): first defined he=
      re
      drivers/net/wireless/ath/ath6kl/built-in.o: In function `htc_stop':
      (.opd+0x5e8): multiple definition of `htc_stop'
      drivers/net/wireless/ath/ath9k/built-in.o:(.opd+0x3e28): first defined here
      
      To fix this add ath6kl prefix to all public functions in htc.c.
      Reported-by: NStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      ad226ec2
    • R
    • K
      Add ath6kl cleaned up driver · bdcd8170
      Kalle Valo 提交于
      Last May we started working on cleaning up ath6kl driver which is
      currently in staging. The work has happened in a separate
      ath6kl-cleanup tree:
      
      http://git.kernel.org/?p=linux/kernel/git/kvalo/ath6kl-cleanup.git;a=summary
      
      After over 1100 (!) patches we have now reached a state where I would
      like to start discussing about pushing the driver to the wireless
      trees and replacing the staging driver.
      
      The driver is now a lot smaller and looks like a proper Linux driver.
      The size of the driver (measured with simple wc -l) dropped from 49
      kLOC to 18 kLOC and the number of the .c and .h files dropped from 107
      to 22. Most importantly the number of subdirectories reduced from 26
      to zero :)
      
      There are two remaining checkpatch warnings in the driver which we
      decided to omit for now:
      
      drivers/net/wireless/ath/ath6kl/debug.c:31:
        WARNING: printk() should include KERN_ facility level
      drivers/net/wireless/ath/ath6kl/sdio.c:527:
        WARNING: msleep < 20ms can sleep for up to 20ms;
        see Documentation/timers/timers-howto.txt
      
      The driver has endian annotations for all the hardware specific
      structures and there are no sparse errors. Unfortunately I don't have
      any big endian hardware to test that right now.
      
      We have been testing the driver both on x86 and arm platforms. The
      code is also compiled with sparc and parisc cross compilers.
      
      Notable missing features compared to the current staging driver are:
      
      o HCI over SDIO support
      o nl80211 testmode
      o firmware logging
      o suspend support
      
      Testmode, firmware logging and suspend support will be added soon. HCI
      over SDIO support will be more difficult as the HCI driver needs to
      share code with the wifi driver. This is something we need to research
      more.
      
      Also I want to point out the changes I did for signed endian support.
      As I wasn't able to find any support for signed endian annotations I
      decided to follow what NTFS has done and added my own. Grep for sle16
      and sle32, especially from wmi.h.
      
      Various people have been working on the cleanup, the hall of
      fame based on number of patches is:
      
         543  Vasanthakumar Thiagarajan
         403  Raja Mani
         252  Kalle Valo
          16  Vivek Natarajan
          12  Suraj Sumangala
           3  Joe Perches
           2  Jouni Malinen
      Signed-off-by: NVasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
      Signed-off-by: NRaja Mani <rmani@qca.qualcomm.com>
      Signed-off-by: NVivek Natarajan <nataraja@qca.qualcomm.com>
      Signed-off-by: NSuraj Sumangala <surajs@qca.qualcomm.com>
      Signed-off-by: NJoe Perches <joe@perches.com>
      Signed-off-by: NJouni Malinen <jouni@qca.qualcomm.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      bdcd8170