1. 29 12月, 2009 1 次提交
  2. 12 11月, 2009 1 次提交
  3. 31 10月, 2009 1 次提交
  4. 28 10月, 2009 1 次提交
    • B
      zd1211rw: Fix TX status reporting in order to have proper rate control · 7f4013f0
      Benoit PAPILLAULT 提交于
      First, we reduce the number of hardware retries to 0 (ie 2 real retries
      for each rate). Next, when we report the retries to mac80211, we always
      report a retry count of 1 (it seems to be 2 in fact, but using 2 seems
      to lead to wrong performance for some reason). We use a state machine to
      determine the real fate of a packet based on the 802.11 ACK and what the
      Zydas hardware is saying when a real retry occurs. The real retry rates
      are encoded in a static array. It has been tested with both zd1211 and
      zd1211b hardware. Of course, since the Zydas hardware is not reporting
      retries accurately, we are just doing our best in order to get the best
      performance (ie higher throughput).
      Signed-off-by: NBenoit PAPILLAULT <benoit.papillault@free.fr>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      7f4013f0
  5. 23 9月, 2009 1 次提交
  6. 21 9月, 2009 1 次提交
  7. 20 8月, 2009 1 次提交
    • J
      mac80211: allow configure_filter callback to sleep · 3ac64bee
      Johannes Berg 提交于
      Over time, a whole bunch of drivers have come up
      with their own scheme to delay the configure_filter
      operation to a workqueue. To be able to simplify
      things, allow configure_filter to sleep, and add
      a new prepare_multicast callback that drivers that
      need the multicast address list implement. This new
      callback must be atomic, but most drivers either
      don't care or just calculate a hash which can be
      done atomically and then uploaded to the hardware
      non-atomically.
      
      A cursory look suggests that at76c50x-usb, ar9170,
      mwl8k (which is actually very broken now), rt2x00,
      wl1251, wl1271 and zd1211 should make use of this
      new capability.
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      3ac64bee
  8. 14 8月, 2009 1 次提交
  9. 05 8月, 2009 1 次提交
    • L
      mac80211: redefine usage of the mac80211 workqueue · 42935eca
      Luis R. Rodriguez 提交于
      The mac80211 workqueue exists to enable mac80211 and drivers
      to queue their own work on a single threaded workqueue. mac80211
      takes care to flush the workqueue during suspend but we never
      really had requirements on drivers for how they should use
      the workqueue in consideration for suspend.
      
      We extend mac80211 to document how the mac80211 workqueue should
      be used, how it should not be used and finally move raw access to
      the workqueue to mac80211 only. Drivers and mac80211 use helpers
      to queue work onto the mac80211 workqueue:
      
        * ieee80211_queue_work()
        * ieee80211_queue_delayed_work()
      
      These helpers will now warn if mac80211 already completed its
      suspend cycle and someone is trying to queue work. mac80211
      flushes the mac80211 workqueue prior to suspend a few times,
      but we haven't taken the care to ensure drivers won't add more
      work after suspend. To help with this we add a warning when
      someone tries to add work and mac80211 already completed the
      suspend cycle.
      
      Drivers should ensure they cancel any work or delayed work
      in the mac80211 stop() callback.
      Signed-off-by: NLuis R. Rodriguez <lrodriguez@atheros.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      42935eca
  10. 04 8月, 2009 1 次提交
  11. 25 7月, 2009 1 次提交
  12. 11 7月, 2009 2 次提交
  13. 09 7月, 2009 2 次提交
  14. 19 6月, 2009 1 次提交
  15. 21 5月, 2009 1 次提交
  16. 07 5月, 2009 1 次提交
  17. 17 3月, 2009 1 次提交
  18. 06 3月, 2009 1 次提交
  19. 28 2月, 2009 1 次提交
  20. 14 2月, 2009 3 次提交
  21. 12 2月, 2009 2 次提交
  22. 10 2月, 2009 1 次提交
  23. 23 1月, 2009 1 次提交
  24. 09 1月, 2009 1 次提交
  25. 30 12月, 2008 1 次提交
    • J
      drivers/net/usb: use USB API functions rather than constants · f201a8a4
      Julia Lawall 提交于
      This set of patches introduces calls to the following set of functions:
      
      usb_endpoint_dir_in(epd)
      usb_endpoint_dir_out(epd)
      usb_endpoint_is_bulk_in(epd)
      usb_endpoint_is_bulk_out(epd)
      usb_endpoint_is_int_in(epd)
      usb_endpoint_is_int_out(epd)
      usb_endpoint_num(epd)
      usb_endpoint_type(epd)
      usb_endpoint_xfer_bulk(epd)
      usb_endpoint_xfer_control(epd)
      usb_endpoint_xfer_int(epd)
      usb_endpoint_xfer_isoc(epd)
      
      In some cases, introducing one of these functions is not possible, and it
      just replaces an explicit integer value by one of the following constants:
      
      USB_ENDPOINT_XFER_BULK
      USB_ENDPOINT_XFER_CONTROL
      USB_ENDPOINT_XFER_INT
      USB_ENDPOINT_XFER_ISOC
      
      In drivers/net/wireless/zd1211rw/zd_usb.c the code:
      
      (endpoint->bEndpointAddress & USB_TYPE_MASK) == USB_DIR_OUT
      
      is suspicious.  If it is intended to use USB_ENDPOINT_DIR_MASK rather than
      USB_TYPE_MASK, then the whole conditional test could be converted to a call
      to usb_endpoint_is_bulk_in.
      
      An extract of the semantic patch that makes these changes is as follows:
      (http://www.emn.fr/x-info/coccinelle/)
      
      // <smpl>
      @r1@ struct usb_endpoint_descriptor *epd; @@
      
      - ((epd->bmAttributes & \(USB_ENDPOINT_XFERTYPE_MASK\|3\)) ==
      - \(USB_ENDPOINT_XFER_CONTROL\|0\))
      + usb_endpoint_xfer_control(epd)
      
      @r5@ struct usb_endpoint_descriptor *epd; @@
      
      - ((epd->bEndpointAddress & \(USB_ENDPOINT_DIR_MASK\|0x80\)) ==
      -  \(USB_DIR_IN\|0x80\))
      + usb_endpoint_dir_in(epd)
      
      @inc@
      @@
      
      #include <linux/usb.h>
      
      @depends on !inc && (r1||r5)@
      @@
      
      + #include <linux/usb.h>
        #include <linux/usb/...>
      // </smpl>
      Signed-off-by: NJulia Lawall <julia@diku.dk>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f201a8a4
  26. 05 12月, 2008 1 次提交
    • S
      zd1211rw: use unaligned safe memcmp() in-place of compare_ether_addr() · cde6901b
      Shaddy Baddah 提交于
      Under my 2.6.28-rc6 sparc64, when associating to an AP through my
      zd1211rw device, I was seeing kernel log messages like (not exact output):
      
        Kernel unaligned access at TPC[10129b68] zd_mac_rx+0x144/0x32c [zd1211rw]
      
      For the zd1211rw module, on RX, the 80211 packet will be located after
      the PLCP header in the skb data buffer. The PLCP header being 5 bytes
      long, the 80211 header will start unaligned from an aligned skb
      buffer.
      
      As per Documentation/unaligned-memory-access.txt, we must replace the
      not unaligned() safe compare_ether_addr() with memcmp() to protect
      architectures that require alignment.
      Signed-off-by: NShaddy Baddah <shaddy_baddah@hotmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      cde6901b
  27. 07 11月, 2008 1 次提交
  28. 01 11月, 2008 3 次提交
  29. 28 10月, 2008 1 次提交
  30. 23 9月, 2008 2 次提交
  31. 16 9月, 2008 2 次提交