1. 01 3月, 2008 2 次提交
    • I
      rt2x00: Queue handling overhaul · 181d6902
      Ivo van Doorn 提交于
      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: NIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      181d6902
    • I
      rt2x00: Update copyright notice · 811aa9ca
      Ivo van Doorn 提交于
      Signed-off-by: NIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      811aa9ca
  2. 29 1月, 2008 23 次提交
  3. 19 11月, 2007 1 次提交
  4. 15 11月, 2007 1 次提交
    • I
      rt2x00: Fix chipset revision validation · 755a957d
      Ivo van Doorn 提交于
      The validation of the chipset revision was broken
      since for rt2500usb and rt73usb different registers
      should be read. When rt2500usb was loaded for a rt73
      device it would false think the chipset was correct
      because the wrong register was read and validated.
      
      This has been fixed by expanding the check to also
      see if the first 4 bits of the revision is not-0
      (When reading the wrong register offset the returned
      value is usually 0 which can be interpreted as invalid)
      Signed-off-by: NIvo van Doorn <IvDoorn@gmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      755a957d
  5. 11 10月, 2007 13 次提交