coreboot-kgpe-d16/util/mainboard/google
Paul Fagerburg 259cccd7e7 mb/google: order matters in mem_parts_used.txt
* Add comments to mem_parts_used.txt to point out that the order of
the entries matters when assigning IDs, so always add a new part
to the end of the file.
* Update existing mem_parts_used.txt to add the same comment.
* No updates to Zork variants, because they use an optional ID, so
the order actually doesn't matter there.

BUG=b:175898902
TEST=create a new variant of dalboz, trembyle, volteer, waddledee,
or waddledoo, and observe that mem_parts_used.txt has the new
verbiage.

Signed-off-by: Paul Fagerburg <pfagerburg@google.com>
Change-Id: Iffbd8e69a89b1b7c810c5d25c7a6148d459d8b02
Reviewed-on: https://review.coreboot.org/c/coreboot/+/50449
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Martin Roth <martinroth@google.com>
Reviewed-by: Rob Barnes <robbarnes@google.com>
2021-02-10 22:15:52 +00:00
..
dalboz/template mb/google: order matters in mem_parts_used.txt 2021-02-10 22:15:52 +00:00
hatch/template templates: add an empty SPD to SPD_SOURCES 2020-10-06 18:27:31 +00:00
puff/template
trembyle/template mb/google: order matters in mem_parts_used.txt 2021-02-10 22:15:52 +00:00
volteer/template mb/google: order matters in mem_parts_used.txt 2021-02-10 22:15:52 +00:00
waddledee/template mb/google: order matters in mem_parts_used.txt 2021-02-10 22:15:52 +00:00
waddledoo/template mb/google: order matters in mem_parts_used.txt 2021-02-10 22:15:52 +00:00