Hi everyone,
Sorry, I'm missing something hopefully-obvious about this patch:
Which command does someone use to run the new ext_csd code in lsmmc?
I thought that this patch would add lsmmc's ext_csd parsing to the
existing "mmc extcsd read" command. But it doesn't seem to do that --
it duplicates the code, so there are two separate, unrelated extcsd
parsers in:
* lsmmc.c:print_mmc_ext_csd()
* mmc_cmds.c:do_read_extcsd().
I don't think that's what Ulf's suggestion intended -- as I read it,
he was hoping to see the parsers merged to make one better parser.
I'd like to see that too, though I understand that it's more work.
And I'm still confused, as above, about how to actually use the new
extcsd parser, because "mmc extcsd read" doesn't seem to be it, and
the new commands added:
int do_read_scr(int argc, char **argv);
int do_read_cid(int argc, char **argv);
int do_read_csd(int argc, char **argv);
.. don't seem to be it either, since they don't pass "EXT_CSD" to
process_dir(), which is the only way I can see to activate lsmmc's
ext_csd printer. How's it supposed to work?
Also:
On Fri, Feb 05 2016, Baolin Wang wrote:
> +void usage(void)
> +int parse_opts(int argc, char **argv, struct config *config)
These functions could be totally removed now, I think?
Thanks!
- Chris.
--
Chris Ball <http://printf.net/>
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
