summaryrefslogtreecommitdiffstats
path: root/3rdparty/fsp
diff options
context:
space:
mode:
authorNico Huber <nico.huber@secunet.com>2019-12-13 13:44:04 +0100
committerPatrick Georgi <pgeorgi@google.com>2019-12-16 09:41:57 +0000
commitbf15b2f7c3474c9811516d16f40a3533da5108c7 (patch)
tree3c973f5ae5b088c3718f167d20138edcd7afb5c4 /3rdparty/fsp
parentb86e96ab8cb190d0244fe442069fcef5e88ef68b (diff)
downloadcoreboot-bf15b2f7c3474c9811516d16f40a3533da5108c7.tar.gz
coreboot-bf15b2f7c3474c9811516d16f40a3533da5108c7.tar.bz2
coreboot-bf15b2f7c3474c9811516d16f40a3533da5108c7.zip
3rdparty/fsp: Update to current master again
We had to role the `fsp` submodule back for a minute due to a regression with the Coffee Lake binary. Intel silently mixed FSP 2.1 features into the Coffee Lake FSP which is supposed to be FSP 2.0. With the stack and heap usage partitioned for FSP using coreboot's stack (config FSP_USES_ CB_STACK), it works again. To make this even messier: We already selected this Kconfig option for Whiskey Lake, which is supposed to use the very same FSP binary. So with either submodule pointer, something was always broken :-/ Change-Id: Id2aa17aaa2c843dcc7e0fb28779d1e5948da83c9 Signed-off-by: Nico Huber <nico.huber@secunet.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/37700 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Jeremy Soller <jeremy@system76.com> Reviewed-by: Angel Pons <th3fanbus@gmail.com> Reviewed-by: Mimoja <coreboot@mimoja.de>
Diffstat (limited to '3rdparty/fsp')
m---------3rdparty/fsp0
1 files changed, 0 insertions, 0 deletions
diff --git a/3rdparty/fsp b/3rdparty/fsp
-Subproject 9e53d779eb34e944f9b3386ad6a9df80f710bdd
+Subproject 0bc2b07eab29a8a75cd084963c285ee5434e666