1. 09 9月, 2009 1 次提交
  2. 01 9月, 2009 1 次提交
  3. 29 8月, 2009 1 次提交
  4. 20 8月, 2009 1 次提交
  5. 04 6月, 2009 1 次提交
    • J
      rfkill: rewrite · 19d337df
      Johannes Berg 提交于
      This patch completely rewrites the rfkill core to address
      the following deficiencies:
      
       * all rfkill drivers need to implement polling where necessary
         rather than having one central implementation
      
       * updating the rfkill state cannot be done from arbitrary
         contexts, forcing drivers to use schedule_work and requiring
         lots of code
      
       * rfkill drivers need to keep track of soft/hard blocked
         internally -- the core should do this
      
       * the rfkill API has many unexpected quirks, for example being
         asymmetric wrt. alloc/free and register/unregister
      
       * rfkill can call back into a driver from within a function the
         driver called -- this is prone to deadlocks and generally
         should be avoided
      
       * rfkill-input pointlessly is a separate module
      
       * drivers need to #ifdef rfkill functions (unless they want to
         depend on or select RFKILL) -- rfkill should provide inlines
         that do nothing if it isn't compiled in
      
       * the rfkill structure is not opaque -- drivers need to initialise
         it correctly (lots of sanity checking code required) -- instead
         force drivers to pass the right variables to rfkill_alloc()
      
       * the documentation is hard to read because it always assumes the
         reader is completely clueless and contains way TOO MANY CAPS
      
       * the rfkill code needlessly uses a lot of locks and atomic
         operations in locked sections
      
       * fix LED trigger to actually change the LED when the radio state
         changes -- this wasn't done before
      Tested-by: NAlan Jenkins <alan-jenkins@tuffmail.co.uk>
      Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br> [thinkpad]
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      19d337df
  6. 28 2月, 2009 8 次提交
  7. 30 1月, 2009 1 次提交
  8. 26 12月, 2008 1 次提交
    • H
      drivers/net/wireless/b43: fix sparse warnings: make symbols static · 11ab72a7
      Hannes Eder 提交于
      Fix this sparse warnings:
      
        drivers/net/wireless/b43/phy_a.c:80:6: warning: symbol 'b43_radio_set_tx_iq' was not declared. Should it be static?
        drivers/net/wireless/b43/phy_a.c:150:6: warning: symbol 'b43_radio_init2060' was not declared. Should it be static?
        drivers/net/wireless/b43/phy_g.c:57:10: warning: symbol 'b43_radio_channel_codes_bg' was not declared. Should it be static?
        drivers/net/wireless/b43/phy_g.c:218:6: warning: symbol 'b43_set_txpower_g' was not declared. Should it be static?
        drivers/net/wireless/b43/phy_g.c:386:6: warning: symbol 'b43_nrssi_hw_write' was not declared. Should it be static?
        drivers/net/wireless/b43/phy_g.c:393:5: warning: symbol 'b43_nrssi_hw_read' was not declared. Should it be static?
        drivers/net/wireless/b43/phy_g.c:404:6: warning: symbol 'b43_nrssi_hw_update' was not declared. Should it be static?
        drivers/net/wireless/b43/phy_g.c:418:6: warning: symbol 'b43_nrssi_mem_update' was not declared. Should it be static?
        drivers/net/wireless/b43/phy_g.c:592:6: warning: symbol 'b43_calc_nrssi_slope' was not declared. Should it be static?
        drivers/net/wireless/b43/phy_g.c:1357:5: warning: symbol 'b43_radio_init2050' was not declared. Should it be static?
      Signed-off-by: NHannes Eder <hannes@hanneseder.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      11ab72a7
  9. 20 12月, 2008 1 次提交
  10. 12 9月, 2008 1 次提交
  11. 09 9月, 2008 1 次提交
  12. 06 9月, 2008 2 次提交
  13. 30 8月, 2008 2 次提交
    • M
      b43: Rewrite TX power adjustment · 18c8adeb
      Michael Buesch 提交于
      This patch rewrites the TX power recalculation algorithms to scale better
      with changed enviromnent. If there's low
      TX traffic, the power will be checked against the desired values
      every 60 seconds.
      If there is high TX traffic, the check is redone every 2 seconds. This improves
      the reaction times a lot and confuses the rate control less.
      It will also reduce the time it initially takes to tune to a new TX power
      value. With the old algorithm it could take about 30 to 45 seconds to settle to
      a new power value. This will happen in about two to four seconds now.
      Signed-off-by: NMichael Buesch <mb@bu3sch.de>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      18c8adeb
    • M
      b43: Implement dynamic PHY API · ef1a628d
      Michael Buesch 提交于
      This patch implements a dynamic "ops" based PHY API.
      This is needed in order to conveniently support future PHY types
      to avoid the "switch"-hell.
      
      This patch does not change any functionality. It just moves lots
      of code from one place to another and adjusts it for the changed
      data structures.
      Signed-off-by: NMichael Buesch <mb@bu3sch.de>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      ef1a628d
  14. 15 5月, 2008 2 次提交
  15. 08 5月, 2008 2 次提交
    • M
      b43: Remove some dead code · f4440e8a
      Michael Buesch 提交于
      This patch removes some dead code from the driver.
      Signed-off-by: NMichael Buesch <mb@bu3sch.de>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      f4440e8a
    • M
      b43: Rewrite LO calibration algorithm · f5eda47f
      Michael Buesch 提交于
      This patch distributes the Local Oscillator calibration bursts over time,
      so that calibration only happens when it's actually needed.
      Currently we periodically perform a recalibration of the whole table.
      The table is huge and this takes lots of time. Additionally only small bits
      of the table are actually needed at a given time. So instead of maintaining
      a huge table with all possible calibration values, we create dynamic calibration
      settings that
      a) We only calibrate when they are actually needed.
      b) Are cached for some time until they expire.
      So a recalibration might happen if we need a calibration setting that's not
      cached, or if the active calibration setting expires.
      Currently the expire timeout is set to 30 seconds. We may raise that in future.
      
      This patch reduces overall memory consumption by nuking the
      huge static calibration tables.
      
      This patch has been tested on several 4306, 4311 and 4318 flavours.
      Signed-off-by: NMichael Buesch <mb@bu3sch.de>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      f5eda47f
  16. 24 4月, 2008 1 次提交
  17. 14 3月, 2008 1 次提交
  18. 29 1月, 2008 8 次提交
  19. 30 11月, 2007 1 次提交
  20. 14 10月, 2007 1 次提交
    • G
      b43 wireless needs <linux/io.h> · 50e36ebe
      Geert Uytterhoeven 提交于
      b43 wireless needs <linux/io.h>
      
        linux/drivers/net/wireless/b43/pio.h: In function 'b43_pio_write':
        linux/drivers/net/wireless/b43/pio.h:89: error: implicit declaration of function 'mmiowb'
      
        linux/drivers/net/wireless/b43/phy.c: In function 'b43_phy_write':
        linux/drivers/net/wireless/b43/phy.c:301: error: implicit declaration of function 'mmiowb'
      
        linuxdrivers/net/wireless/b43/sysfs.c: In function 'b43_attr_interfmode_store':
        linuxdrivers/net/wireless/b43/sysfs.c:147: error: implicit declaration of function 'mmiowb'
      Signed-off-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      50e36ebe
  21. 11 10月, 2007 2 次提交