1. 27 6月, 2007 2 次提交
  2. 21 6月, 2007 6 次提交
  3. 11 6月, 2007 2 次提交
    • T
      libata: limit post SRST nsect/lbal wait to ~100ms · e141d999
      Tejun Heo 提交于
      After SRST, libata used to wait for nsect/lbal to be set to 1/1 for
      the slave device.  However, some ATAPI devices don't set nsect/lbal
      after SRST and the wait itself isn't too useful as we're gonna wait
      for !BSY right after that anyway.
      
      Before reset-seq update, nsect/lbal wait failure used to be ignored
      and caused 30sec delay during detection.  After reset-seq, all
      timeouts are considered error conditions making libata fail to detect
      such ATAPI devices.
      
      This patch limits nsect/lbal wait to around 100ms.  This should give
      acceptable behavior to such ATAPI devices while not disturbing the
      heavily used code path too much.
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      e141d999
    • T
      libata: force PIO on IOMEGA ZIP 250 ATAPI · 5acd50f6
      Tejun Heo 提交于
      IOMEGA ZIP 250 ATAPI claims MWDMA0 support but fails SETXFERMODE if
      asked to configure itself to MWDMA0.  Force PIO.
      
      This fixes bugzilla bug#8497.
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Cc: Calvin Walton <calvin.walton@gmail.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      5acd50f6
  4. 10 6月, 2007 13 次提交
  5. 09 6月, 2007 1 次提交
  6. 05 6月, 2007 2 次提交
    • D
      65d8bac3
    • T
      libata: always use polling SETXFER · 464cf177
      Tejun Heo 提交于
      Several people have reported LITE-ON LTR-48246S detection failed
      because SETXFER fails.  It seems the device raises IRQ too early after
      SETXFER.  This is controller independent.  The same problem has been
      reported for different controllers.
      
      So, now we have pata_via where the controller raises IRQ before it's
      ready after SETXFER and a device which does similar thing.  This patch
      makes libata always execute SETXFER via polling.  As this only happens
      during EH, performance impact is nil.  Setting ATA_TFLAG_POLLING is
      also moved from issue hot path to ata_dev_set_xfermode() - the only
      place where SETXFER can be issued.
      
      Note that ATA_TFLAG_POLLING applies only to drivers which implement
      SFF TF interface and use libata HSM.  More advanced controllers ignore
      the flag.  This doesn't matter for this fix as SFF TF controllers are
      the problematic ones.
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      464cf177
  7. 04 6月, 2007 1 次提交
  8. 28 5月, 2007 1 次提交
  9. 26 5月, 2007 2 次提交
  10. 25 5月, 2007 10 次提交