Add NV storage fields for firmware flags
1) Did firmware attempt RW slot B before slot A?
2) Did firmware check the kernel keyblock signature, or just its hash?
Added crossystem support as well.
BUG=chrome-os-partner:1657
TEST=make && make runtests
Review URL: http://codereview.chromium.org/6597011
Change-Id: I0d743ae87cedd938ba988170793717d3fdbd8ce9
diff --git a/utility/crossystem_main.c b/utility/crossystem_main.c
index 07c14e4..5352b4d 100644
--- a/utility/crossystem_main.c
+++ b/utility/crossystem_main.c
@@ -33,6 +33,7 @@
{"savedmem_base", 0, 0, "RAM debug data area physical address", "0x%08x"},
{"savedmem_size", 0, 0, "RAM debug data area size in bytes"},
{"fmap_base", 0, 0, "Main firmware flashmap physical address", "0x%08x"},
+ {"tried_fwb", 0, 0, "Tried firmware B before A this boot"},
/* Read-only strings */
{"hwid", 1, 0, "Hardware ID"},
{"fwid", 1, 0, "Active firmware ID"},
@@ -40,6 +41,7 @@
{"mainfw_act", 1, 0, "Active main firmware"},
{"mainfw_type", 1, 0, "Active main firmware type"},
{"ecfw_act", 1, 0, "Active EC firmware"},
+ {"kernkey_vfy", 1, 0, "Type of verification done on kernel key block"},
/* Writable integers */
{"recovery_request", 0, 1, "Recovery mode request (writable)"},
{"dbg_reset", 0, 1, "Debug reset mode request (writable)"},