public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Yao Zi <me@ziyao.cc>
To: Fabio Estevam <festevam@gmail.com>,
	Kever Yang <kever.yang@rock-chips.com>
Cc: Quentin Schulz <quentin.schulz@cherry.de>,
	Jonas Karlman <jonas@kwiboo.se>,
	U-Boot-Denx <u-boot@lists.denx.de>, Tom Rini <trini@konsulko.com>,
	xuhui.lin@rock-chips.com
Subject: Re: RV1103B: Attempt to upstream
Date: Fri, 19 Dec 2025 03:23:02 +0000	[thread overview]
Message-ID: <aUTFFpDswwsVYdI0@pie> (raw)
In-Reply-To: <CAOMZO5B0HmoyCtHHuOFjTq8n1HRoHxZ0-c-mJ_2e6JoT2heSBA@mail.gmail.com>

On Thu, Dec 18, 2025 at 11:45:11PM -0300, Fabio Estevam wrote:
> Hi,
> 
> I have a custom board based on the Rockchip evb-rv1103 (RV1103B silicon),
> booting from SPI-NAND.
> 
> I can successfully boot the vendor Rockchip U-Boot v2017.09 on this board,
> from SPI-NAND
> 
> I am currently working on upstreaming U-Boot support for the RV1103B SoC.
> My first RFC attempt is available here:

I think the upstreaming process should start from the kernel side,
then we will have stable devicetree ABI reference to work with, instead
of creating everything from scratch in U-Boot.

This will also makes it easier to enable OF_UPSTREAM.

>   https://github.com/fabioestevam/u-boot/commits/rv1103/
> 
> Build steps:
> 
>   make evb-rv1103_defconfig
>   make
> 
> However, I am not yet able to boot U-Boot on the board. At the moment,
> the board does not boot and only prints "RKUART".
> 
> My initial plan was to avoid SPL, similar to the evb-rv1108 approach
> (described in board/rockchip/evb_rv1108/README).
> 
> Before going further, I would like to ask:
> 
> Is the evb-rv1108 “no SPL” boot flow a valid reference for RV1103B?
> 
> Any guidance or pointers would be greatly appreciated.
> 
> Thanks,
> 
> Fabio Estevam

Best regards,
Yao Zi

  reply	other threads:[~2025-12-19  3:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19  2:45 RV1103B: Attempt to upstream Fabio Estevam
2025-12-19  3:23 ` Yao Zi [this message]
2025-12-19 17:47   ` Fabio Estevam
2026-01-08 16:33 ` Quentin Schulz
2026-01-10  2:17   ` Fabio Estevam
2026-01-08 16:37 ` Quentin Schulz
2026-01-10  3:20 ` Christopher Obbard
2026-01-10  9:04   ` Yao Zi

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=aUTFFpDswwsVYdI0@pie \
    --to=me@ziyao.cc \
    --cc=festevam@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=kever.yang@rock-chips.com \
    --cc=quentin.schulz@cherry.de \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xuhui.lin@rock-chips.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