ACPI: Declare GNVS variables globally
There is a common place where acpigen generates these, so the declarations for the OperationRegions should be centralized too. Change-Id: I772492ca9e651b60244c565d1e926dc2ad33cfd8 Signed-off-by: Kyösti Mälkki <kyosti.malkki@gmail.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/49795 Reviewed-by: Raul Rangel <rrangel@chromium.org> Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
This commit is contained in:
@@ -1,8 +1,5 @@
|
||||
/* SPDX-License-Identifier: GPL-2.0-only */
|
||||
|
||||
External (NVSD)
|
||||
|
||||
OperationRegion (DNVS, SystemMemory, NVSD, 0x1000)
|
||||
Field (DNVS, ByteAcc, NoLock, Preserve)
|
||||
{
|
||||
/* Device Enabled in ACPI Mode */
|
||||
|
@@ -4,16 +4,6 @@
|
||||
|
||||
Name(\PICM, 0) /* IOAPIC/8259 */
|
||||
|
||||
/*
|
||||
* Global ACPI memory region. This region is used for passing information
|
||||
* between coreboot (aka "the system bios"), ACPI, and the SMI handler.
|
||||
* Since we don't know where this will end up in memory at ACPI compile time,
|
||||
* we have to fix it up in coreboot's ACPI creation phase.
|
||||
*/
|
||||
|
||||
External (NVSA)
|
||||
|
||||
OperationRegion (GNVS, SystemMemory, NVSA, 0x1000)
|
||||
Field (GNVS, ByteAcc, NoLock, Preserve)
|
||||
{
|
||||
/* Miscellaneous */
|
||||
|
Reference in New Issue
Block a user