1. 29 1月, 2008 1 次提交
  2. 09 5月, 2007 1 次提交
  3. 10 12月, 2006 1 次提交
  4. 30 6月, 2006 1 次提交
  5. 24 6月, 2006 1 次提交
  6. 20 3月, 2006 1 次提交
  7. 29 9月, 2005 3 次提交
  8. 20 9月, 2005 1 次提交
    • D
      [SPARC64]: Handle little-endian unaligned loads/stores correctly. · ff171d8f
      David S. Miller 提交于
      Because we use byte loads/stores to cons up the value
      in and out of registers, we can't expect the ASI endianness
      setting to take care of this for us.  So do it by hand.
      
      This case is triggered by drivers/block/aoe/aoecmd.c in the
      ataid_complete() function where it goes:
      
      		/* word 100: number lba48 sectors */
      		ssize = le64_to_cpup((__le64 *) &id[100<<1]);
      
      This &id[100<<1] address is 4 byte, rather than 8 byte aligned,
      thus triggering the unaligned exception.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ff171d8f
  9. 30 8月, 2005 1 次提交
    • D
      [SPARC64]: Revamp Spitfire error trap handling. · 6c52a96e
      David S. Miller 提交于
      Current uncorrectable error handling was poor enough
      that the processor could just loop taking the same
      trap over and over again.  Fix things up so that we
      at least get a log message and perhaps even some register
      state.
      
      In the process, much consolidation became possible,
      particularly with the correctable error handler.
      
      Prefix assembler and C function names with "spitfire"
      to indicate that these are for Ultra-I/II/IIi/IIe only.
      
      More work is needed to make these routines robust and
      featureful to the level of the Ultra-III error handlers.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6c52a96e
  10. 20 8月, 2005 1 次提交
  11. 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