Dear Andy Fleming,
In message BANLkTi=+tGpet6BDHiY_7Xx2dyiDbcu9DQ@mail.gmail.com you wrote:
It's just that the other way would also be possible. I re-read the thread where this was discussed, and while I definitely agree that the originally proposed solution was highly error-prone, I think *allowing* users to do this is fine:
mmc read <dev>:<part> <addr> <blk> <cnt>
Is there a reason that this wouldn't work with the current model?
Of course it works, but I don't like it:
- I think different user interfaces for the same thing are usually confusing. - Defining a policy will be necessay, and even then it may cause side effects. For example, does "mmc read <dev>:<part> ..." change the "current" device settings, or are these only temporarily active while the command is running? etc.
Best regards,
Wolfgang Denk