diff options
| author | Tom Hughes <tomhughes@chromium.org> | 2022-06-08 10:42:47 -0700 |
|---|---|---|
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | 2022-06-08 22:01:36 +0000 |
| commit | f49eb6f8944670012c0d6875ce302a9241c628f8 (patch) | |
| tree | 28520d0f3ad2bd971573b703709f9893d69528a3 | |
| parent | 1fe2899ffe9800af116565c31e5d969d62abb40c (diff) | |
| download | chrome-ec-f49eb6f8944670012c0d6875ce302a9241c628f8.tar.gz | |
docs/fingerprint: Run mdformat
BRANCH=none
BUG=none
TEST=view in gitiles
Signed-off-by: Tom Hughes <tomhughes@chromium.org>
Change-Id: I20caf005a0692d7e1d89528c87bb49b7743b8199
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3696148
Reviewed-by: Andrea Grandi <agrandi@google.com>
| -rw-r--r-- | docs/fingerprint/fingerprint-debugging.md | 4 | ||||
| -rw-r--r-- | docs/fingerprint/fingerprint.md | 8 |
2 files changed, 6 insertions, 6 deletions
diff --git a/docs/fingerprint/fingerprint-debugging.md b/docs/fingerprint/fingerprint-debugging.md index 772ea91e81..d098ca4427 100644 --- a/docs/fingerprint/fingerprint-debugging.md +++ b/docs/fingerprint/fingerprint-debugging.md @@ -32,8 +32,8 @@ used for JTAG and SWD for ARM devices. is the only software required for flashing. * In order to perform breakpoint debugging, you will need a tool that supports connecting `gdbserver`. This document will assume [CLion] \(Googlers see - [CLion for ChromeOS]) and was tested with `JLink v6.94a`. Alternatively, - you can use [Ozone], a standalone debugger from Segger. + [CLion for ChromeOS]) and was tested with `JLink v6.94a`. Alternatively, you + can use [Ozone], a standalone debugger from Segger. ## JLink Software {#software} diff --git a/docs/fingerprint/fingerprint.md b/docs/fingerprint/fingerprint.md index f5e372c8f5..04f5a6bab9 100644 --- a/docs/fingerprint/fingerprint.md +++ b/docs/fingerprint/fingerprint.md @@ -52,8 +52,8 @@ to determine the FPMCU that it contains: (dut) $ cros_config /fingerprint board ``` -Alternatively, if you have a Chromium OS build, you can use [ChromeOS Config] -in the chroot to determine the FPMCU: +Alternatively, if you have a Chromium OS build, you can use [ChromeOS Config] in +the chroot to determine the FPMCU: ```bash (chroot) $ cros_config_host -c /build/<BOARD>/usr/share/chromeos-config/yaml/config.yaml -m <MODEL> get /fingerprint board @@ -529,8 +529,8 @@ detail. The fingerprint sensor may only be included on certain SKUs for a given device. The fingerprint code uses [ChromeOS Config] to determine whether a device has a fingerprint sensor or not. For each SKU, there is an associated -[fingerprint config][ChromeOS Config fingerprint]. [ChromeOS Config] -determines the [SKU information][ChromeOS Config SKU] (and thus the +[fingerprint config][ChromeOS Config fingerprint]. [ChromeOS Config] determines +the [SKU information][ChromeOS Config SKU] (and thus the [fingerprint config][ChromeOS Config fingerprint]) from [CBI Info]. The SKU for a given device can be found by viewing `chrome://system/#platform_identity_sku`. |