Hello,
Mark Lord wrote:
All I can offer on this, is that "-i" is *100%* dependent upon
whatever the IDE driver in the kernel decides to tell us.
Whereas "-I" (uppercase) is what the drive itself tells hdparm.
in the meantime, I detected "-I" as well, which seems to work as it is
expected:
hdparm -tTI:
...
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 1
Standby timer values: spec'd by Standard, no device specific
minimum
R/W multiple sector transfer: Max = 16 Current = ?
Recommended acoustic management value: 254, current value: 0
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
I don't know why "-i" outputs not the same - maybe this report should be
CC'd to someone who deals with that on kernel or chipset driver basis?
I plan on removing "-i" relatively soon (next year or so)
since it will not be supported at all by libata ("-I" works, though).
Or perhaps simply having "-i" use the data from "-I",
if people want hdparm to keep the abbreviated output format.
I like the "short" output from "-i" and found it somehow difficult on
the first encountering of hdparm to get all the parameters right - at
the moment hdparm seems to "mix" features for beginners and experts,
maybe you could provide an beginner and an expert mode like in other
tools (fdisk), just be deviding the parameters in two groups?
Just my 2 cents,
Andre
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
