1. 01 2月, 2006 1 次提交
  2. 15 1月, 2006 4 次提交
  3. 14 12月, 2005 3 次提交
  4. 02 12月, 2005 1 次提交
  5. 30 11月, 2005 1 次提交
  6. 09 11月, 2005 2 次提交
  7. 29 10月, 2005 2 次提交
  8. 20 9月, 2005 2 次提交
    • M
      [SCSI] fusion SAS support (mptsas driver) updates · 466544d8
      Moore, Eric Dean 提交于
      Summary of Changes:
      * splitting mpt_interrupt per Christophs suggestion
      about a month ago
      * rename ScsiCfgData to SpiCfgData structure,
      then move all the raid related info into
      new structure called RaidCfgData.  This is
      done because SAS supports RAID, as well as SPI,
      so the raid stuff should be seperate.
      * incorrect timeout calculation for cntdn
      inside WaitForDoorbellAck and WaitForDoortbellInt
      * add support for interpreting SAS Log Info
      * Increase Event Log Size from 0xA to 0x32
      * Fix bug in mptsas/mptfc/mptspi - when controller
      has Initiator Mode Disabled, and only running in
      TargetMode, the mptctl would panic when loading.
      The fix is to return 0, instead of -ENODEV, in
      SCSI LLD respective probe routines
      * Fix bug in mptlan.c - driver will panic if
      there is host reset, due to dev being set to
      zero in mpt_lan_ioc_reset
      * Fix's for SPI - Echo Buffer
      * Several fix's in mptscsih_io_done - FCP Response
      info, RESIDUAL_MISMATCH, Data Underrun, etc.
      * Cleanup Error Handling - EH handlers,
      mptscsih_flush_cmds, and zeroing out ScsiLookup
      from mptscsih_qcmd
      * Cleanup asyn event handling from
      mptscsih -> mptscsih_event_process.  Also
      added support for SAS Persistent Table Full,
      an asyn event
      Signed-off-by: NEric Moore <Eric.Moore@lsil.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      466544d8
    • C
      [SCSI] fusion core changes for SAS support · 82ffb671
      Christoph Hellwig 提交于
       - various bits for SAS support from the LSI driver.
       - use the device private data for the fusion target private data.
         this should be using the midlayer target data framework, but we
         can't move over to that until fusion has been switched to the
         generic DV code
       - use target ID and channel from the fusion target private data,
         because those in scsi_device will be different for mptsas
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      82ffb671
  9. 05 9月, 2005 1 次提交
  10. 21 5月, 2005 4 次提交
  11. 17 4月, 2005 2 次提交