From: Hiago De Franco <hfranco@baylibre.com>
To: Yao Zi <me@ziyao.cc>
Cc: Leo Yu-Chi Liang <leo.liang@sifive.com>,
u-boot@lists.u-boot-project.org, Tom Rini <trini@konsulko.com>,
Tim Ouyang <tim609@andestech.com>,
Zhuxu Ran <zhuxu_ran@zohomail.com>,
Kongyang Liu <seashell11234455@gmail.com>
Subject: Re: [PATCH 0/2] riscv: cv1800b: Milk-V Duo boot fixes
Date: Fri, 9 Oct 2026 11:31:21 -0300 [thread overview]
Message-ID: <asj6OaDxcTTEUvm6@hiagonb> (raw)
In-Reply-To: <asa-S7LCji4uX4af@pie>
Hello,
On Wed, Oct 07, 2026 at 09:48:59PM +0000, Yao Zi wrote:
> On Wed, Sep 30, 2026 at 09:17:48AM -0300, Hiago De Franco wrote:
> > This series fixes two problems on the Sophgo CV1800B/SG2002 Milk-V Duo
> > boards.
> >
> > Patch 1 fixes the fdtfile environment variable of the Milk-V Duo 256M.
> > CONFIG_DEFAULT_DEVICE_TREE is a quoted string, so the quotes ended up
> > in the environment.
> >
> > Patch 2 keeps U-Boot out of the memory reserved for the coprocessor
> > firmware. The upstream devicetrees reserve the end of DRAM as a no-map
> > region, but U-Boot relocates to ram_top, which is the end of DRAM, so
> > it lands inside that region.
>
> I think the issue solved by PATCH 2 is introduced during switching to
> upstream devicetree? Could you please cooperate with Zhuxu so nothing
> is broken at the first place? Thanks.
Thanks for the review, you are right. The issue only shows up once the
boards switch to the upstream devicetrees from Zhuxu's series, and
Andrei's patches that drop the coprocessor reserved-memory nodes are
already in the Sophgo tree for linux-next:
6645398c4621 ("riscv: dts: sophgo: cv1800b-milkv-duo: drop reserved memory node")
60e4cafd3090 ("riscv: dts: sophgo: sg2002-milkv-duo256m: drop reserved memory node")
I tested Zhuxu's v5 plus these two commits applied to dts/upstream,
without my patch 2, on both Milk-V Duo 64M and 256M. The reserved memory
error is gone and U-Boot relocates to the top of DRAM as before:
Duo 64M: relocaddr = 0x83f79000
Duo 256M: relocaddr = 0x8ff6e000
So I will drop patch 2 and send a v2 with only the fdtfile fix.
Zhuxu (Cc'd), to avoid breaking these boards in between, could you carry
those two devicetree changes in your series, or should we wait for the
next dts/upstream sync that includes them before your series is merged?
>
> Regards,
> Yao Zi
>
> > This was tested on both Milk-V Duo 64M and 256M (CV1800B and SG2002).
> >
> > Signed-off-by: Hiago De Franco <hfranco@baylibre.com>
> > ---
> > Hiago De Franco (2):
> > board: sophgo: milkv_duo_256m: fix fdtfile quoting
> > riscv: cpu: cv1800b: keep U-Boot out of reserved memory
Best regards,
--
Hiago
next prev parent reply other threads:[~2026-10-09 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 12:17 [PATCH 0/2] riscv: cv1800b: Milk-V Duo boot fixes Hiago De Franco
2026-09-30 12:17 ` [PATCH 1/2] board: sophgo: milkv_duo_256m: fix fdtfile quoting Hiago De Franco
2026-09-30 12:17 ` [PATCH 2/2] riscv: cpu: cv1800b: keep U-Boot out of reserved memory Hiago De Franco
2026-10-07 21:46 ` Yao Zi
2026-10-07 21:48 ` [PATCH 0/2] riscv: cv1800b: Milk-V Duo boot fixes Yao Zi
2026-10-09 14:31 ` Hiago De Franco [this message]
2026-10-11 7:23 ` Zhuxu Ran
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=asj6OaDxcTTEUvm6@hiagonb \
--to=hfranco@baylibre.com \
--cc=leo.liang@sifive.com \
--cc=me@ziyao.cc \
--cc=seashell11234455@gmail.com \
--cc=tim609@andestech.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.org \
--cc=zhuxu_ran@zohomail.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 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.