diff options
| author | Stefan Reinauer <reinauer@chromium.org> | 2015-03-16 16:47:39 -0700 |
|---|---|---|
| committer | Stefan Reinauer <stefan.reinauer@coreboot.org> | 2015-03-17 04:54:46 +0100 |
| commit | 45a225b05dbc22c5aff3c8baf927a68142f6be86 (patch) | |
| tree | 61aec713371f33e6c0145f4432a994474cbc4218 | |
| parent | 49168805112d021f8715cab3abded8ab384860ac (diff) | |
elog: Fix compilation with CONFIG_CHROMEOS enabled
On ChromeOS devices the ELOG section size and offset are
provided by the FMAP, rather than KConfig. Some upstream
refactoring broke compilation in that case.
Change-Id: I8b08daa327726218815855c7c2be45f44fcffeed
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/8700
Tested-by: build bot (Jenkins)
Reviewed-by: Aaron Durbin <adurbin@google.com>
| -rw-r--r-- | src/drivers/elog/elog.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/drivers/elog/elog.c b/src/drivers/elog/elog.c index 77019065ed..8bc8a0753a 100644 --- a/src/drivers/elog/elog.c +++ b/src/drivers/elog/elog.c @@ -37,7 +37,7 @@ #include <vendorcode/google/chromeos/fmap.h> -#if CONFIG_ELOG_FLASH_BASE == 0 +#if !IS_ENABLED(CONFIG_CHROMEOS) && CONFIG_ELOG_FLASH_BASE == 0 #error "CONFIG_ELOG_FLASH_BASE is invalid" #endif #if CONFIG_ELOG_FULL_THRESHOLD >= CONFIG_ELOG_AREA_SIZE |