Douglas Gilbert wrote:
Putting this post on this list might head off
more (private) emails on this subject.
sdparm uses the START STOP UNIT SCSI command to start
and stop (spin up and spin down) SCSI devices.
Currently libata does not implement that SCSI command.
[Hopefully Jeff contradicts
Douglas Gilbert wrote:
sdparm uses the START STOP UNIT SCSI command to start
and stop (spin up and spin down) SCSI devices.
Currently libata does not implement that SCSI command.
[Hopefully Jeff contradicts me.]
Correct.
Someone should submit a libata patch for this!
Jeff
-
To
Jeff Garzik wrote:
Douglas Gilbert wrote:
sdparm uses the START STOP UNIT SCSI command to start
and stop (spin up and spin down) SCSI devices.
Currently libata does not implement that SCSI command.
[Hopefully Jeff contradicts me.]
Correct.
Someone should submit a libata patch for this!
Douglas Gilbert wrote:
A further thought about implementing the START STOP
UNIT SCSI command in libata: the TEST UNIT READY
SCSI command should become more than just a no-op.
Correct.
Jeff
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message
Douglas Gilbert wrote:
I could have a go at the SCSI half of it. According to
SAT, START STOP UNIT should only be allowed for non-packet
ATA devices. I assume your SATAPI code will the bypass
libata-scsi.c SAT layer.
Mostly. There is still a few translation bits in there. 99% bypass,
not
5 matches
Mail list logo