From 269b537c00d547e854405eff4932da3139db8735 Mon Sep 17 00:00:00 2001 From: Tim Crawford Date: Tue, 20 Feb 2024 19:29:14 -0700 Subject: [PATCH] docs: Update note about coreboot config The whole coreboot generated `.config` has not been used since ff0a27ad9c60 ("Use defconfig to generate .config"). The required `coreboot.config` is much simpler now and can usually just be copied from another model. Signed-off-by: Tim Crawford --- docs/adding-a-new-board.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/adding-a-new-board.md b/docs/adding-a-new-board.md index 95ef98a..f2d0f3a 100644 --- a/docs/adding-a-new-board.md +++ b/docs/adding-a-new-board.md @@ -71,11 +71,10 @@ Other things that should be dumped before porting/flashing are: To port coreboot to a new board, see the coreboot documentation. -Once coreboot is ported, add its configuration. - -``` -cp coreboot/.config models//coreboot.config -``` +Add a `coreboot.config` file to the model directory. This can be copied from +another similar board as a reference, just updating the name. Typically, the +only special cases that need to be handled are when an FSP or microcode is +used that are not part of coreboot. ### Smart amp