6ba82381f2
In some cases, we don't want the Chrome EC firmwares (both EC and PD)
built directly by the coreboot build system or included in images at
all. This is already supported with EC_EXTERNAL_FIRMWARE but it does
implement a binary (build and include) or (neither build nor include)
policy.
Some cases require the ability to separately control whether the EC
and PD firmwares should be built and included by the coreboot build
system, only included from externally-built images or not included
at all.
This introduces config changes implementing that behaviour, renaming
options to make it clear that they are specific to the Chrome EC.
BUG=none
BRANCH=none
TEST=none
CQ-DEPEND=CL:434278
Change-Id: Ie0b9e2063280a2b596a2d43afae855401319a959
Signed-off-by: Patrick Georgi <pgeorgi@chromium.org>
Original-Commit-Id:
|
||
|---|---|---|
| .. | ||
| acpi | ||
| compal/ene932 | ||
| google/chromeec | ||
| kontron/it8516e | ||
| lenovo | ||
| purism/librem | ||
| quanta | ||
| roda/it8518 | ||
| smsc/mec1308 | ||
| ec.h | ||