From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> Date: Fri, 29 Jan 2010 23:25:40 +0000 > The old IDE "maintenance mode" seems to be drifting - the rate of change > is rather high for that claim. I think there's another angle to this. By making the IDE layer build from the same code as the ATA driver, the legacy IDE layer gets an indirect tester base. I like that. However what I don't like is how this is implemented. We shouldn't pretend the data structures are the same by using macros in some header file, we should truly abstract out the data types properly such that these drivers in fact use the same datastructures. For the price of a few series of data structure morphs, we eliminate the tester-base issue of legacy IDE. There's one driver for both ATA and legacy IDE, the stuff in front is just a presentation and probing layer, nothing more. The cost and risk is testing the morphing changes, but I think the scales tip towards making this truly worth it. Bart, thanks for working on this and publishing what you came up with. -- 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
