skylake: fix invalid GNVS base address
Leaving a sentinel 0xC0DEBABE and fixing it up is is the old way of setting the correct base address for GNVS. One just needs to reference NVSA which is already filled in by the skylake ACPI code. BUG=chrome-os-partner:43611 BUG=chrome-os-partner:43522 BRANCH=None TEST=Built and booted glados. /sys/firmware/log shows up as well as ramoops using the correct address. Original-Change-Id: I1d4979b1bb65faa76316a4ec4c551a7b9b9eed32 Original-Signed-off-by: Aaron Durbin <adurbin@chromium.org> Original-Reviewed-on: https://chromium-review.googlesource.com/290338 Original-Reviewed-by: Duncan Laurie <dlaurie@chromium.org> Change-Id: I25efea73a383215f9365ce91230f79516b0201a6 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/11185 Tested-by: build bot (Jenkins) Reviewed-by: Patrick Georgi <pgeorgi@google.com>
This commit is contained in:
parent
3b6c398bf4
commit
04a066661d
|
@ -30,7 +30,8 @@ Name (\PICM, 0) // IOAPIC/8259
|
||||||
* we have to fix it up in coreboot's ACPI creation phase.
|
* we have to fix it up in coreboot's ACPI creation phase.
|
||||||
*/
|
*/
|
||||||
|
|
||||||
OperationRegion (GNVS, SystemMemory, 0xC0DEBABE, 0x2000)
|
External(NVSA)
|
||||||
|
OperationRegion (GNVS, SystemMemory, NVSA, 0x2000)
|
||||||
Field (GNVS, ByteAcc, NoLock, Preserve)
|
Field (GNVS, ByteAcc, NoLock, Preserve)
|
||||||
{
|
{
|
||||||
/* Miscellaneous */
|
/* Miscellaneous */
|
||||||
|
|
Loading…
Reference in New Issue