summaryrefslogtreecommitdiff
path: root/extra/usb_spi
diff options
context:
space:
mode:
authorWei-Cheng Xiao <garryxiao@chromium.org>2018-10-17 13:16:34 +0800
committerchrome-bot <chrome-bot@chromium.org>2018-10-25 15:19:00 -0700
commit392ff3028b1619c6d0efd3ae93a5cac998497bc6 (patch)
treeb3a61338fb0f1caf7ddba1ab564e5d965f037175 /extra/usb_spi
parent80c5282b54a53702aee9078226efab55c5869861 (diff)
downloadchrome-ec-392ff3028b1619c6d0efd3ae93a5cac998497bc6.tar.gz
gsctool: add machine output support (-M) to chip board ID (-i, -O)
Now gsctool can print out GSC board ID in a machine-friendly way. This allows other programs (e.g., debugd) to parse the output. This is the final CL that adds machine output support to gsctool during verify_ro migration. BRANCH=none BUG=None TEST=manually run gsctool -M -i and gsctool -O verify_ro.db -M on a soraka device connected with a naultilus and check the board ID part in the outputs. Sample output (the board ID part is identical in the outputs of both commands): BID_TYPE=5a534b4d BID_TYPE_INV=a5acb4b2 BID_FLAGS=00007f80 Signed-off-by: Wei-Cheng Xiao <garryxiao@chromium.org> Change-Id: Ia275806672c08841c5b5fcc7758d8e0c777b3fc9 Reviewed-on: https://chromium-review.googlesource.com/1286312 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Wei-Cheng Xiao <garryxiao@chromium.org> Reviewed-by: Andrey Pronin <apronin@chromium.org>
Diffstat (limited to 'extra/usb_spi')
0 files changed, 0 insertions, 0 deletions