| commit | c06a3f72f82f46eb2b56c7b84a605001f7c38049 | [log] [tgz] |
|---|---|---|
| author | Aaron Durbin <adurbin@chromium.org> | Thu Oct 12 11:32:20 2017 -0600 |
| committer | Aaron Durbin <adurbin@chromium.org> | Mon Oct 16 16:56:19 2017 +0000 |
| tree | 3f1b76e5fbed82981ae847a6a97531b4e61922a7 | |
| parent | c714137d9519c12d2b951abf3c335fb1d6912029 [diff] |
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>