| commit | 877facd0ce77d172f6d54eb5f503c82d8f6d8526 | |
| author | Sergei Shtylyov <sshtylyov@ru.mvista.com> | |
| Sat, 18 Apr 2009 15:42:19 +0000 (18 17:42 +0200) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Sat, 2 May 2009 17:24:24 +0000 (2 10:24 -0700) | ||
| tree | 278639742b47b3b8feb57414fad4119fa67ca2e7 | treesnapshot (tar.gz zip) |
| parent | 561bbe9e42cd6b0d0148ac5d36e07b90c8065fa3 | commitdiff |
hpt366: fix HPT370 DMA timeouts
upstream commit: c018f1ee5cf81e58b93d9e93a2ee39cad13dc1ac
The big driver change in 2.4.19-rc1 introduced a regression for many HPT370[A]
chips -- DMA stopped to work completely, only causing endless timeouts...
The culprit has been identified (at last!): it turned to be the code resetting
the DMA state machine before each transfer. Stop doing it now as this counter-
measure has clearly caused more harm than good.
This should fix the kernel.org bug #7703.
Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Signed-off-by: Chris Wright <chrisw@sous-sol.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
upstream commit: c018f1ee5cf81e58b93d9e93a2ee39cad13dc1ac
The big driver change in 2.4.19-rc1 introduced a regression for many HPT370[A]
chips -- DMA stopped to work completely, only causing endless timeouts...
The culprit has been identified (at last!): it turned to be the code resetting
the DMA state machine before each transfer. Stop doing it now as this counter-
measure has clearly caused more harm than good.
This should fix the kernel.org bug #7703.
Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Signed-off-by: Chris Wright <chrisw@sous-sol.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/ide/pci/hpt366.c | diffblobblamehistory |