U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yao Zi <me@ziyao.cc>
To: Hiago De Franco <hfranco@baylibre.com>,
	u-boot@lists.u-boot-project.org, Yao Zi <me@ziyao.cc>
Cc: Kongyang Liu <seashell11234455@gmail.com>,
	Tom Rini <trini@konsulko.com>, Zhuxu Ran <zhuxu_ran@zohomail.com>,
	Tim Ouyang <tim609@andestech.com>,
	Leo Liang <leo.liang@sifive.com>
Subject: Re: [PATCH v2 0/3] board: sophgo: milkv_duo: enable standard boot
Date: Mon, 19 Oct 2026 08:08:00 +0000	[thread overview]
Message-ID: <atXP4EoaPk6ydwCa@pie> (raw)
In-Reply-To: <atPXMIVNYWOKWJPm@hiagonb>

On Sat, Oct 17, 2026 at 05:17:11PM -0300, Hiago De Franco wrote:
> Hi Yao Zi,
> 
> On Fri, Oct 09, 2026 at 11:58:21AM -0300, Hiago De Franco wrote:
> > The Milk-V Duo (CV1800B, 64MB) does not enable CONFIG_BOOTSTD_DEFAULTS
> > and has no environment file, so U-Boot has no bootcmd and none of the
> > kernel_addr_r, fdt_addr_r, ramdisk_addr_r, ... variables required by
> > the extlinux bootmeth.
> > 
> > Enable CONFIG_BOOTSTD_DEFAULTS and add a milkv_duo.env with a memory
> > layout that fits into the 64MB of DRAM:
> > 
> >   0x80200000  kernel_addr_r       (16MB)
> >   0x81200000  kernel_comp_addr_r  (16MB, Image.gz decompression)
> >   0x82200000  fdt_addr_r
> >   0x82300000  scriptaddr
> >   0x82400000  pxefile_addr_r
> >   0x82500000  ramdisk_addr_r
> > 
> > Also reduce CONFIG_STACK_SIZE to 1MB. LMB reserves CONFIG_STACK_SIZE
> > below the relocated stack pointer, and the default 16MB left only about
> > 1.4MB between ramdisk_addr_r and the reserved region. With 1MB, about
> > 16MB are available for an initrd.
> > 
> > This series depends on Zhuxu Ran's "riscv: sophgo: Use upstream
> > devicetrees for CV18xx boards" (v5), which sets CONFIG_DEFAULT_DEVICE_TREE
> > to sophgo/<board>, so that fdtfile matches the Linux devicetree install
> > path (sophgo/cv1800b-milkv-duo.dtb and sophgo/sg2002-milkv-duo256m.dtb).
> > 
> > Link: https://lore.kernel.org/all/20260927-milkv-duo-upstream-dts-v5-0-7f64983e59e1@zohomail.com/
> > 
> > Tested on Milk-V Duo, booting Linux through "bootflow scan" and an
> > extlinux.conf on the SD card.
> > 
> > Signed-off-by: Hiago De Franco <hfranco@baylibre.com>
> 
> just a ping about this patch, I do not know if it was picked
> yet or If I should wait and rebase on v2027.01-rc1. Can you help please?

I'm only reviewer of the RISC-V architecture, and don't help with picking
patches etc :)

And I think the series (Zhuxu's one) on which it depends hasn't been merged
yet?

Best regards,
Yao Zi

  reply	other threads:[~2026-10-19  8:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 14:58 [PATCH v2 0/3] board: sophgo: milkv_duo: enable standard boot Hiago De Franco
2026-10-09 14:58 ` [PATCH v2 1/3] board: sophgo: milkv_duo: add environment for " Hiago De Franco
2026-10-09 14:58 ` [PATCH v2 2/3] configs: milkv_duo: enable BOOTSTD_DEFAULTS Hiago De Franco
2026-10-09 14:58 ` [PATCH v2 3/3] configs: milkv_duo: reduce CONFIG_STACK_SIZE to 1MB Hiago De Franco
2026-10-17 20:17 ` [PATCH v2 0/3] board: sophgo: milkv_duo: enable standard boot Hiago De Franco
2026-10-19  8:08   ` Yao Zi [this message]
2026-10-20 16:58     ` Hiago De Franco

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=atXP4EoaPk6ydwCa@pie \
    --to=me@ziyao.cc \
    --cc=hfranco@baylibre.com \
    --cc=leo.liang@sifive.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox