1. 22 7月, 2009 1 次提交
  2. 23 5月, 2009 1 次提交
  3. 23 4月, 2009 2 次提交
  4. 22 4月, 2009 2 次提交
    • R
      iwlwifi: DMA fixes · df833b1d
      Reinette Chatre 提交于
      A few issues wrt DMA were uncovered when using the driver with swiotlb.
      - driver should not use memory after it has been mapped
      - iwl3945's RX queue management cannot use all of iwlagn because
        the size of the RX buffer is different. Revert back to using
        iwl3945 specific routines that map/unmap memory.
      - no need to "dma_syn_single_range_for_cpu" followed by pci_unmap_single,
        we can just call pci_unmap_single initially
      - only map the memory area that will be used by device. this is especially
        relevant to the mapping of iwl_cmd. we should not map the entire
        structure because the meta data at the beginning of structure contains
        the address to be used later for unmapping. If the address to be used for
        unmapping is stored in mapped data it creates a problem.
      - ensure that _if_ memory needs to be modified after it is mapped that we
        call _sync_single_for_cpu first, and then release it back to device with
        _sync_single_for_device
      - we mapped the wrong length of data for host commands, with mapped length
        differing with length provided to device, fix that.
      
      Thanks to Jason Andryuk <jandryuk@gmail.com> for significant bisecting
      help to find these issues.
      
      This fixes http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1964Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      Tested-by: NJason Andryuk <jandryuk@gmail.com>
      Tested-by: NBen Gamari <bgamari@gmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      df833b1d
    • R
      iwlwifi: add debugging for TX path · d2ee9cd2
      Reinette Chatre 提交于
      When debugging TX issues it is helpful to know the seq nr of the
      frame being transmitted. The seq nr is printed as part of ucode's
      log informing us which frame is being processed. Having this information
      printed in driver log makes it easy to match activities between driver
      and firmware.
      
      Also make possible to print TX flags directly. These are already printed
      as part of entire TX command, but having it printed directly in cpu format
      makes it easier to look at.
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      d2ee9cd2
  5. 28 3月, 2009 3 次提交
  6. 28 2月, 2009 1 次提交
  7. 26 2月, 2009 1 次提交
  8. 10 2月, 2009 2 次提交
  9. 30 1月, 2009 9 次提交
  10. 20 12月, 2008 1 次提交
  11. 13 12月, 2008 2 次提交
  12. 05 12月, 2008 1 次提交
  13. 26 11月, 2008 3 次提交
  14. 22 11月, 2008 2 次提交
  15. 11 11月, 2008 1 次提交
  16. 01 11月, 2008 6 次提交
  17. 28 10月, 2008 1 次提交
  18. 25 9月, 2008 1 次提交