summaryrefslogtreecommitdiff
path: root/util/kbc1126
diff options
context:
space:
mode:
authorMartin Roth <martin@coreboot.org>2021-02-14 13:52:00 -0700
committerMartin Roth <martinroth@google.com>2021-02-17 17:30:05 +0000
commit5c7341331dd6fbb4dd9aaaa68693b83c3d47fe66 (patch)
tree8ff0b45a117f1fa4db7e2d8477c5cc7a8c0e80c1 /util/kbc1126
parent175e4c59a0025dc4636669734ae4ed756cb1af5f (diff)
downloadcoreboot-5c7341331dd6fbb4dd9aaaa68693b83c3d47fe66.tar.gz
treewide: Remove trailing whitespace
Remove trailing whitespace in files that aren't typically checked. Signed-off-by: Martin Roth <martin@coreboot.org> Change-Id: I8dfffbdeaadfa694fef0404719643803df601065 Reviewed-on: https://review.coreboot.org/c/coreboot/+/50704 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Angel Pons <th3fanbus@gmail.com>
Diffstat (limited to 'util/kbc1126')
-rw-r--r--util/kbc1126/README.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/util/kbc1126/README.md b/util/kbc1126/README.md
index 8f39069793..776272cc2a 100644
--- a/util/kbc1126/README.md
+++ b/util/kbc1126/README.md
@@ -20,9 +20,9 @@ I use [radare2](https://radare.org) to analyze the firmware. Open the
firmware image, and we can see 8 bytes at `$s-0x100` (`$s` means the
image size).
- [0x00000000]> x @ $s-0x100
- - offset - 0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF
- 0x00ffff00 fff7 0008 f700 08ff 0000 0000 0000 0000 ................
+ [0x00000000]> x @ $s-0x100
+ - offset - 0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF
+ 0x00ffff00 fff7 0008 f700 08ff 0000 0000 0000 0000 ................
X86 machines map the firmware at the end of the memory address
space. These 8 bytes tell the address of the two blobs, which we call
@@ -33,9 +33,9 @@ Let's look at FW1. The first two bytes mean the address of FW1 is
3 are just complements of byte 1 and 2 (in this case,
0x0008=0xffff-0xfff7).
- [0x00000000]> x @ $s-0x900
- - offset - 0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF
- 0x00fff700 fc07 c13e 02ff 1000 0000 0000 0000 0000 ...>............
+ [0x00000000]> x @ $s-0x900
+ - offset - 0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF
+ 0x00fff700 fc07 c13e 02ff 1000 0000 0000 0000 0000 ...>............
Both FW1 and FW2 use the same format: the first two bytes is payload
length, then a two-byte checksum, then the payload. The payload length