On 11-11-03 11:46 AM, Tejun Heo wrote:
On Thu, Nov 3, 2011 at 8:34 AM, Douglas Gilbert<dgilbert@xxxxxxxxxxxx> wrote:
That's a pretty poor attitude. I suspect Microsoft care. If so they
would be transitioning away from TEST UNIT READY to REQUEST SENSE
to monitor power conditions and the progress indication.
I was talking about media presence polling. We used to include TUR in
the sequence and there have been some number of devices which worked
fine for a while but lock up eventually. Windows only issues
CHECK_MEDIA_EVENT_STATUS so nobody has tested extended TUR cycles and
Do you mean the GET EVENT STATUS NOTIFICATION command (as there is
no CHECK MEDIA EVENT STATUS command in SCSI or ATA)? If so it is
one of the "good guys" along with the REQUEST SENSE command. And
as I said TUR is not recommended. So looking at MS usage _and_
the standards is a useful guide.
BTW The REQUEST SENSE implemented in the libata's SAT layer is
completely broken (and has been since day one). Is anyone planning
to fix it? An LSI SAS HBA with recent firmware and accessing a
SATA disk is a pretty good example of what a compliant SAT layer
looks like.
nobody is fixing an optical drive EOL'd six months ago either, so what
I or you think or feel doesn't matter in the end. The most important
thing is we provide drivers which allow proper operation and, sadly,
at this point, the best way to get there is following what windows
does. It's not like we lose any functionality that way anyway.
If windows isn't spinning down the drive, it is highly unlikely that
missing that harms anything and it's highly like there are a bunch of
devices which would go "uh... what the hell is this? I don't know
this. osidfjalekjalkgjs". So, there simply is no point at all.
I agree. SCSI and ATA define idle states (with some fuzziness in
the naming) that have timers associated with them. Those
mechanisms seem to work pretty well without the intervention of
commands like START STOP UNIT.
Doug Gilbert
--
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
