summaryrefslogtreecommitdiff
path: root/configs/tec_defconfig
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2016-02-17 00:16:23 -0800
committerBin Meng <bmeng.cn@gmail.com>2016-02-21 13:42:52 +0800
commitdc5be508b065ff305cef451ac1aed7465603db02 (patch)
tree47bc097dafc2edd3815c5e8d955262c5b6e3e23d /configs/tec_defconfig
parent98af34f897a6ef5de253806049d033471b02479f (diff)
downloadu-boot-imx-dc5be508b065ff305cef451ac1aed7465603db02.zip
u-boot-imx-dc5be508b065ff305cef451ac1aed7465603db02.tar.gz
u-boot-imx-dc5be508b065ff305cef451ac1aed7465603db02.tar.bz2
x86: fsp: Make sure HOB list is not overwritten by U-Boot
Intel IvyBridge FSP seems to be buggy that it does not report memory used by FSP itself as reserved in the resource descriptor HOB. The FSP specification does not describe how resource descriptor HOBs are generated by the FSP to describe what memory regions. It looks newer FSPs like Queensbay and BayTrail do not have such issue. This causes U-Boot relocation overwrites the important boot service data which is used by FSP, and the subsequent call to fsp_notify() will fail. To resolve this, we find out the lowest memory base address allocated by FSP for the boot service data when walking through the HOB list in fsp_get_usable_lowmem_top(). Check whether the memory top address is below the FSP HOB list, and if not, use the lowest memory base address allocated by FSP as the memory top address. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Acked-by: Simon Glass <sjg@chromium.org> Tested on link (ivybridge non-FSP) Tested-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'configs/tec_defconfig')
0 files changed, 0 insertions, 0 deletions