From 750ce06cd5541f999d9b9dac17821e0aa0ff0ec9 Mon Sep 17 00:00:00 2001 From: Arthur Heymans Date: Mon, 21 Oct 2019 19:25:32 +0200 Subject: technotes/coreboot-image-generation: Fix markdown The manifest example has to be marked as code. The Manifest parsing section header should be L2 and finally # is a special character in markdown. Change-Id: I38cb1a508ec9ccb39cb39048de3742a5cb595f7b Signed-off-by: Arthur Heymans Reviewed-on: https://review.coreboot.org/c/coreboot/+/36199 Tested-by: build bot (Jenkins) Reviewed-by: Patrick Georgi --- .../technotes/2015-11-rebuilding-coreboot-image-generation.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'Documentation/technotes/2015-11-rebuilding-coreboot-image-generation.md') diff --git a/Documentation/technotes/2015-11-rebuilding-coreboot-image-generation.md b/Documentation/technotes/2015-11-rebuilding-coreboot-image-generation.md index d2a8fdcc0d..9accbfe65d 100644 --- a/Documentation/technotes/2015-11-rebuilding-coreboot-image-generation.md +++ b/Documentation/technotes/2015-11-rebuilding-coreboot-image-generation.md @@ -154,6 +154,7 @@ several data regions for its own purpose (similar to GBB, FWID, VPD, …). After the regions are filled, one data region must be post-processed to contain signatures to enable verifying other regions. +``` Chipset manifest ================ # A region called IFD, starting at 0, ending at 4K @@ -249,14 +250,15 @@ EC firmware manifest # overrides the cbfsdefault above group payload: ecrw.bin name=ecrw hash=sha256 group payload: pdrw.bin name=pdrw hash=sha256 +``` manifest parsing -================ +---------------- The exact BNF is work in progress. Some parser rules are * one line per statement -* # introduces a command until the end of line +* '#' introduces a command until the end of line Some processing rules * When there’s a conflict (eg. two statements on what to do to a region, -- cgit v1.2.3