From: Yao Zi <me@ziyao.cc>
To: Jonas Karlman <jonas@kwiboo.se>, Yao Zi <ziyao@disroot.org>
Cc: Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>,
Tom Rini <trini@konsulko.com>, Sumit Garg <sumit.garg@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: Re: [PATCH 2/2] board: rockchip: Add FriendlyElec NanoPi Zero2
Date: Fri, 9 Jan 2026 05:59:11 +0000 [thread overview]
Message-ID: <aWCZLw6ROLDRX6M0@pie> (raw)
In-Reply-To: <f8b616ca-7930-4125-bbd8-6e3b96403651@kwiboo.se>
On Fri, Jan 09, 2026 at 02:26:25AM +0100, Jonas Karlman wrote:
> Hi Yao Zi,
>
> On 10/20/2025 4:27 AM, Yao Zi wrote:
> > On Sun, Oct 19, 2025 at 12:52:17PM +0200, Jonas Karlman wrote:
> >> Hi Yao Zi,
> >>
> >> On 10/19/2025 7:26 AM, Yao Zi wrote:
> >>> FriendlElec NanoPi Zero2 is a super-tiny development board based on
> >>> RK3528A SoC. Add board-level configuration and U-Boot-specific
> >>> devicetree piece for it.
> >>>
> >>> Signed-off-by: Yao Zi <ziyao@disroot.org>
> >>> ---
> >>> arch/arm/dts/rk3528-nanopi-zero2-u-boot.dtsi | 11 +++++
> >>> arch/arm/mach-rockchip/rk3528/MAINTAINERS | 6 +++
> >>> configs/nanopi-zero2_defconfig | 46 ++++++++++++++++++++
> >>> doc/board/rockchip/rockchip.rst | 1 +
> >>> 4 files changed, 64 insertions(+)
> >>> create mode 100644 arch/arm/dts/rk3528-nanopi-zero2-u-boot.dtsi
> >>> create mode 100644 configs/nanopi-zero2_defconfig
...
> >> With above adjustments this closely matches the defconfig I have been
> >> carrying in my rk3528 branch at [1] a few months.
> >>
> >> So with above fixed this is:
> >>
> >> Reviewed-by: Jonas Karlman <jonas@kwiboo.se>
> >
> > Thanks, these changes are all reasonable and I'll adapt them in v2.
> > Seems I did something wrong when doing savedefconfig and lost some
> > defconfig changes...
>
> Are you planing on sending out a v2 of this?
>
> I still carry my old version of this in my rk3528 branch, see [2], I
> can send that commit out if you do not have time to send a v2?
Sure, please go ahead and send yours instead, thanks. Sorry for the huge
delay.
> Btw, I should be able to send out a new revision of the Linux RK3528 USB
> series any day now, once I have completed re-testing.
>
> [2] https://source.denx.de/u-boot/contributors/kwiboo/u-boot/-/commit/e3f251b7828ddc09f0bc1c2240687c5ad22a40df
>
> Regards,
> Jonas
Regards,
Yao Zi
> >
> >> [1] https://source.denx.de/u-boot/contributors/kwiboo/u-boot/-/commits/rk3528
> >>
> >> I plan to send out a series with the ROCK-2 and Sige1 board additions shortly.
> >>
> >> Regards,
> >> Jonas
> >
> > Best regards,
> > Yao Zi
>
next prev parent reply other threads:[~2026-01-09 5:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-19 5:26 [PATCH 0/2] Add support for FriendlyElec NanoPi Zero2 board Yao Zi
2025-10-19 5:26 ` [PATCH 1/2] arm64: dts: rockchip: Add FriendlyElec NanoPi Zero2 Yao Zi
2025-10-19 5:26 ` [PATCH 2/2] board: " Yao Zi
2025-10-19 10:52 ` Jonas Karlman
2025-10-20 2:27 ` Yao Zi
2026-01-09 1:26 ` Jonas Karlman
2026-01-09 5:59 ` Yao Zi [this message]
2025-10-20 17:02 ` Quentin Schulz
2025-10-20 18:03 ` Jonas Karlman
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=aWCZLw6ROLDRX6M0@pie \
--to=me@ziyao.cc \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=sumit.garg@kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=ziyao@disroot.org \
/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.