summaryrefslogtreecommitdiff
path: root/src/mainboard/asrock/h81m-hds/bootblock.c
diff options
context:
space:
mode:
authorFurquan Shaikh <furquan@google.com>2021-03-13 12:35:20 -0800
committerPatrick Georgi <pgeorgi@google.com>2021-03-17 07:55:33 +0000
commiteb876a583049ca7765ab7c19e40bbbacaf17aa8e (patch)
treefe661741467793820f01365d71ca5e58d4db966c /src/mainboard/asrock/h81m-hds/bootblock.c
parenta94fea1ee444b8f1359729064cd72c963d36ad3f (diff)
vc/google/chromeos: Deprecate support for SAR tables in VPD
SAR table in VPD has been deprecated for Chrome OS platforms for > 1 year now. All new Chrome OS platforms have switched to using SAR tables from CBFS. This change drops the support for SAR table in VPD from coreboot to align with the factory changes. `get_wifi_sar_limits()` is thus updated to look for SAR file in CBFS only. Anyone building ToT coreboot for an already released Chrome OS platform with SAR table in VPD will have to extract the "wifi_sar" key from VPD and add it as a file to CBFS using following steps: - On DUT, read SAR value using `vpd -i RO_VPD -g wifi_sar` - In coreboot repo, generate CBFS SAR file using: `echo ${SAR_STRING} > site-local/${BOARD}-sar.hex` - Add to site-local/Kconfig: ``` config WIFI_SAR_CBFS_FILEPATH string default "site-local/${BOARD}-sar.hex" ``` BUG=b:173465272 Change-Id: I21d190dcc9f3554fab6e21b4498e7588a32bb1f0 Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/51483 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Patrick Georgi <pgeorgi@google.com> Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org>
Diffstat (limited to 'src/mainboard/asrock/h81m-hds/bootblock.c')
0 files changed, 0 insertions, 0 deletions