summaryrefslogtreecommitdiff
path: root/src/vendorcode
diff options
context:
space:
mode:
authorRonak Kanabar <ronak.kanabar@intel.com>2024-06-06 11:21:22 +0530
committerSubrata Banik <subratabanik@google.com>2024-06-07 06:16:27 +0000
commitc9302d5d39267209f25a9d7de236cba344c65e7d (patch)
treeffae7db561be2b9d55e139cc5abd06f9a8596003 /src/vendorcode
parent491afc3cc778ba82154f405061922da5024357c5 (diff)
mb/aoostar/wtr_r1: Select FSP_TYPE_IOT
Currently, the 3rdparty/fsp submodule contains only the IoT FSP for ADL-N. However, coreboot's Kconfig is incorrectly applying the IoT FSP for both Client and IoT configurations, despite the Client FSP requiring distinct headers. The aoostar/wtr_r1 board relies on the FSP provided by the 3rdparty/fsp submodule, which means it has been using the IoT FSP by default. To ensure the board continues to use the correct FSP as we plan to introduce Client FSP headers into vendorcode, we are now explicitly select FSP_TYPE_IOT for the aoostar/wtr_r1 board. Change-Id: I68feeaaffd825013ae1012694047b067535e7341 Signed-off-by: Ronak Kanabar <ronak.kanabar@intel.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/82914 Reviewed-by: Nico Huber <nico.h@gmx.de> Reviewed-by: Subrata Banik <subratabanik@google.com> Reviewed-by: Angel Pons <th3fanbus@gmail.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/vendorcode')
0 files changed, 0 insertions, 0 deletions