1. 27 3月, 2007 2 次提交
    • S
      ide: use correct IDE error recovery · 513daadd
      Suleiman Souhlal 提交于
      IDE error recovery is using IDLE IMMEDIATE if the drive is busy or has DRQ set.
      This violates the ATA spec (can only send IDLE IMMEDIATE when drive is not
      busy) and really hoses up some drives (modern drives will not be able to
      recover using this error handling).  The correct thing to do is issue a SRST
      followed by a SET FEATURES command.  This is what Western Digital recommends
      for error recovery and what Western Digital says Windows does.  It also does
      not violate the ATA spec as far as I can tell.
      
      Bart:
      * port the patch over the current tree
      * undo the recalibration code removal
      * send SET FEATURES command after checking for good drive status
      * don't check whether the current request is of REQ_TYPE_ATA_{CMD,TASK}
        type because we need to send SET FEATURES before handling any requests
      * some pre-ATA4 drives require INITIALIZE DEVICE PARAMETERS command before
        other commands (except IDENTIFY) so send SET FEATURES only if there are
        no pending drive->special requests
      * update comments and patch description
      * any bugs introduced by this patch are mine and not Suleiman's :-)
      Signed-off-by: NSuleiman Souhlal <suleiman@google.com>
      Acked-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NBartlomiej Zolnierkiewicz <bzolnier@gmail.com>
      513daadd
    • B
      ide: revert "ide: fix drive side 80c cable check, take 2" for now · f68d9320
      Bartlomiej Zolnierkiewicz 提交于
      "ide: fix drive side 80c cable check, take 2" patch from Tejun Heo (commit
      fab59375) fixed 80c bit test (bit13 of word93)
      but we also need to fix master/slave IDENTIFY order (slave device should be
      probed first in order to make it release PDIAG- signal) and we should also
      check for pre-ATA3 slave devices (which may not release PDIAG- signal).
      
      [ Unfortunately the fact that IDE driver doesn't reset devices itself helps
        only a bit as it seems that some BIOS-es reset ATA devices after programming
        the chipset, some BIOS-es can be set to not probe/configure selected devices,
        there may be no BIOS in case of add-on cards etc. ]
      
      Since we are quite late in the release cycle and the required changes will
      affect a lot of systems just revert the fix for now.
      
      [ Please also see libata commit f31f0cc2. ]
      
      Thanks goes out to Fernando Mitio Yamada for reporting the problem
      and patiently testing patches.
      Acked-by: NTejun Heo <htejun@gmail.com>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: NBartlomiej Zolnierkiewicz <bzolnier@gmail.com>
      f68d9320
  2. 04 3月, 2007 1 次提交
  3. 17 2月, 2007 3 次提交
  4. 03 10月, 2006 1 次提交
    • A
      [PATCH] ide: Fix crash on repeated reset · 913759ac
      Alan Cox 提交于
      Michal Miroslaw reported a problem (bugzilla #7023) where a user initiated
      reset while the IDE layer was already resetting the channel caused a crash,
      and provided a rough fix.
      
      This is a slightly cleaner version of the fix which tracks the reset state
      and blocks further reset requests while a reset is in progress.
      
      Note this is not a security issue - random end users can't access the
      ioctl in question anyway.
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Cc: Michal Miroslaw <mirq-linux@rere.qmqm.pl>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      913759ac
  5. 01 8月, 2006 1 次提交
  6. 01 7月, 2006 1 次提交
  7. 29 6月, 2006 1 次提交
  8. 23 6月, 2006 1 次提交
  9. 04 2月, 2006 1 次提交
  10. 10 11月, 2005 1 次提交
  11. 13 9月, 2005 1 次提交
  12. 28 6月, 2005 1 次提交
  13. 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