Message ID | BLU436-SMTP44B11B66DB4B7249DE9C0FBFB60@phx.gbl |
---|---|
State | Accepted |
Delegated to: | Simon Glass |
Headers | show |
On 1 June 2015 at 07:07, Bin Meng <bmeng.cn@gmail.com> wrote: > FSP_TEMP_RAM_ADDR should only be visible when HAVE_FSP is on. > > Signed-off-by: Bin Meng <bmeng.cn@gmail.com> > --- > > arch/x86/Kconfig | 1 + > 1 file changed, 1 insertion(+) Acked-by: Simon Glass <sjg@chromium.org>
On 4 June 2015 at 02:47, Simon Glass <sjg@chromium.org> wrote: > On 1 June 2015 at 07:07, Bin Meng <bmeng.cn@gmail.com> wrote: >> FSP_TEMP_RAM_ADDR should only be visible when HAVE_FSP is on. >> >> Signed-off-by: Bin Meng <bmeng.cn@gmail.com> >> --- >> >> arch/x86/Kconfig | 1 + >> 1 file changed, 1 insertion(+) > > Acked-by: Simon Glass <sjg@chromium.org> Applied to u-boot-x86, thanks!
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index ac1dc65..3506ba2 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -220,6 +220,7 @@ config FSP_ADDR config FSP_TEMP_RAM_ADDR hex + depends on HAVE_FSP default 0x2000000 help Stack top address which is used in FspInit after DRAM is ready and
FSP_TEMP_RAM_ADDR should only be visible when HAVE_FSP is on. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> --- arch/x86/Kconfig | 1 + 1 file changed, 1 insertion(+)