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>
This commit is contained in:
committed by
Stefan Reinauer
parent
4916880511
commit
45a225b05d
@ -37,7 +37,7 @@
|
|||||||
|
|
||||||
#include <vendorcode/google/chromeos/fmap.h>
|
#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"
|
#error "CONFIG_ELOG_FLASH_BASE is invalid"
|
||||||
#endif
|
#endif
|
||||||
#if CONFIG_ELOG_FULL_THRESHOLD >= CONFIG_ELOG_AREA_SIZE
|
#if CONFIG_ELOG_FULL_THRESHOLD >= CONFIG_ELOG_AREA_SIZE
|
||||||
|
Reference in New Issue
Block a user