1. 11 12月, 2013 1 次提交
  2. 15 10月, 2013 1 次提交
  3. 08 7月, 2011 1 次提交
  4. 20 4月, 2011 1 次提交
    • I
      rt2x00: Split rt2x00dev->flags · 7dab73b3
      Ivo van Doorn 提交于
      The number of flags defined for the rt2x00dev->flags field,
      has been growing over the years. Currently we are approaching
      the maximum number of bits which are available in the field.
      
      A secondary problem, is that one part of the field are initialized only
      during boot, because the driver requirements are initialized or device
      requirements are loaded from the EEPROM. In both cases, the flags are
      fixed and will not change during device operation. The other flags are
      the device state, and will change frequently. So far this resulted in the fact
      that for some flags, the atomic bit accessors are used, while for the others
      the non-atomic variants are used.
      
      By splitting the flags up into a "flags" and "cap_flags" we can put all flags
      which are fixed inside "cap_flags". This field can then be read non-atomically.
      In the "flags" field we keep the device state, which is going to be read atomically.
      
      This adds more room for more flags in the future, and sanitizes the field access methods.
      Signed-off-by: NIvo van Doorn <IvDoorn@gmail.com>
      Acked-by: NHelmut Schaa <helmut.schaa@googlemail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      7dab73b3
  5. 31 3月, 2011 1 次提交
  6. 17 8月, 2010 1 次提交
  7. 11 5月, 2010 1 次提交
  8. 12 11月, 2009 1 次提交
  9. 01 9月, 2009 1 次提交
    • I
      rt2x00: Reorganize padding & L2 padding · daee6c09
      Ivo van Doorn 提交于
      The old function rt2x00queue_payload_align() handled
      both adding and removing L2 padding and some basic
      frame alignment. The entire function was being abused
      because it had multiple functions and the header length
      argument was somtimes used to align the header instead
      of the payload.
      
      Additionally there was a bug when inserting L2 padding
      that only the payload was aligned but not the header. This
      happens when the header wasn't aligned properly by mac80211,
      but rt2x00lib only moves the payload.
      
      A secondary problem was that when removing L2 padding during
      TXdone or RX the skb wasn't resized to the proper size.
      
      Split the function into seperate functions each handling
      its task as it should.
      Signed-off-by: NIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      daee6c09
  10. 25 7月, 2009 1 次提交
  11. 11 7月, 2009 1 次提交
  12. 23 5月, 2009 1 次提交
  13. 07 5月, 2009 2 次提交
  14. 30 1月, 2009 2 次提交
  15. 06 1月, 2009 1 次提交
  16. 05 12月, 2008 3 次提交
  17. 07 10月, 2008 1 次提交
  18. 23 8月, 2008 1 次提交
    • I
      rt2x00: Implement HW encryption · 2bb057d0
      Ivo van Doorn 提交于
      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: NIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      2bb057d0