On Wed, Jul 30, 2025 at 01:28:06PM +0800, Kevin Lo wrote:
> Ping.
>
> Below are the U-Boot and boot messages on Rock 3A.
I don't have this kind of board so I can't really comment on the
update itself. But something caught my eye,
<snip>
> > Index:
> > sysutils/u-boot/rk356x/patches/patch-dts_upstream_src_arm64_rockchip_rk3566-anbernic-rgxx3_dtsi
> > ===================================================================
> > RCS file:
> > sysutils/u-boot/rk356x/patches/patch-dts_upstream_src_arm64_rockchip_rk3566-anbernic-rgxx3_dtsi
> > diff -N
> > sysutils/u-boot/rk356x/patches/patch-dts_upstream_src_arm64_rockchip_rk3566-anbernic-rgxx3_dtsi
> > --- /dev/null 1 Jan 1970 00:00:00 -0000
> > +++
> > sysutils/u-boot/rk356x/patches/patch-dts_upstream_src_arm64_rockchip_rk3566-anbernic-rgxx3_dtsi
> > 21 Jul 2025 06:02:12 -0000
> > @@ -0,0 +1,12 @@
> > +Index: dts/upstream/src/arm64/rockchip/rk3566-anbernic-rgxx3.dtsi
> > +--- dts/upstream/src/arm64/rockchip/rk3566-anbernic-rgxx3.dtsi.orig
> > ++++ dts/upstream/src/arm64/rockchip/rk3566-anbernic-rgxx3.dtsi
> > +@@ -13,7 +13,7 @@
> > + chassis-type = "handset";
> > +
> > + chosen: chosen {
> > +- stdout-path = "serial2:1500000n8";
> > ++ stdout-path = "serial2:115200n8";
Out of curiosity, is there a particular reason why you're forcing
115200 instead of upstream's default? Is 150000 not functional?
--
jca
