diff options
author | peter fuerst <post@pfrst.de> | 2007-02-12 15:27:17 +0100 |
---|---|---|
committer | James Bottomley <jejb@mulgrave.il.steeleye.com> | 2007-02-16 09:38:12 -0600 |
commit | 8f3334edae93f8b664417f4140d4d9dc9a003fe4 (patch) | |
tree | 4d37601784b78e1f699727c3d8e0e624db6c59f6 /drivers/scsi/ide-scsi.c | |
parent | a5d8421b2f03e46f02cc02066b186fdbc0f590a6 (diff) | |
download | kernel_samsung_smdk4412-8f3334edae93f8b664417f4140d4d9dc9a003fe4.zip kernel_samsung_smdk4412-8f3334edae93f8b664417f4140d4d9dc9a003fe4.tar.gz kernel_samsung_smdk4412-8f3334edae93f8b664417f4140d4d9dc9a003fe4.tar.bz2 |
[SCSI] sgiwd93: interfacing to wd33c93
1) sgiwd93 used to switch off asynchronous mode on the wd33c93, discarding
any "nosync"-requests from the commandline.
But we need to allow "nosync"-requests for selected devices, for example
the Pioneer DVD305S.
(For the curious: this device accepts the SDTR from wd33c93 and success-
fully sends inquiry data in sync mode, but after the data phase in the
inquiry command does an unexpected disconnect, seemingly sending no
"status" or "command complete". Forcing async transfers makes it work
together flawlessly with the wd33c93. Of course, preferable would be, to
implement wd33c93's "resume command" stuff, but that probably will not
come soon.)
2) Maximize benefit from the preceding Fast SCSI patch for wd33c93 by passing
the higher input-clock frequency explicitely. To be applied after the
mentioned wd33c93 patch.
Signed-off-by: peter fuerst <post@pfrst.de>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Diffstat (limited to 'drivers/scsi/ide-scsi.c')
0 files changed, 0 insertions, 0 deletions