Hi Darren!
Did you understand what Puthikorn was asking for?
linux-mmc maintainers don't care about Chrome-OS branches
(stabilize-5784.0.B). Puthikorn was just pointing out the patch needs
to be against something that linux-mmc can build.
This Kingston support patch is a good example of why
I am interested in this topic too.
I have some issues want to discuss here.
Should we check the firmware binary file before we execute FFU? (for
example, execute checksum to
verify firmware bin file) Should eMMC controller vendors cover this issue?
Another issue is about interrupt, because FFU
Hi Darren
Thanks for the patch. To make the reviewers job easier, could you send the patch
against [RFC PATCH 1/1 v7]mmc: Support-FFU-for-eMMC-v5.0 by avi.
You can find that patch at http://www.spinics.net/lists/linux-mmc/msg26519.html
Also, please include the Signed-off-by: field in the patch.
