> So, why was it serialized before? I assume that either someone noticed the > corruption or someone read some datasheet noting the corruption or someone > reverse engineered some other driver and saw the serialization. The data sheet has some things to say for the 643 abd 646 In PIO mode it says you must check CFR bit 2 (indicates primary interrupt) ARTIM23 bit 4 (secondary interrupt) Both bits can be written 1 to clear the interrupt. The doc doesn't say anything about not touching status but it also uses the word "must" about the other bits so make what you will of it. In DMA mode I would read the BMDMA status in preference to status but the doc doesn't specifically say to do so and simply say it works to the spec. it isn't clear if ARTIM23 and CFR work for reporting/clearing a DMA interrupt. You'd have to try it. ARTIM23 may well need some locking care The 646U2 adds the MRDMODE register so you can check the bits more sanely -- 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
