All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] configs: move CONFIG_SPL_TEXT_BASE to Kconfig
Date: Wed, 14 Nov 2018 19:51:41 +0100	[thread overview]
Message-ID: <be26dd1a-bde9-6d02-5849-bed154b41978@gmail.com> (raw)
In-Reply-To: <20181007004921.GA1999@bill-the-cat>

On 07.10.2018 02:49, Tom Rini wrote:
> On Sun, Sep 30, 2018 at 02:31:53PM +0200, Simon Goldschmidt wrote:
>
>> Moved CONFIG_SPL_TEXT_BASE to common/spl/Kconfig with
>> help from moveconfig.py (only had to prepare socfpga,
>> stm32f746 and am33x/43x manually)
>>
>> Signed-off-by: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
>> ---
>>
>> This patch is in preparation for boot-from-FPGA for
>> socfpga cyclone5, where we need a different SPL_TEXT_BASE.
>> By moving this to Kconfig, this can then be done via
>> defconfig.
>>
>> I did notice that some defconfig files change more than
>> necessary, it seems like they are out of sync?
> So, I see at least one set of problems with the conversion, the am33*
> family gets put to 0x0 which isn't right.  I'm going to pull out the
> print tool I made and posted a while back and use that for conversion.
> Thanks for the starting point!

Tom, what's the status on this? I still can't build an SPL for socfpga 
gen5 boot from FPGA because I can't change SPL_TEXT_BASE.

Marek, if getting CONFIG_SPL_TEXT_BASE into 2019.01 won't work, can we 
have a separate (k)config option for socfpga only? That might be useful 
anyway as when booting from fpga, there is no 64 KByte size limit and 
the "magic value into magic register to unlock support for issuing warm 
reset" must not be written as the SPL is not in SRAM. But that might 
have its separate config option, too...

Anyway, I just need input to know in which direction I should continue. 
I'm waiting to get all our versions of SPL and U-Boot running from 
mainline (with only board configs added for our private boards).

Thanks,
Simon

Simon

  parent reply	other threads:[~2018-11-14 18:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-30 12:31 [U-Boot] [PATCH] configs: move CONFIG_SPL_TEXT_BASE to Kconfig Simon Goldschmidt
2018-10-07  0:49 ` [U-Boot] " Tom Rini
2018-10-07  6:37   ` Simon Goldschmidt
2018-11-14 18:51   ` Simon Goldschmidt [this message]
2019-01-02 20:13     ` Simon Goldschmidt
2019-01-07  9:12       ` Simon Goldschmidt
2019-01-18 22:02         ` Tom Rini
2019-01-19 16:52           ` Simon Goldschmidt
2019-01-19 16:57             ` Tom Rini
2019-02-14 18:28               ` Simon Goldschmidt
2019-02-18 15:07                 ` 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=be26dd1a-bde9-6d02-5849-bed154b41978@gmail.com \
    --to=simon.k.r.goldschmidt@gmail.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.