From: Leo Liang <ycliang@andestech.com>
To: Zong Li <zong.li@sifive.com>
Cc: <u-boot@lists.denx.de>
Subject: Re: [PATCH 2/2] board: sifive: overwrite board_fdt_blob_setup in u-boot proper
Date: Mon, 2 Aug 2021 17:07:47 +0800 [thread overview]
Message-ID: <20210802090747.GE3588@andestech.com> (raw)
In-Reply-To: <20210727090659.7525-2-zong.li@sifive.com>
On Tue, Jul 27, 2021 at 05:06:59PM +0800, Zong Li wrote:
> Add board_fdt_blob_setup to return the device tree location which is
> passed by prior stage in u-boot proper. The generic board_fdt_blob_setup
> always returns _end, it mignt be ok because u-boot SPL would currently
> put the dtb there, but it would be broken if we put the dtb to another
> place and assigned the location into a1 register for u-boot proper. Use
> the location passed by prior stage would make more sence, because we
> actually pass the location to u-boot proper and want to use that one,
> rather than the dtb which in _end.
>
> We can't use CONFIG_OF_PRIOR_STAGE because it doens't distinguish the
> implementation of u-boot SPL and u-boot proper, so u-boot SPL need to
> reply on the prior stage to pass device tree location as well, but we
> don't pass the DT from boot rom now. In addition, when
> CONFIG_OF_PRIOR_STAGE is enabled, the u-boot-spl.bin and u-boot.itb won't
> include the device tree.
>
> Signed-off-by: Zong Li <zong.li@sifive.com>
> ---
> board/sifive/unleashed/unleashed.c | 11 +++++++++++
> board/sifive/unmatched/unmatched.c | 11 +++++++++++
> 2 files changed, 22 insertions(+)
Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>
next prev parent reply other threads:[~2021-08-02 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 9:06 [PATCH 1/2] board: sifive: compile stuff only related to SPL in SPL build Zong Li
2021-07-27 9:06 ` [PATCH 2/2] board: sifive: overwrite board_fdt_blob_setup in u-boot proper Zong Li
2021-08-02 9:07 ` Leo Liang [this message]
2021-08-02 8:54 ` [PATCH 1/2] board: sifive: compile stuff only related to SPL in SPL build Leo Liang
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=20210802090747.GE3588@andestech.com \
--to=ycliang@andestech.com \
--cc=u-boot@lists.denx.de \
--cc=zong.li@sifive.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox