> while IDE thinks that IRQ might be lost and complete the command if the > TF status register says so.
For PATA at least that makes a lot of sense. It would probably make the Promise driver a lot more stable too. > It could be that the particular device doesn't raise IRQ on certain > error conditions but updates TF registers. After timeout, IDE completes > the command with the indicated error while libata ignores the status and > resets the device. And loses the important information like media errors > libata never touches TF register after timeout because some controllers > lock up hard if TF register is read after certain error conditions > (event the status register). Should that not then be a per host flag ? Alan - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
