volteer: bypass mosys memory tables
Some memory parts used on volteer show an incorrect device width when
mosys memory is queried via "mosys memory spd print all". This is
because the embedded table of memory parts in mosys makes assumptions
about device_width, and in volteer's case, shows some parts as being
twice as big as they actually are due to assuming device_width of 32
instead of the actual device width of 16. To get around this issue, we
instruct volteer to search the smbios tables ONLY, and not look at
the embedded mosys memory part tables when getting memory information.
BUG=b:160894734, b:164716202
TEST="emerge-volteer mosys", copy to volteer SKU4 with K4UBE3D4AA-MGCL
memory parts, execute "mosys memory spd print geometry" and verify
that device width is 16 and total size is 16GB:
localhost ~ # mosys memory spd print id
0 | 1-0 | K4UBE3D4AA-MGCL
1 | 1-0 | K4UBE3D4AA-MGCL
2 | 1-0 | K4UBE3D4AA-MGCL
3 | 1-0 | K4UBE3D4AA-MGCL
4 | 1-0 | K4UBE3D4AA-MGCL
5 | 1-0 | K4UBE3D4AA-MGCL
6 | 1-0 | K4UBE3D4AA-MGCL
7 | 1-0 | K4UBE3D4AA-MGCL
localhost ~ # mosys memory spd print geometry
0 | 2048 | 2 | 16
1 | 2048 | 2 | 16
2 | 2048 | 2 | 16
3 | 2048 | 2 | 16
4 | 2048 | 2 | 16
5 | 2048 | 2 | 16
6 | 2048 | 2 | 16
7 | 2048 | 2 | 16
Change-Id: If7e5c56edf07fd9b591f9aec4d234f2b4879d3c8
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/mosys/+/2412774
Tested-by: Nick Vaccaro <nvaccaro@google.com>
Commit-Queue: caveh jalali <caveh@chromium.org>
Reviewed-by: caveh jalali <caveh@chromium.org>
Reviewed-by: Jack Rosenthal <jrosenth@chromium.org>
1 file changed
