From: Yao Zi <me@ziyao.cc>
To: Christopher Obbard <christopher.obbard@linaro.org>,
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: Sat, 10 Jan 2026 09:04:23 +0000 [thread overview]
Message-ID: <aWIWF_sZ5Epf5zYN@pie> (raw)
In-Reply-To: <879112a0bf19df9d79bee3dc33557bf382e0d839.camel@linaro.org>
On Sat, Jan 10, 2026 at 03:20:39AM +0000, Christopher Obbard wrote:
> Hi Fabio,
>
> On Thu, 2025-12-18 at 23:45 -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:
> >
> > 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?
> >
>
> Great to see the RV1103 being upstreamed!
>
>
> I have a Rockchip RV1106 based board, the CoolPi 1B https://www.cool-pi.com/product-category/gateway/cp1b/ which I'd also like to get in upstream linux/u-boot.
>
> The downstream kernel/devicetree is at https://github.com/coolpi-george/coolpi-kernel/blob/linux-5.10-gen-rkr8/arch/arm/boot/dts/rv1106-cp1b.dts with defconfig
> https://github.com/coolpi-george/coolpi-kernel/blob/linux-5.10-gen-rkr8/arch/arm/configs/rv1106_cp1b_defconfig
>
> The downstream u-boot is https://github.com/coolpi-george/coolpi-loader/blob/develop/configs/rv1106_coolpicp1b_defconfig
>
> I wonder how similar the RV1106 SoC is to the RV1103 you're working on ?
Given that the devicetree for RV1103 in Rockchip downstream kernel tree
includes RV1106's devicetree[1] and only adds some overrides, I'd like
to say RV1103 is basically only in a different package. They're likely
the same silicon, probably with different qualities.
> I only ask since the RV1106 SoC has a similar prefix to the RV1103. I don't have any other information about the SoC.
>
>
> Cheers!
>
> Chris
Regards,
Yao Zi
[1]: https://github.com/rockchip-linux/kernel/blob/1ba51b059f25533c5529b7f68186190b47d6a7b3/arch/arm/boot/dts/rockchip/rv1103.dtsi#L6
prev parent reply other threads:[~2026-01-10 9:05 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
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 [this message]
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=aWIWF_sZ5Epf5zYN@pie \
--to=me@ziyao.cc \
--cc=christopher.obbard@linaro.org \
--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