All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v2 11/11] spl: Kconfig: Add CONFIG_SPL_TEXT_BASE as Kconfig option
Date: Tue, 23 Aug 2016 09:57:34 -0500	[thread overview]
Message-ID: <09109096-c66d-6c7c-a0e4-35da4977289a@ti.com> (raw)
In-Reply-To: <CAK7LNASPzoCQO9MLBB+hYPajjYW=xCEO0L=E-KX4+yeaWgKFwg@mail.gmail.com>

On 08/23/2016 12:45 AM, Masahiro Yamada wrote:
> 2016-08-23 0:21 GMT+09:00 Andrew F. Davis <afd@ti.com>:
>> Add a new Kconfig CONFIG_SPL_TEXT_BASE. Set its default value to 0x0.
>>
>> Signed-off-by: Andrew F. Davis <afd@ti.com>
>> ---
>>  Kconfig | 8 ++++++++
>>  1 file changed, 8 insertions(+)
>>
>> diff --git a/Kconfig b/Kconfig
>> index cb5af5b..2935c41 100644
>> --- a/Kconfig
>> +++ b/Kconfig
>> @@ -319,6 +319,14 @@ config SYS_TEXT_BASE
>>         help
>>           TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
>>
>> +config SPL_TEXT_BASE
>> +       hex "SPL Text Base"
>> +       depends on SPL
>> +       default 0x0
>> +       help
>> +         When SPL is enabled the image is linked with this as the
>> +         starting address in memeory for which the SPL will be loaded.
>> +
>>  config SPL_LOAD_FIT
>>         bool "Enable SPL loading U-Boot as a FIT"
>>         depends on FIT
> 
> 
> 
> For example, my SoC, configs/uniphier_ld20_defconfig,
> needs to set CONFIG_SPL_TEXT_BASE to 0x100000
> because its Boot ROM loads SPL onto 0x100000.
> 
> It is not user-configurable at all, so I do not see much sense for the prompt.
> I am not quite sure for other SoCs, but I guess similar situation.
> 
> (If we support relocation for SPL, we can make SPL_TEXT_BASE
> a configurable parameter, but we do not have it at this point of time.)
> 
> 
> Is it better to hide the prompt unless EXPERT is defined?
> 
> config SPL_TEXT_BASE
>        hex "SPL Text Base" if EXPERT
> 
> 

I would be okay with this, I only really need this as a Kconfig option
so I can easily set it on a per defconfig basis
(am335x_evm_{boot_type}_defconfig), as you stated this isn't really for
users to change and so should be hidden by default.

Andrew

  reply	other threads:[~2016-08-23 14:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22 15:21 [U-Boot] [PATCH v2 00/11] Allow secure boot on AM33xx devices Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [PATCH v2 01/11] Kconfig: Separate AM33XX SOC config from target board config Andrew F. Davis
2016-08-26 20:12   ` Tom Rini
2016-08-22 15:21 ` [U-Boot] [PATCH v2 02/11] am33xx: config.mk: Add support for additional secure boot image types Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [PATCH v2 03/11] am33xx: config.mk: Fix option used to enable SPI SPL image type Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [PATCH v2 04/11] doc: Update info on using AM33xx secure devices from TI Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [PATCH v2 05/11] ti: omap-common: Allow AM33xx devices to be built securely Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [PATCH v2 06/11] board: am33xx-hs: spl: Allow post-processing of FIT image on AM33xx Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 07/11] omap: Use SD_BOOT in place of EMMC_BOOT Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 08/11] config: Remove usage of CONFIG_STORAGE_EMMC Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 09/11] spl: Kconfig: Add SPL_<media>_SUPPORT as Kconfig option Andrew F. Davis
2016-08-23  6:08   ` Masahiro Yamada
2016-08-23 15:02     ` Andrew F. Davis
2016-08-26 20:06     ` Tom Rini
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 10/11] spl: Kconfig: Add SPL_<media>_BOOT " Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 11/11] spl: Kconfig: Add CONFIG_SPL_TEXT_BASE " Andrew F. Davis
2016-08-23  5:45   ` Masahiro Yamada
2016-08-23 14:57     ` Andrew F. Davis [this message]
2016-08-26 17:59       ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=09109096-c66d-6c7c-a0e4-35da4977289a@ti.com \
    --to=afd@ti.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.