Alan Cox wrote:
Lots of *other* problems occur instead. Daniel is reporting that if he
makes a stupid request to a buggy drive he gets a reset and the system
continues happily. Even that reset being a reset not a new command issue
is actually us being excessively paranoid.
Sorry if I'm sprouting nonsense here -- I don't have the knowledge that
you all do. However, just wanted to point out that I looked up the info
about that mode page in the MMC specs.
http://www.t10.org/ftp/t10/drafts/mmc4/mmc4r05a.pdf page 513.
"E.3.3 MM Capabilities and Mechanical Status Page (Page Code 2Ah)"
The length of this mode page varies from drive to drive, so there is no
"one size" that you can supply to the SG_IO command (unless you want to
use a stupidly large buffer) to retrieve all the data at once. Instead,
as Tejun describes, you put a short read request in first, look at byte
1 of the page which tells you the length, and then read the whole lot.
Again, ignore me if I'm not contributing anything useful, but I'm
increasingly thinking that the SG_IO command block in question is
perfectly valid, and doing a short read of the mode page in question
(and probably others too) is in fact required before you can know its
true size to do a full read anyway.
Thanks,
Daniel
-
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
