> 1. IDE status read does not work. (But am I understand correctly > that IDE works well if IRQ is unspecified? Then this is hardly > an issue.) > 2. IDE interrupt comes when it should not. I'd recommend to use > oscilloscope to find out what is happening there, that is, if > the drive actually deasserts its irq line after status read. > If so, than this could be a PIC problem. > > What is the platform on which you're observing the issue, btw? Another possibility is that you got the wrong interrupt number in the device-tree... Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
