Alan Cox wrote: >>> Yes - I'd like it to just work, but I'd like it to just work without >>> breaking anything else, without adding device specific special cases and >>> ideally in a way that makes other stuff that is similarly odd just work >>> too. >> Then, how do you suggest proceeding on it? Without a bus tracer, we >> can't easily tell what Windows is doing and on native SATA skipping >> SETXFER isn't likely to cause any serious problem. It's basically >> noop. > > I would suggest we issue the SETXFER always. If it times out then we will > revalidate the identify data so we can use that to see what mode we are > actually in. Hmmm... our current timeout for SETXFER is 5s, so it wouldn't be nice but not too bad either. Alright, I'll brew up something. -- tejun -- 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
