1. 08 9月, 2005 1 次提交
  2. 05 8月, 2005 1 次提交
    • D
      [PATCH] USB: ehci: microframe handling fix · 7dedacf4
      David Brownell 提交于
      This patch has a one line oops fix, plus related cleanups.
      
       - The bugfix uses microframe scheduling data given to the hardware to
         test "is this a periodic QH", rather than testing for nonzero period.
         (Prevents an oops by providing the correct answer.)
      
       - The cleanup going along with the patch should make it clearer what's
         going on whenever those bitfields are accessed.
      
      The bug came about when, around January, two new kinds of EHCI interrupt
      scheduling operation were added, involving both the high speed (24 KBytes
      per millisec) and low/full speed (1-64 bytes per millisec) microframe
      scheduling.  A driver for the Edirol UA-1000 Audio Capture Unit ran into
      the oops; it used one of the newly supported high speed modes.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      7dedacf4
  3. 13 7月, 2005 1 次提交
  4. 28 6月, 2005 1 次提交
    • D
      [PATCH] USB: ehci-hcd - fix page pointer allocation in itd_patch() · 77078570
      David Brownell 提交于
      The itd_patch() function is responsible for allocating entries in the
      buffer page pointer list of the iTD.  Particularly, a new page pointer
      is needed every time when buffer data crosses a page boundary.
      
      However, there is a bug in the allocation logic: the function does not
      allocate a new entry when the current transaction is the first
      transaction in the iTD (as indicated by first!=0).
      
      The consequence is that, when the data of the first transaction begins
      somewhere at the end of a page so that it actually does cross the page
      boundary, no new page pointer is allocated.  This means that the data
      at the end of the first transaction (beyond the page boundary) will be
      accessed by the HC using the second page pointer, which is zero.
      Furthermore, the first page pointer will be later overwritten by the
      page pointers of the other transactions, which will garble it because
      the value is or-ed into the iTD field.
      
      All this particular check (for !first) does is cause incorrect
      behaviour, so it should be entirely removed (and with it the variable
      first that is not used for anything else).
      Signed-off-by: NClemens Ladisch <clemens@ladisch.de>
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      77078570
  5. 19 4月, 2005 1 次提交
  6. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4