Alan Cox wrote:
The fussy bit is that these commands require a non-standard
sector size, usually 520 bytes instead of 512.
Do we always know the worst case here as this breaks my pending patch to
use bounce buffers for PIO so we transfer with IRQ enabled and I need to
know the correct new worst case size.
Ugh. The drives default to 520 bytes (always),
but can specify a different, preferred, length in
the IDENTIFY data. A SETFEATURES command is required
to change the setting from the default of 520.
In practice, I only ever use 520, because (1) it always works,
and (2) I'm only trying to corrupt drives, not write correct stuff. ;)
So we could modify the patch to limit it to a specific maximum,
or always require exactly 520 bytes without any hardship.
???
Cheers
-
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