diff options
author | Nick Vaccaro <nvaccaro@google.com> | 2020-03-10 00:23:40 -0700 |
---|---|---|
committer | Patrick Georgi <pgeorgi@google.com> | 2020-03-15 12:52:54 +0000 |
commit | aeaeeb7687d657a3f6d71a63ba717af2f14f3bad (patch) | |
tree | b298739a4088e818599ae207b3e5e805476d3cc0 /src/mainboard/google/hatch | |
parent | ee47fe42f57b47c5fa301966bbb709abc775f66c (diff) |
mb/google/volteer: Use generic SPD files
Volteer uses 4 bits (hardware straps) to indicate what memory
configuration the board is populated with (i.e. which SPD file
to use for the populated memory). This allows for only 16
different SPDs for supporting Volteer and all future variants of
Volteer. Currently, each memory chip needs its own SPD file, so we
can only support 16 different memory chip options for Volteer and
all of its variants.
Generic SPD files are just SPD files that have been stripped down
to contain only fields that are important for the memory controller
(strips out items like vendor info, for example). Using generic SPD
files allows for more than 16 different memory options given it's no
longer a 1-to-1 mapping as similar memory modules from different
vendors can share the same generic SPD file.
BUG=b:147857288
TEST="emerge-volteer coreboot chromeos-bootimage", flash ripto and
verify ripto boots to kernel and "cat /proc/meminfo" reports 8GB
of memory.
Change-Id: I17bd4f4a00b4e3bbaf845d6d321962c11569a186
Signed-off-by: Nick Vaccaro <nvaccaro@google.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/39423
Reviewed-by: Angel Pons <th3fanbus@gmail.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/mainboard/google/hatch')
0 files changed, 0 insertions, 0 deletions