> Obviously it is going to change per command -- because different > commands have different sizes. I was thinking that we could call the > driver to see if it can handle a particular sector size right after we > get the IDENTIFY data. The drivers need to know if you are going to be using odd sizes regularly so they can pick between - I do this fine who cares (most chips) - Er uh wtf its not 512 byts (some chip state machines) - FIFO off (performance hit) for this disk - FIFO managed for the odd command thats a funny size - Various other levels of software managed controller thumping It's not a passive thing and we'd want to do it post identify on the drive pair as it'll often need per channel decisions (eg on FIFO) Alan -- 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
