1. 14 1月, 2007 1 次提交
    • S
      [SCSI] megaraid_{mm,mbox}: init fix for kdump · cd96d96f
      Sumant Patro 提交于
      1.      Changes in Initialization to fix kdump failure.
              Send SYNC command on loading.
              This command clears the pending commands in the adapter
              and re-initialize its internal RAID structure.
              Without this change, megaraid driver either panics or fails to
              initialize the adapter during kdump's second kernel boot
              if there are pending commands or interrupts from other devices
              sharing the same IRQ.
      2.      Authors email-id domain name changed from lsil.com to lsi.com.
              Also modified the MODULE_AUTHOR to megaraidlinux@lsi.com
      Signed-off-by: NSumant Patro <sumant.patro@lsi.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      cd96d96f
  2. 29 7月, 2006 1 次提交
    • J
      [SCSI] megaraid_{mm,mbox}: 64-bit DMA capability checker · fbf60802
      Ju, Seokmann 提交于
      This patch contains
      - a fix for 64-bit DMA capability check in megaraid_{mm,mbox} driver.
      - includes changes (going back to 32-bit DMA mask if 64-bit DMA mask
      failes) suggested by James with previous patch.
      - addition of SATA 150-4/6 as commented by Vasily Averin.
      
      With patch, the driver access PCIconfiguration space with dedicated
      offset to read a signature. If the signature read, it means that the
      controller has capability to handle 64-bit DMA.
      Without this patch, the driver used to blindly claim 64-bit DMA
      capability.
      The issue has been reported by Vasily Averin [vvs@sw.ru].
      Thank you Vasily for the reporting.
      
      Signed-Off By: Seokmann Ju <seokmann.ju@lsil.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      fbf60802
  3. 28 4月, 2006 1 次提交
  4. 14 12月, 2005 1 次提交
  5. 21 5月, 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