On Thu, 13 Dec 2007 17:08:16 +0900
"Kyungmin Park" <[EMAIL PROTECTED]> wrote:
>
> In my MMC Spec. (v4.2), there's no problem to read it even though it's
> revision 1.1
>
Well, the spec says that those reserved fields "should be zero". Unfortunately,
people seem to have read this in the IETF sense and not as "the fields MUST be
zero". I.e. I've seen cards where reserved fields contain junk.
> Anyway how do it handle this one? Do you have any idea?
>
The EXT_CSD is read after the CID, so add some table that maps certain
workarounds to specific cards. Then add some bit saying "is really EXT_CSD 1.2"
and check for that bit when parsing the EXT_CSD.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
