chromeos: provide option to dynamically allocate ram oops buffer
Fixing the location of the ram oops buffer can lead to certain kernel and boot loaders being confused when there is a ram reservation low in the address space. Alternatively provide a mechanism to allocate the ram oops buffer in cbmem. As cbmem is usually high in the address space it avoids low reservation confusion. The patch uncondtionally provides a GOOG9999 ACPI device with a single memory resource describing the memory region used for the ramoops region. BUG=None BRANCH=baytrail,haswell TEST=Built and booted with and w/o dynamic ram oops. With the corresponding kernel change things behave correctly. Change-Id: Ide2bb4434768c9f9b90e125adae4324cb1d2d073 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/5257 Tested-by: build bot (Jenkins) Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
This commit is contained in:
committed by
Aaron Durbin
parent
e7e78d61a9
commit
06ece7de93
@ -62,6 +62,7 @@
|
||||
#define CBMEM_ID_REFCODE 0x04efc0de
|
||||
#define CBMEM_ID_REFCODE_CACHE 0x4efc0de5
|
||||
#define CBMEM_ID_SMM_SAVE_SPACE 0x07e9acee
|
||||
#define CBMEM_ID_RAM_OOPS 0x05430095
|
||||
#define CBMEM_ID_NONE 0x00000000
|
||||
#define CBMEM_ID_AGESA_RUNTIME 0x41474553
|
||||
#define CBMEM_ID_HOB_POINTER 0x484f4221
|
||||
|
Reference in New Issue
Block a user