1. 02 6月, 2011 1 次提交
  2. 20 5月, 2011 4 次提交
  3. 17 5月, 2011 1 次提交
  4. 12 5月, 2011 2 次提交
  5. 11 5月, 2011 2 次提交
  6. 06 5月, 2011 1 次提交
  7. 29 4月, 2011 1 次提交
  8. 31 3月, 2011 1 次提交
  9. 26 2月, 2011 1 次提交
    • J
      mac80211: make tx() operation return void · 7bb45683
      Johannes Berg 提交于
      The return value of the tx operation is commonly
      misused by drivers, leading to errors. All drivers
      will drop frames if they fail to TX the frame, and
      they must also properly manage the queues (if they
      didn't, mac80211 would already warn).
      
      Removing the ability for drivers to return a BUSY
      value also allows significant cleanups of the TX
      TX handling code in mac80211.
      
      Note that this also fixes a bug in ath9k_htc, the
      old "return -1" there was wrong.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      Tested-by: Sedat Dilek <sedat.dilek@googlemail.com> [ath5k]
      Acked-by: Gertjan van Wingerde <gwingerde@gmail.com> [rt2x00]
      Acked-by: Larry Finger <Larry.Finger@lwfinger.net> [b43, rtl8187, rtlwifi]
      Acked-by: Luciano Coelho <coelho@ti.com> [wl12xx]
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      7bb45683
  10. 23 12月, 2010 2 次提交
  11. 14 12月, 2010 1 次提交
    • R
      b43: rename TMS defines, drop useless condition from core reset · 42ab135f
      Rafał Miłecki 提交于
      As discussed we do not know band width at core reset time and it is not a good
      idea to reset whole just to change band. So just set unconditionally 20 MHz
      band width as default during core reset.
      
      As for defines PHY clock changed to band width in specs and it makes much more
      sens to call defines by band width which is self-explainable. Updated specs do
      not mention 0 value, but comparing to old ones you can notice lineral relation
      between PHY clock speed and band width. So it makes sense for 0x0 value to be
      10 MHz band width.
      Signed-off-by: NRafał Miłecki <zajec5@gmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      42ab135f
  12. 09 12月, 2010 3 次提交
  13. 17 11月, 2010 1 次提交
  14. 17 8月, 2010 3 次提交
  15. 22 7月, 2010 1 次提交
    • J
      b43: silence most sparse warnings · 41950bdf
      John W. Linville 提交于
        CHECK   drivers/net/wireless/b43/main.c
      drivers/net/wireless/b43/main.c:111:5: warning: symbol 'b43_modparam_pio' was not declared. Should it be static?
        CHECK   drivers/net/wireless/b43/phy_g.c
      drivers/net/wireless/b43/phy_g.c:975:56: warning: cast truncates bits from constant value (ffff7fff becomes 7fff)
        CHECK   drivers/net/wireless/b43/phy_lp.c
      drivers/net/wireless/b43/phy_lp.c:2701:6: warning: symbol 'b43_lpphy_op_switch_analog' was not declared. Should it be static?
      drivers/net/wireless/b43/phy_lp.c:1148:30: warning: cast truncates bits from constant value (ffff1fff becomes 1fff)
      drivers/net/wireless/b43/phy_lp.c:1525:30: warning: cast truncates bits from constant value (ffff1fff becomes 1fff)
      drivers/net/wireless/b43/phy_lp.c:1529:30: warning: cast truncates bits from constant value (ffff1fff becomes 1fff)
        CHECK   drivers/net/wireless/b43/wa.c
      drivers/net/wireless/b43/wa.c:385:60: warning: cast truncates bits from constant value (ffff00ff becomes ff)
      drivers/net/wireless/b43/wa.c:403:55: warning: cast truncates bits from constant value (ffff00ff becomes ff)
      drivers/net/wireless/b43/wa.c:405:55: warning: cast truncates bits from constant value (ffff00ff becomes ff)
      drivers/net/wireless/b43/wa.c:415:71: warning: cast truncates bits from constant value (ffff0fff becomes fff)
      
      AFAICT, none of these amount to real bugs.  But this reduces warning
      spam from sparse w/o significantly affecting readability of the code (IMHO).
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      41950bdf
  16. 22 6月, 2010 1 次提交
  17. 04 5月, 2010 1 次提交
  18. 01 5月, 2010 1 次提交
  19. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  20. 24 3月, 2010 1 次提交
  21. 27 2月, 2010 1 次提交
  22. 09 2月, 2010 2 次提交
  23. 04 2月, 2010 1 次提交
    • L
      b43: Fix throughput regression · b6c3f5be
      Larry Finger 提交于
      Commit c7ab5ef9 entitled "b43: implement
      short slot and basic rate handling" reduced the transmit throughput for
      my BCM4311 device from 18 Mb/s to 0.7 Mb/s. The basic rate handling
      portion is OK, the problem is in the short slot handling.
      
      Prior to this change, the short slot enable/disable routines were never
      called. Experimentation showed that the critical part was changing the
      value at offset 0x0010 in the shared memory. This is supposed to contain
      the 802.11 Slot Time in usec, but if it is changed from its initial value
      of zero, performance is destroyed. On the other hand, changing the value
      in the MMIO register corresponding to the Interframe Slot Time increased
      performance from 18 to 22 Mb/s. A BCM4306/3 also shows dramatic
      improvement of the transmit rate from 5.3 to 19.0 Mb/s.
      
      Other changes in the patch include removal of the magic number for the
      MMIO register, and allowing the slot time to be set for any PHY operating
      in the 2.4 GHz band. Previously, the routine was executed only for G PHYs.
      Signed-off-by: NLarry Finger <Larry.Finger@lwfinger.net>
      Cc: Stable <stable@kernel.org> [Any stable version back through 2.6.28]
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      b6c3f5be
  24. 26 1月, 2010 1 次提交
  25. 23 1月, 2010 2 次提交
  26. 16 1月, 2010 1 次提交
  27. 15 1月, 2010 1 次提交
  28. 29 12月, 2009 1 次提交