summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIdwer Vollering <vidwer@gmail.com>2017-09-01 17:24:18 +0200
committerIdwer Vollering <vidwer@gmail.com>2017-09-04 08:27:27 +0000
commit1918c81d65ecfdcb64fa811debd919b2a25cf47d (patch)
tree39b471911365626488cdc4c7f29e7bba4a56d7d8
parent3f43edc351a6bbbffdedbdd7fe1333f9d28b8b5d (diff)
util/board_status: do a spell check
Change-Id: Ie39be471851586076343b8e9454a9140d4664b8d Signed-off-by: Idwer Vollering <vidwer@gmail.com> Reviewed-on: https://review.coreboot.org/21322 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net> Reviewed-by: Sumeet R Pawnikar <sumeet.r.pawnikar@intel.com>
-rw-r--r--util/board_status/README12
1 files changed, 6 insertions, 6 deletions
diff --git a/util/board_status/README b/util/board_status/README
index 23378262dd..c462e7de2c 100644
--- a/util/board_status/README
+++ b/util/board_status/README
@@ -9,13 +9,13 @@ Else you will need to have to set the default log level at compile
time, to do that go in "Console --->" in make menuconfig, then set
"Default console log level" to SPEW
-Rereference:
-------------
+Reference:
+----------
[1] in make menuconfig you should have: [*] Use CMOS for configuration values
This option is also known as CONFIG_USE_OPTION_TABLE in Kconfig.
-Information trough SSH
+Information through SSH
======================
-board_status.sh can gather information trough ssh with the -r
+board_status.sh can gather information through ssh with the -r
option.
When using "-r <host>", The script will attempt to log into
@@ -28,10 +28,10 @@ That can be achieved with the use of SSH keys and ssh-agent.
board_status.sh expects the remote host to have the following
programs in its path: cbmem, dmesg
-Boot log gathering trough a serial port
+Boot log gathering through a serial port
=======================================
When using -s </dev/xxx>, board_status.sh starts by retrieving the
-boot log trough the serial port.
+boot log through the serial port.
To produce such logs, power off the board, run board_status.sh
with the right arguments, power on the board.