From: Kel Modderman <kelvmod@gmail.com>
To: Dennis Gilmore <dennis@ausil.us>
Cc: u-boot@lists.u-boot-project.org,
Quentin Schulz <u-boot@0leil.net>,
Kever Yang <kever.yang@rock-chips.com>,
Simon Glass <sjg@chromium.org>,
Sumit Garg <sumit.garg@kernel.org>,
Jonas Karlman <jonas@kwiboo.se>,
Alexey Charkov <alchark@gmail.com>,
Peter Robinson <pbrobinson@gmail.com>,
Tom Rini <trini@konsulko.com>, Kel Modderman <kelvmod@gmail.com>
Subject: Re: [PATCH v2 0/5] rockchip: Add Xunlong Orange Pi 5 Pro
Date: Mon, 19 Oct 2026 20:46:30 +1000 [thread overview]
Message-ID: <20261019104630.2596905-1-kelvmod@gmail.com> (raw)
In-Reply-To: <20261012020134.621305-1-dennis@ausil.us>
Hi Dennis,
Sorry, I missed that v2 was out - I'd been testing your v1 the whole
time. v2 works fine on my board, a 4GB Orange Pi 5 Pro with the YT6801
NIC and an NVMe in the M.2 slot.
I tested patches 1-5 on v2026.10 in both a LibreELEC and an OpenWrt
build, with rkbin DDR v1.19 and TF-A v2.15. v2 as posted boots from SD,
and with PREBOOT="pci enum;" added it boots as well, where v1 hung every
time. So the -u-boot.dtsi change fixes it. Linux then sees the NVMe and
the YT6801 at 1 Gbps.
Tested-by: Kel Modderman <kelvmod@gmail.com>
Thanks heaps,
Kel
prev parent reply other threads:[~2026-10-19 13:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 2:01 [PATCH v2 0/5] rockchip: Add Xunlong Orange Pi 5 Pro Dennis Gilmore
2026-10-12 2:01 ` [PATCH v2 1/5] dt-bindings: arm: rockchip: Add " Dennis Gilmore
2026-10-12 2:01 ` [PATCH v2 2/5] arm64: dts: rockchip: rename PLDO regulator labels to match schematic on rk3588s-orangepi-5 Dennis Gilmore
2026-10-12 2:01 ` [PATCH v2 3/5] arm64: dts: rockchip: refactor items from Orange Pi 5/b to prep for Pro Dennis Gilmore
2026-10-12 2:01 ` [PATCH v2 4/5] arm64: dts: rockchip: Add Orange Pi 5 Pro board support Dennis Gilmore
2026-10-12 2:01 ` [PATCH v2 5/5] board: rockchip: Add Xunlong Orange Pi 5 Pro Dennis Gilmore
2026-10-27 17:17 ` Quentin Schulz
2026-10-28 4:46 ` Dennis Gilmore
2026-10-19 10:46 ` Kel Modderman [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=20261019104630.2596905-1-kelvmod@gmail.com \
--to=kelvmod@gmail.com \
--cc=alchark@gmail.com \
--cc=dennis@ausil.us \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=pbrobinson@gmail.com \
--cc=sjg@chromium.org \
--cc=sumit.garg@kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot@0leil.net \
--cc=u-boot@lists.u-boot-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox