1. 24 3月, 2010 1 次提交
  2. 10 3月, 2010 1 次提交
  3. 27 2月, 2010 1 次提交
  4. 13 2月, 2010 1 次提交
  5. 03 2月, 2010 1 次提交
  6. 26 1月, 2010 1 次提交
  7. 16 1月, 2010 2 次提交
  8. 13 1月, 2010 1 次提交
  9. 23 12月, 2009 1 次提交
  10. 22 12月, 2009 1 次提交
  11. 05 12月, 2009 1 次提交
  12. 29 11月, 2009 2 次提交
    • L
      ath9k: Fix maximum tx fifo settings for single stream devices · f4709fdf
      Luis R. Rodriguez 提交于
      Atheros single stream AR9285 and AR9271 have half the PCU TX FIFO
      buffer size of that of dual stream devices. Dual stream devices
      have a max PCU TX FIFO size of 8 KB while single stream devices
      have 4 KB. Single stream devices have an issue though and require
      hardware only to use half of the amount of its capable PCU TX FIFO
      size, 2 KB and this requires a change in software.
      
      Technically a change would not have been required (except for frame
      burst considerations of 128 bytes) if these devices would have been
      able to use the full 4 KB of the PCU TX FIFO size but our systems
      engineers recommend 2 KB to be used only. We enforce this through
      software by reducing the max frame triggger level to 2 KB.
      
      Fixing the max frame trigger level should then have a few benefits:
      
        * The PER will now be adjusted as designed for underruns when the
          max trigger level is reached. This should help alleviate the
          bus as the rate control algorithm chooses a slower rate which
          should ensure frames are transmitted properly under high system
          bus load.
      
        * The poll we use on our TX queues should now trigger and work
          as designed for single stream devices. The hardware passes
          data from each TX queue on the PCU TX FIFO queue respecting each
          queue's priority. The new trigger level ensures this seeding of
          the PCU TX FIFO queue occurs as designed which could mean avoiding
          false resets and actually reseting hw correctly when a TX queue
          is indeed stuck.
      
        * Some undocumented / unsupported behaviour could have been triggered
          when the max trigger level level was being set to 4 KB on single
          stream devices. Its not clear what this issue was to me yet.
      
      Cc: Kyungwan Nam <kyungwan.nam@atheros.com>
      Cc: Bennyam Malavazi <bennyam.malavazi@atheros.com>
      Cc: Stephen Chen <stephen.chen@atheros.com>
      Cc: Shan Palanisamy <shan.palanisamy@atheros.com>
      Cc: Paul Shaw <paul.shaw@atheros.com>
      Signed-off-by: NVasanthakumar Thiagarajan <vasanth@atheros.com>
      Signed-off-by: NLuis R. Rodriguez <lrodriguez@atheros.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      f4709fdf
    • F
      ath9k: properly use the mac80211 rate control api · 545750d3
      Felix Fietkau 提交于
      This patch changes ath9k to pass proper MCS indexes and flags
      between the RC and the rest of the driver code.
      sc->cur_rate_table remains, as it's used by the RC code internally,
      but the rest of the driver code no longer uses it, so a potential
      new RC for ath9k would not have to update it.
      Signed-off-by: NFelix Fietkau <nbd@openwrt.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      545750d3
  13. 19 11月, 2009 2 次提交
  14. 12 11月, 2009 1 次提交
  15. 31 10月, 2009 14 次提交
  16. 08 10月, 2009 9 次提交