Files
system76-coreboot/src/vendorcode/google/chromeos/gnvs.h
Aaron Durbin 06ece7de93 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>
2014-03-11 21:37:36 +01:00

72 lines
2.2 KiB
C

/*
* This file is part of the coreboot project.
*
* Copyright (C) 2011 The ChromiumOS Authors. All rights reserved.
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; version 2 of the License.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/
#ifndef __VENDORCODE_GOOGLE_CHROMEOS_GNVS_H
#define __VENDORCODE_GOOGLE_CHROMEOS_GNVS_H
#define BOOT_REASON_OTHER 0
#define BOOT_REASON_S3DIAG 9
#define CHSW_RECOVERY_X86 (1 << 1)
#define CHSW_RECOVERY_EC (1 << 2)
#define CHSW_DEVELOPER_SWITCH (1 << 5)
#define CHSW_FIRMWARE_WP_DIS (1 << 9)
#define ACTIVE_MAINFW_RECOVERY 0
#define ACTIVE_MAINFW_RW_A 1
#define ACTIVE_MAINFW_RW_B 2
#define ACTIVE_MAINFW_TYPE_RECOVERY 0
#define ACTIVE_MAINFW_TYPE_NORMAL 1
#define ACTIVE_MAINFW_TYPE_DEVELOPER 2
#define RECOVERY_REASON_NONE 0
#define RECOVERY_REASON_ME 1
// TODO(reinauer) other recovery reasons?
#define ACTIVE_ECFW_RO 0
#define ACTIVE_ECFW_RW 1
typedef struct {
/* ChromeOS specific */
u32 vbt0; // 00 boot reason
u32 vbt1; // 04 active main firmware
u32 vbt2; // 08 active ec firmware
u16 vbt3; // 0c CHSW
u8 vbt4[256]; // 0e HWID
u8 vbt5[64]; // 10e FWID
u8 vbt6[64]; // 14e FRID - 275
u32 vbt7; // 18e active main firmware type
u32 vbt8; // 192 recovery reason
u32 vbt9; // 196 fmap base address
u8 vdat[3072]; // 19a
u32 vbt10; // d9a smbios bios version
u32 mehh[8]; // d9e management engine hash
u32 ramoops_base; // dbe ramoops base address
u32 ramoops_len; // dc2 ramoops length
u8 pad[314]; // dc6-eff
} __attribute__((packed)) chromeos_acpi_t;
extern chromeos_acpi_t *vboot_data;
void chromeos_init_vboot(chromeos_acpi_t *chromeos);
void chromeos_set_me_hash(u32*, int);
void acpi_get_vdat_info(uint64_t *vdat_addr, uint32_t *vdat_size);
#endif