summaryrefslogtreecommitdiff
path: root/common/fmap.c
diff options
context:
space:
mode:
authorBill Richardson <wfrichar@chromium.org>2012-05-08 14:34:03 -0700
committerBill Richardson <wfrichar@chromium.org>2012-05-10 17:27:36 -0700
commit8101b7131651e344807d2bd0ec77542b3196a653 (patch)
treedf058964eee0efdfe82cfa2bd0f7e6ef013c45b8 /common/fmap.c
parent058079977e3d94d05d40e44144549b9d4e391144 (diff)
downloadchrome-ec-8101b7131651e344807d2bd0ec77542b3196a653.tar.gz
Enable verified boot for EC firmware
BUG=chrome-os-partner:7459 TEST=manual In the chroot: cd src/platform/ec make BOARD=link The firmware image (build/link/ec.bin) is signed with dev-keys. Reflash the EC and try it, and it should verify and reboot into RW A. Additional tests (setting USE_RO_NORMAL, poking random values into VBLOCK_A or FW_MAIN_A to force RW B to run, etc.) are left as an exercise for the reader. I've done them and they work, though. Change-Id: I29a23ea69aef02a11aebd4af3b043f6864723523 Signed-off-by: Bill Richardson <wfrichar@chromium.org>
Diffstat (limited to 'common/fmap.c')
-rw-r--r--common/fmap.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/common/fmap.c b/common/fmap.c
index 3f7baceb93..40524c21ef 100644
--- a/common/fmap.c
+++ b/common/fmap.c
@@ -83,7 +83,6 @@ const struct _ec_fmap {
.area_flags = FMAP_AREA_STATIC | FMAP_AREA_RO,
},
{
- /* FIXME(wfrichar): GBB != FMAP. Use the right terms */
.area_name = "FMAP",
.area_offset = (uint32_t)&ec_fmap,
.area_size = sizeof(ec_fmap),