1. 16 Jul, 2011 3 commits
  2. 11 Jul, 2011 8 commits
  3. 01 Jul, 2011 4 commits
  4. 18 Jun, 2011 6 commits
  5. 11 Jun, 2011 4 commits
  6. 03 Jun, 2011 1 commit
  7. 01 Jun, 2011 1 commit
  8. 13 May, 2011 2 commits
    • Johannes Berg's avatar
      iwlagn: support multiple TBs per command · 4ce7cc2b
      Johannes Berg authored
      
      
      The current "huge" command handling is a bit
      confusing, and very limited since only one
      command may be huge at a time. Additionally,
      we often copy data around quite pointlessly
      since we could instead map the existing scan
      buffer for example and use it directly.
      
      This patch makes that possible. The first
      change is that multiple buffers may be given
      to each command (this change was prepared
      earlier so callsites don't need to change).
      Each of those can be mapped attached to a TB
      in the TFD, and the command header can use a
      TB (the first one) in the TFD as well.
      
      Doing this allows getting rid of huge commands
      in favour of mapping existing buffers. The
      beacon transmission is also optimised to not
      copy the SKB at all but use multiple TBs.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: default avatarWey-Yi Guy <wey-yi.w.guy@intel.com>
      4ce7cc2b
    • Johannes Berg's avatar
      iwlagn: prepare for multi-TB commands · 3fa50738
      Johannes Berg authored
      
      
      In a subsequent patch, I want to make commands use
      multiple TBs in a TFD. This is a simple change to
      prepare the data structures for this, with as of
      now still just a single TB supported.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: default avatarWey-Yi Guy <wey-yi.w.guy@intel.com>
      3fa50738
  9. 30 Apr, 2011 3 commits
  10. 22 Apr, 2011 7 commits
  11. 08 Apr, 2011 1 commit
    • Johannes Berg's avatar
      iwlagn: clean up & autodetect statistics · 0da0e5bf
      Johannes Berg authored
      
      
      There's no need to keep both normal and BT statistics
      versions around all the time in memory when we only
      use a subset of both. So keep only the subsets that
      we need in memory, depending on the debug config).
      
      Also, in doing so, we can remove all the calls to
      iwl_bt_statistics() in the driver as we'll just
      access the copied statistics now.
      
      Finally, also remove this call from the one place
      where it might still be needed and automatically
      detect what kind of statistics the device is sending
      based on their size. This way, we don't need to keep
      track of which devices do what any more, which is
      good since this is subject to change based on the
      ucode version (as some ucode even for non-BT devices
      will in fact use BT statistics).
      
      Warn upon encountering a statistics command from the
      ucode that isn't known, so we will find such issues
      earlier in the future.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      Tested-by: default avatarDon Fry <donald.h.fry@intel.com>
      Signed-off-by: default avatarWey-Yi Guy <wey-yi.w.guy@intel.com>
      0da0e5bf