From: Hsun Lai <i@chainsx.cn>
To: i@chainsx.cn
Cc: robh@kernel.org, andrew@lunn.ch, conor+dt@kernel.org,
inindev@gmail.com, heiko@sntech.de, jonas@kwiboo.se,
quentin.schulz@cherry.de, krzysztof.kozlowski@linaro.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
devicetree@vger.kernel.org, sfr@canb.auug.org.au,
krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [v3,1/3] dt-bindings: vendor-prefixes: Add SakuraPi prefix
Date: Tue, 20 May 2025 10:12:59 +0800 [thread overview]
Message-ID: <20250520021259.2387130-1-i@chainsx.cn> (raw)
In-Reply-To: <20250519075432.2239713-2-i@chainsx.cn>
On 5/19/25 10:20 AM, Quentin Schulz wrote:
> Would you know what the actual differences are? For the Station M2 they
> say "Based on ROC-RK3566-PC" which may indicate there are some
> additional things or changes? Same for the Station P2: "Based on
> ROC-RK3568-PC".
Station M3 is a product from Firefly. This product usually comes with an
outer case, and the internal board used is the ROC-RK3588S-PC development
board, which is why this situation occurs. The same applies to the
Station M2 (ROC-RK3566-PC) and Station P2 (ROC-RK3568-PC).
Thank you for your review!
Hsun
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-05-20 2:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 7:54 [PATCH v4 0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC Hsun Lai
2025-05-19 7:54 ` [PATCH v4 1/2] dt-bindings: arm: rockchip: Add Firefly ROC-RK3588S-PC Hsun Lai
2025-05-19 10:20 ` Quentin Schulz
2025-05-20 2:12 ` Hsun Lai [this message]
2025-05-19 7:54 ` [PATCH v4 2/2] arm64: dts: rockchip: add DTs for " Hsun Lai
2025-05-23 7:00 ` Chukun Pan
2025-05-23 7:12 ` Krzysztof Kozlowski
2025-05-23 10:26 ` Heiko Stübner
2025-05-19 13:01 ` [PATCH v4 0/2] Add support for Firefly Station-M3/ROC-RK3588S-PC Rob Herring (Arm)
-- strict thread matches above, loose matches on Subject: below --
2025-05-19 8:56 [PATCH v3 1/3] dt-bindings: vendor-prefixes: Add SakuraPi prefix Hsun Lai
2025-05-20 2:00 ` [v3,1/3] " Hsun Lai
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=20250520021259.2387130-1-i@chainsx.cn \
--to=i@chainsx.cn \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=inindev@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@cherry.de \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
/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