> So just because we fit a chip, we're suddenyly a special case? Moving > to libata has ignored the code in the old IDE driver which ensures that > the IRQ driver is used. I have no idea how many other systems have this > same problems, but the systems we've shipped have had this chip setup > for nearly 10 years now. Yes and it happened to work by luck. Now it doesn't, instead standards compliant systems work better. > I admit the original fix is wrong, the change should be handled by some > form of callback or a method of passing the interrupt numbers in when > registering with the libata-sff.c driver. Why do you want to hack up the libata driver code ? You've said yourself you have put the chip into native mode yet are using the legacy interrupts. Thats misconfiguration and you can undo that by configuring the chip right in the first place - as per the BIOS guide. -- 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
