1. 31 Oct, 2008 1 commit
  2. 30 Oct, 2008 1 commit
  3. 29 Oct, 2008 1 commit
  4. 27 Oct, 2008 1 commit
  5. 14 Oct, 2008 1 commit
  6. 06 Oct, 2008 2 commits
  7. 30 Sep, 2008 1 commit
  8. 24 Sep, 2008 1 commit
  9. 15 Sep, 2008 2 commits
    • Johannes Berg's avatar
      mac80211: fix virtual interfaces vs. injection · 25d834e1
      Johannes Berg authored
      
      
      Currently, virtual interface pointers passed to drivers might be
      from monitor interfaces and as such completely uninitialised
      because we do not tell the driver about monitor interfaces when
      those are created. Instead of passing them, we should therefore
      indicate to the driver that there is no information; do that by
      passing a NULL value and adjust drivers to cope with it.
      
      As a result, some mac80211 API functions also need to cope with
      a NULL vif pointer so drivers can still call them unconditionally.
      
      Also, when injecting frames we really don't want to pass NULL all
      the time, if we know we are the source address of a frame and have
      a local interface for that address, we can to use that interface.
      This also helps with processing the frame correctly for that
      interface which will help the 802.11w implementation. It's not
      entirely correct for VLANs or WDS interfaces because there the MAC
      address isn't unique, but it's already a lot better than what we
      do now.
      
      Finally, when injecting without a matching local interface, don't
      assign sequence numbers at all.
      Signed-off-by: default avatarJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      25d834e1
    • Johannes Berg's avatar
      mac80211: use nl80211 interface types · 05c914fe
      Johannes Berg authored
      
      
      There's really no reason for mac80211 to be using its
      own interface type defines. Use the nl80211 types and
      simplify the configuration code a bit: there's no need
      to translate them any more now.
      Signed-off-by: default avatarJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      05c914fe
  10. 11 Sep, 2008 3 commits
  11. 05 Sep, 2008 1 commit
  12. 02 Sep, 2008 1 commit
  13. 29 Aug, 2008 7 commits
  14. 22 Aug, 2008 9 commits
  15. 18 Aug, 2008 1 commit
  16. 07 Aug, 2008 1 commit
  17. 04 Aug, 2008 1 commit
    • Ivo van Doorn's avatar
      rt2x00: Disable link tuning in rt2500usb · d06193f3
      Ivo van Doorn authored
      
      
      In the legacy rt2570 driver the link tuner was never
      really called. And now the reason has finally become
      apparent: It breaks TX capabilities
      
      As soon as the device has been associated all following
      TX frames will be queued in the hardware and never transmitted
      to the air. Disabling sections of the link tuner did not
      have the expected result, but completely disabling the
      link tuner did have the right result (Both of my rt2570 devices
      came back to life).
      
      This should fix Fedora bug: 411481
      
      v2: Fix typos
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      d06193f3
  18. 02 Aug, 2008 1 commit
    • Ivo van Doorn's avatar
      rt2x00: Fix compile warning · 82f97b8d
      Ivo van Doorn authored
      
      
      rt2x00usb_vendor_request_large_buff is write-only, so it is
      safe to make the argument a const.
      
      Fixes compile warning:
      drivers/net/wireless/rt2x00/rt73usb.c: In function 'rt73usb_load_firmware':
      drivers/net/wireless/rt2x00/rt73usb.c:916: warning: passing argument 5 of 'rt2x00usb_vendor_request_large_buff' discards qualifiers from pointer target typ
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      82f97b8d
  19. 01 Aug, 2008 4 commits