An error occurred fetching the project authors.
  1. 29 Jan, 2009 1 commit
  2. 05 Dec, 2008 2 commits
  3. 25 Nov, 2008 1 commit
    • Ivo van Doorn's avatar
      rt2x00: Detect USB BULK in/out endpoints · f1ca2167
      Ivo van Doorn authored
      Instead of hardcoding the used in/out endpoints
      we should detect them by walking through all
      available endpoints.
      
      rt2800usb will gain the most out of this, because
      the legacy drivers indicate that there are multiple
      endpoints available.
      However this code might benefit at least rt73usb as
      well for the MIMO queues, and if we are really lucky
      rt2500usb will benefit because for the TX and PRIO
      queues.
      
      Even if rt2500usb and rt73usb do not get better performance
      after this patch, the endpoint detection still belongs to
      rt2x00usb, and it shouldn't hurt to always try to detect
      the available endpoints.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      f1ca2167
  4. 31 Oct, 2008 1 commit
  5. 29 Aug, 2008 2 commits
  6. 22 Aug, 2008 1 commit
    • Ivo van Doorn's avatar
      rt2x00: Implement HW encryption · 2bb057d0
      Ivo van Doorn authored
      Various rt2x00 devices support hardware encryption.
      
      Most of them require the IV/EIV to be generated by mac80211,
      but require it to be provided seperately instead of within
      the frame itself. This means that rt2x00lib should extract
      the data from the frame and place it in the frame descriptor.
      During RX the IV/EIV is provided in the descriptor by the
      hardware which means that it should be inserted into the
      frame by rt2x00lib.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      2bb057d0
  7. 18 Aug, 2008 1 commit
  8. 29 Jul, 2008 1 commit
    • Ivo van Doorn's avatar
      rt2x00: Fix QOS sequence counting · 5adf6d63
      Ivo van Doorn authored
      When IEEE80211_TX_CTL_ASSIGN_SEQ is not set,
      the driver should disable hardware sequence counting
      to make sure the mac80211 provided counter is used.
      This fixes QOS sequence counting, since that is one
      of the cases where mac80211 provides a seperate
      sequence counter.
      
      By moving the sequence counting code to rt2x00queue
      we make sure that _all_ frames get the sequence counter,
      including RTS/CTS and Beacon frames.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      5adf6d63
  9. 08 Jul, 2008 1 commit
  10. 26 Jun, 2008 3 commits
  11. 14 Jun, 2008 3 commits
  12. 22 May, 2008 7 commits
    • Johannes Berg's avatar
      mac80211: use multi-queue master netdevice · e2530083
      Johannes Berg authored
      This patch updates mac80211 and drivers to be multi-queue aware and
      use that instead of the internal queue mapping. Also does a number
      of cleanups in various pieces of the code that fall out and reduces
      internal mac80211 state size.
      Signed-off-by: default avatarJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      e2530083
    • Johannes Berg's avatar
      mac80211: move TX info into skb->cb · e039fa4a
      Johannes Berg authored
      This patch converts mac80211 and all drivers to have transmit
      information and status in skb->cb rather than allocating extra
      memory for it and copying all the data around. To make it fit,
      a union is used where only data that is necessary for all steps
      is kept outside of the union.
      
      A number of fixes were done by Ivo, as well as the rt2x00 part
      of this patch.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohannes Berg <johannes@sipsolutions.net>
      Acked-by: default avatarDavid S. Miller <davem@davemloft.net>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      e039fa4a
    • Ivo van Doorn's avatar
      rt2x00: Split rt2x00lib_write_tx_desc() · 7050ec82
      Ivo van Doorn authored
      Split rt2x00lib_write_tx_desc() up into a TX descriptor initializor
      and TX descriptor writer.
      
      This split is required to properly allow mac80211 to move its
      tx_control structure into the skb->cb array.
      The rt2x00queue_create_tx_descriptor() function will read all tx control
      information and convert it into a rt2x00 TX descriptor information structure.
      After that function is complete, we have all information we needed from the
      tx control structure and are free to start writing into the skb->cb array
      for our own purposes.
      rt2x00queue_write_tx_descriptor() will be in charge of really sending
      the TX descriptor to the hardware and kicking the TX queue.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      7050ec82
    • Gertjan van Wingerde's avatar
      rt2x00: Fix queue related oops in case of deselected mac80211 multi-queue feature. · 61448f88
      Gertjan van Wingerde authored
      With the integration of the mac80211 multiqueue patches it has become possible that the
      mac80211 layer modifies the number of TX queues that is stored inside the ieee80211_hw
      structure, especially when multi-queue is not selected.
      
      The rt2x00 drivers are not well suited to handle that situation, as they allocate the
      queue structures before mac80211 has modified the number of queues it is going to use,
      and also expect the number of allocated queues to match the hardware implementation.
      
      Hence, ensure that rt2x00 maintains by itself the number of queues that the hardware
      supports, and, at the same time, making is not dependent on the preservation of contents
      inside a mac80211 structure.
      Signed-off-by: default avatarGertjan van Wingerde <gwingerde@kpnplanet.nl>
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      61448f88
    • Ivo van Doorn's avatar
      rt2x00: Remove ieee80211_tx_control argument from write_tx_desc() · 61486e0f
      Ivo van Doorn authored
      Move the last remaining information details read from ieee80211_tx_control
      in the drivers to the txentry_desc structure. After this we can
      remove ieee80211_tx_control from the argument list for the callback function,
      which makes it easier when the control information is moved into skb->cb
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      61486e0f
    • Ivo van Doorn's avatar
      rt2x00: Fix TX status reporting · fb55f4d1
      Ivo van Doorn authored
      The tx_status enumeration was broken since the introduction
      of rt61pci. That driver uses different values to report the
      status of the tx action.
      This would lead to frames that were reported as success but
      actually failed to be send out, or frames that were neither
      successfull or failure which were reported as failure.
      
      Fix this by change the TX status reporting and more explicitely
      check for failure or success. Note that a third possibility is
      added "unknown". Not all hardware (USB) can report the actual
      TX status, for rt61pci some frames will receive this status
      because the TXdone handler is never called for those frames.
      This unknown will now be handled as neither success or failure,
      so we no longer increment the failure counter while this conclusion
      could not be determined from the real status of the frame.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      fb55f4d1
    • Ivo van Doorn's avatar
      rt2x00: trim skb_frame_desc to 32 bytes · 5a6e5999
      Ivo van Doorn authored
      Remove frame_type from skb_frame_desc and pass it
      as argument to rt2x00debug_dump_frame().
      
      Change data_len and desc_len to unsigned short
      to save another 4 bytes in skb_frame_desc. Note that
      this was the only location where the data_len and
      desc_len was not yet treated as unsigned short.
      
      This trim is required to help mac80211 with adding
      the TX control and TX status informtation into the
      skb->cb structure. When that happens, drivers will
      have approximately 40 bytes left to use freely.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      5a6e5999
  13. 07 May, 2008 2 commits
  14. 25 Mar, 2008 1 commit
  15. 13 Mar, 2008 1 commit
    • Ivo van Doorn's avatar
      rt2x00: Fix rt2400pci signal · 89993890
      Ivo van Doorn authored
      After sampling hundreds of RX frame descriptors,
      the results were conclusive:
      - The Ralink documentation regarding the SIGNAL and RSSI are wrong.
      
      It turns out that of the 5 BBR registers, we should not use BBR0 and BBR1
      for SIGNAL and RSSI respectively, but actually BBR1 and BBR2.
      BBR0 does show values, but the exact meaning remains unclear,
      but they cannot be translated into a SIGNAL or RSSI field.
      BBR3, BBR4 and BBR5 are always 0, so their meaning is unknown.
      
      As it turns out, the reported SIGNAL is the PLCP value, this
      in contradiction to what was expected looking at rt2500pci which
      only reported the PLCP values for OFDM rates and bitrate values
      for CCK rates.
      
      This means we should let the driver raise the flag about the contents
      of the SIGNAL field so rt2x00lib can always do the right thing based
      on what the driver reports.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      89993890
  16. 29 Feb, 2008 4 commits
    • Ivo van Doorn's avatar
      rt2x00: Don't report driver generated frames to tx_status() · baf26a7e
      Ivo van Doorn authored
      This adds a new flag for the skb_frame_desc structure which is used to tag
      rts/cts frames that are generated by the driver. Through the tag we can
      recognize frames we have generated ourselves, so we don't report their tx
      status to mac80211.
      
      This patch is based on the original patch by
      Mattias Nissler <mattias.nissler@gmx.de>.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      baf26a7e
    • Ivo van Doorn's avatar
      rt2x00: Move beacon and atim queue defines into rt2x00 · 5957da4c
      Ivo van Doorn authored
      As Johannes Berg indicated the BEACON and AFTER_BEACON
      queue indeces in mac80211 should be removed because they
      are too hardware specific. This patch adds the queue index
      defines into rt2x00queue.h and removes the dependency of
      the defines inside mac80211.h.
      
      Also move rt2x00pci_beacon_update() into rt2400pci and
      rt2500pci individually since it is no longer a generic
      function since rt61 and rt2800 no longer use that.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      5957da4c
    • Ivo van Doorn's avatar
      rt2x00: Add per-interface structure · 6bb40dd1
      Ivo van Doorn authored
      Rework the interface handling. Delete the interface structure
      and replace it with a per-interface structure. This changes the
      way rt2x00 handles the active interface drastically.
      
      Copy ieee80211_bss_conf to the this rt2x00_intf structure during
      the bss_info_changed() callback function. This will allow us to
      reference it later, and removes the requirement for the device flag
      SHORT_PREAMBLE flag which is interface specific.
      
      Drivers receive the option to give the maximum number of virtual
      interfaces the device can handle. Virtual interface support:
      rt2400pci: 1 sta or 1 ap, * monitor interfaces
      rt2500pci: 1 sta or 1 ap, * monitor interfaces
      rt2500usb: 1 sta or 1 ap, * monitor interfaces
      rt61pci: 1 sta or 4 ap, * monitor interfaces
      rt73usb: 1 sta or 4 ap, * monitor interfaces
      
      At the moment none of the drivers support AP and STA interfaces
      simultaneously, this is a hardware limitation so future support
      will be very unlikely.
      
      Each interface structure receives its dedicated beacon entry,
      with this we can easily work with beaconing while multiple master
      mode interfaces are currently active.
      
      The configuration handlers for the MAC, BSSID and type are
      often called together since they all belong to the interface
      configuration. Merge the 3 configuration calls and cleanup
      the API between rt2x00lib and the drivers. While we are cleaning
      up the interface configuration anyway, we might as well clean up
      the configuration handler as well.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      6bb40dd1
    • Ivo van Doorn's avatar
      rt2x00: Queue handling overhaul · 181d6902
      Ivo van Doorn authored
      This introduces a big queue handling overhaul, this also
      renames "ring" to "queues".
      
      Move queue handling into rt2x00queue.c and the matching header,
      use Kerneldoc to improve rt2x00 library documentation.
      
      Access to the queues is now protected under a spinlock, this
      to prevent race conditions which could corrupt the indexing
      system of the queue.
      
      Each queue entry allocates x bytes for driver/device specific data,
      this cleans up the queue structure significantly and improves
      code readability.
      
      rt2500usb no longer needs 2 entries in the beacon queue to correctly
      send out the guardian byte. This is now handled in the entry specific
      structure.
      
      rt61 and rt73 now use the correct descriptor size for beacon frames,
      since this data is written into the registers not the entire TXD
      descriptor was used but instead of a subset of it named TXINFO.
      
      Finally this also fixes numerous other bugs related to incorrect
      beacon handling or beacon related code.
      Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      181d6902