Duncan Laurie has uploaded this change for review. ( https://review.coreboot.org/c/coreboot/+/30755
Change subject: mb/google/sarien: Add PDR and RW_LEGACY_NVRAM to FMAP
......................................................................
mb/google/sarien: Add PDR and RW_LEGACY_NVRAM to FMAP
1) Add a Platform Data Region called SI_PDR which is allocated in the flash
descriptor for this platform
2) Add a DIAG_NVRAM region for use by the diagnostic payload for non-volatile
storage.
3) Encapsulate both RW_LEGACY and DIAG_NVRAM in a region called RW_DIAG
so it is clear they are associated.
4) Move the RW_DIAG region to the start of the RW region so that once we can
re-enable a larger BIOS region this sub-region will be in the uncached area
since it is not accessed on a normal boot.
BUG=b:119435206
TEST=tested on Arcada board to ensure expected regions are present
Change-Id: Ieb8bc4cf70d0a931e4944210112cfaf5c543f9f3
Signed-off-by: Duncan Laurie <dlaurie(a)google.com>
---
M src/mainboard/google/sarien/chromeos.fmd
1 file changed, 9 insertions(+), 6 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/55/30755/1
diff --git a/src/mainboard/google/sarien/chromeos.fmd b/src/mainboard/google/sarien/chromeos.fmd
index 6631769..ba42a6f 100644
--- a/src/mainboard/google/sarien/chromeos.fmd
+++ b/src/mainboard/google/sarien/chromeos.fmd
@@ -3,20 +3,25 @@
SI_DESC@0x0 0x1000
SI_EC@0x1000 0x100000
SI_GBE@0x101000 0x2000
- SI_ME@0x103000 0xefd000
+ SI_ME@0x103000 0xef9000
+ SI_PDR@0xffc000 0x4000
}
SI_BIOS@0x1000000 0x1000000 {
- RW_SECTION_A@0x0 0x280000 {
+ RW_DIAG@0x0 0x6d0000 {
+ DIAG_NVRAM@0x0 0x10000
+ RW_LEGACY(CBFS)@0x10000 0x6c0000
+ }
+ RW_SECTION_A@0x6d0000 0x280000 {
VBLOCK_A@0x0 0x10000
FW_MAIN_A(CBFS)@0x10000 0x26ffc0
RW_FWID_A@0x27ffc0 0x40
}
- RW_SECTION_B@0x280000 0x280000 {
+ RW_SECTION_B@0x950000 0x280000 {
VBLOCK_B@0x0 0x10000
FW_MAIN_B(CBFS)@0x10000 0x26ffc0
RW_FWID_B@0x27ffc0 0x40
}
- RW_MISC@0x500000 0x30000 {
+ RW_MISC@0xbd0000 0x30000 {
UNIFIED_MRC_CACHE@0x0 0x20000 {
RECOVERY_MRC_CACHE@0x0 0x10000
RW_MRC_CACHE@0x10000 0x10000
@@ -29,8 +34,6 @@
RW_VPD@0x28000 0x2000
RW_NVRAM@0x2a000 0x6000
}
- CONSOLE@0x530000 0x20000
- RW_LEGACY(CBFS)@0x550000 0x6b0000
WP_RO@0xc00000 0x400000 {
RO_VPD@0x0 0x4000
RO_UNUSED@0x4000 0xc000
--
To view, visit https://review.coreboot.org/c/coreboot/+/30755
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: Ieb8bc4cf70d0a931e4944210112cfaf5c543f9f3
Gerrit-Change-Number: 30755
Gerrit-PatchSet: 1
Gerrit-Owner: Duncan Laurie <dlaurie(a)chromium.org>
Gerrit-MessageType: newchange
Hello Mike Banon,
I'd like you to do a code review. Please visit
https://review.coreboot.org/c/coreboot/+/30748
to review the following change.
Change subject: cpu/Kconfig: hide CPU_MICROCODE_CBFS_GENERATE if no SUPPORT_CPU_UCODE_IN_CBFS
......................................................................
cpu/Kconfig: hide CPU_MICROCODE_CBFS_GENERATE if no SUPPORT_CPU_UCODE_IN_CBFS
Trying to use CPU_MICROCODE_CBFS_GENERATE microcode update option for a board
which does not support it - could lead to not-obvious problems. For example: if
someone tries to use this option e.g. for Lenovo G505S which does not belong to
CPU_AMD_MODEL_10XXX (f10h-f15h) group of the only AMD boards supporting it, then
CB will be built successfully but the microcode blob will occupy 0 size at CBFS,
which would result in worse outcome than if CPU_MICROCODE_CBFS_NONE is selected.
So CPU_MICROCODE_CBFS_GENERATE should be hidden for the not-supporting boards.
Signed-off-by: Mike Banon <mikebdp2(a)gmail.com>
Change-Id: I5e4654b14a0c14a25bd6aa62c71ed1d51a7aec03
---
M src/cpu/Kconfig
1 file changed, 1 insertion(+), 0 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/48/30748/1
diff --git a/src/cpu/Kconfig b/src/cpu/Kconfig
index a7cb99e..59c8e23 100644
--- a/src/cpu/Kconfig
+++ b/src/cpu/Kconfig
@@ -92,6 +92,7 @@
config CPU_MICROCODE_CBFS_GENERATE
bool "Generate from tree"
+ depends on SUPPORT_CPU_UCODE_IN_CBFS
help
Select this option if you want microcode updates to be assembled when
building coreboot and included in the final image as a separate CBFS
--
To view, visit https://review.coreboot.org/c/coreboot/+/30748
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I5e4654b14a0c14a25bd6aa62c71ed1d51a7aec03
Gerrit-Change-Number: 30748
Gerrit-PatchSet: 1
Gerrit-Owner: mikeb mikeb <mikebdp2(a)gmail.com>
Gerrit-Reviewer: Mike Banon <mikebdp2(a)gmail.com>
Gerrit-MessageType: newchange
Paul Menzel has uploaded this change for review. ( https://review.coreboot.org/c/coreboot/+/30745
Change subject: arch/x86/Kconfig: Fix spelling of *successful*
......................................................................
arch/x86/Kconfig: Fix spelling of *successful*
Change-Id: If0da91cf94aa12fe7b8670f6b181e443e3446aa1
Signed-off-by: Paul Menzel <pmenzel(a)molgen.mpg.de>
---
M src/arch/x86/Kconfig
1 file changed, 1 insertion(+), 1 deletion(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/45/30745/1
diff --git a/src/arch/x86/Kconfig b/src/arch/x86/Kconfig
index 794ea11..242a7cf 100644
--- a/src/arch/x86/Kconfig
+++ b/src/arch/x86/Kconfig
@@ -263,7 +263,7 @@
Do not clear the reboot count immediately after successful boot.
Set to allow the payload to control normal/fallback image recovery.
Note that it is the responsibility of the payload to reset the
- normal boot bit to 1 after each successsful boot.
+ normal boot bit to 1 after each successful boot.
config ACPI_CPU_STRING
string
--
To view, visit https://review.coreboot.org/c/coreboot/+/30745
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: If0da91cf94aa12fe7b8670f6b181e443e3446aa1
Gerrit-Change-Number: 30745
Gerrit-PatchSet: 1
Gerrit-Owner: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-MessageType: newchange