Skip to content

GitLab

Switch branch/tag
  1. 08 Aug, 2019 1 commit
  3. 15 Dec, 2018 1 commit
  5. 08 Dec, 2018 2 commits
  7. 27 Mar, 2018 1 commit
  9. 17 Feb, 2018 7 commits
  11. 20 Mar, 2017 2 commits
  13. 16 Mar, 2017 1 commit
  15. 01 Sep, 2016 1 commit
  17. 29 Aug, 2016 5 commits
  19. 23 Jun, 2016 1 commit
  21. 07 Jun, 2016 1 commit
  23. 11 May, 2016 1 commit
  25. 08 Mar, 2016 1 commit
    • Avi Shchislowski's avatar
      mmc_utils: add ffu support · 89cd01ed
      Avi Shchislowski authored 
      

Adding support for field firmware update over multiple command ioctl.
As multiple command ioctl is supported only from kernel 4.4, this patch
should be used against kernel 4.4 and above.

Known issues:
- There is no support for Multiple Block write commands (CMD25) in existing
  IOCTL implementation
- In case MODE_OPERATION_CODES field is not supported by the device
  manual reset of the device/platform is required.
  The reset issue discussed in another email thread - " [RFC 0/6] mmc:
  Field Firmware Update"
Signed-off-by: default avatarYaniv Agman <yaniv.agman@sandisk.com>
Signed-off-by: default avatarAvi Shchislowski <avi.shchislowski@sandisk.com>
Signed-off-by: default avatarChris Ball <chris@printf.net>
      89cd01ed
  27. 26 Feb, 2016 1 commit
  29. 18 Nov, 2015 2 commits
  31. 01 May, 2015 4 commits
  33. 25 Mar, 2015 1 commit
  35. 12 Aug, 2014 3 commits
    • Chris Ball's avatar
      Fit usage to 80 cols · f4eb2415
      Chris Ball authored 
      
Signed-off-by: default avatarChris Ball <chris@printf.net>
      f4eb2415
    • Roman Peniaev's avatar
      mmc-utils: RPMB: add support for 4 rpmb operations · c6cb053e
      Roman Peniaev authored 
      

mmc rpmb write-key <rpmb device> <key file>
  Program authentication key which is 32 bytes length and stored in the specified file.
  Also you can specify '-' instead of key file path and utility will read the key from stdin.
  BEWARE: key can be programmed only once!
  Example:
    $ echo -n AAAABBBBCCCCDDDDEEEEFFFFGGGGHHHH | mmc rpmb write-key /dev/mmcblk0rpmb -

mmc rpmb read-counter <rpmb device>
  Counter value for the <rpmb device> will be read to stdout.

mmc rpmb read-block <rpmb device> <address> <blocks count> <output file> [key file]
  Blocks of 256 bytes will be read from <rpmb device> to output file or stdout if '-'
  is specified instead of regular path. If key is specified - read data will be verified.
  Instead of regular path you can specify '-' and key will be read from stdin.
  Example:
    $ echo -n AAAABBBBCCCCDDDDEEEEFFFFGGGGHHHH | \
        mmc rpmb read-block /dev/mmcblk0rpmb 0x02 2 /tmp/block -
  or read the block without verification
    $ mmc rpmb read-block /dev/mmcblk0rpmb 0x02 2 /tmp/block

mmc rpmb write-block <rpmb device> <address> <256 byte data file> <key file>
  Block of 256 bytes will be written from data file to <rpmb device>.
  Also you can specify '-' instead of key file path or data file and utility will read the
  data from stdin.
  Example:
    $ (awk 'BEGIN {while (c++<256) printf "a"}' | echo -n AAAABBBBCCCCDDDDEEEEFFFFGGGGHHHH) | \
      mmc rpmb write-block /dev/mmcblk0rpmb 0x02 - -
Signed-off-by: default avatarRoman Pen <r.peniaev@gmail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Cc: Ben Gardiner <bengardiner@nanometrics.ca>,
Signed-off-by: default avatarChris Ball <chris@printf.net>
      c6cb053e
    • Roman Peniaev's avatar
      mmc-utils: RPMB: add HMAC SHA256 support · 35c31fea
      Roman Peniaev authored 
      RPMB requires digital signature of the message.  Take the implementation
of HMAC SHA256 from this place https://github.com/ogay/hmac.git



Actually this is BSD license, IANAL but according to my understanding
nothing terrible will happen if we provide all the original copyrights.
Signed-off-by: default avatarRoman Pen <r.peniaev@gmail.com>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>
Signed-off-by: default avatarChris Ball <chris@printf.net>
      35c31fea
  37. 23 Jan, 2014 1 commit
  39. 26 Sep, 2013 3 commits