arch/x86: initialize EBDA in S3 and S0/S5 path
It's more consistent to re-initialize EBDA in all boot paths. That way, the data living in EBDA is cleared prior to be accessed (assuming it's after setup_ebda()). Change-Id: I05ff84f869f7b6a463e52b4cb954acc5566475cd Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://review.coreboot.org/21997 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Subrata Banik <subrata.banik@intel.com>
This commit is contained in:
parent
c714137d95
commit
c06a3f72f8
|
@ -18,7 +18,6 @@
|
|||
#include <string.h>
|
||||
#include <arch/io.h>
|
||||
#include <arch/ebda.h>
|
||||
#include <arch/acpi.h>
|
||||
#include <commonlib/endian.h>
|
||||
#include <console/console.h>
|
||||
|
||||
|
@ -84,10 +83,6 @@ void setup_ebda(u32 low_memory_size, u16 ebda_segment, u16 ebda_size)
|
|||
u16 ebda_kb;
|
||||
void *ebda;
|
||||
|
||||
/* Skip in S3 resume path */
|
||||
if (acpi_is_wakeup_s3())
|
||||
return;
|
||||
|
||||
if (!low_memory_size || !ebda_segment || !ebda_size)
|
||||
return;
|
||||
|
||||
|
|
Loading…
Reference in New Issue