From 5f780ee2ecb6324d481db2fb717558f4e48e4df9 Mon Sep 17 00:00:00 2001 From: Tim Crawford Date: Tue, 4 Aug 2020 21:49:14 -0600 Subject: [PATCH] docs: Update notes for adding a new board - Update note about microcode.rom - Remove note about different model names for firmware-open and EC --- docs/adding-a-new-board.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/adding-a-new-board.md b/docs/adding-a-new-board.md index 1ff0e7f..155458d 100644 --- a/docs/adding-a-new-board.md +++ b/docs/adding-a-new-board.md @@ -42,8 +42,9 @@ If planning to use System76 EC firmware, perform the following before running: ./scripts/generate.sh [ec.rom] ``` -You will additionally need to generate the correct `microcode.rom` for the CPU -family from the private [intel-microcode] repo. +If the microcode blobs from coreboot will not be used, then `microcode.rom` +must be generated for the correct CPU set from the private [intel-microcode] +repo. ## Porting coreboot @@ -65,9 +66,6 @@ Once System76 EC is ported, add `ec.config`. echo "BOARD=system76/" > models//ec.config" ``` -The model name used for the EC may be different from the name used for -firmware-open (e.g., `galp3-c` used for `galp4`). - If the proprietary EC was previously used, remove `ec.rom` and regenerate the READMEs.