Workaround for Gigabyte i-RAM, which always reports 0x00 as error code after bus reset,

git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@30474 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Marcus Overhagen 2009-04-27 22:09:31 +00:00
parent 6241755766
commit ca2a912bc9
1 changed files with 6 additions and 1 deletions

View File

@ -354,7 +354,12 @@ ATAChannel::Reset(bool *presence, uint16 *signatures)
&& (i > 0 || taskFile.read.error != 0x81)) { && (i > 0 || taskFile.read.error != 0x81)) {
TRACE_ERROR("device %d failed, error code is 0x%02x\n", i, TRACE_ERROR("device %d failed, error code is 0x%02x\n", i,
taskFile.read.error); taskFile.read.error);
continue; // Workaround for Gigabyte i-RAM, which always reports 0x00
// TODO: find something nicer
if (i == 1 && taskFile.read.error == 0x00) {
TRACE_ERROR("continuing anyway...\n");
} else
continue;
} }
if (i == 0 && taskFile.read.error >= 0x80) { if (i == 0 && taskFile.read.error >= 0x80) {