All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: krzk@kernel.org, Jianfeng Liu <liujianfeng1994@gmail.com>
Cc: HystericalDragons@proton.me, amadeus@jmu.edu.cn,
	conor+dt@kernel.org, devicetree@vger.kernel.org,
	hrushirajg23@gmail.com, krzk+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	liujianfeng1994@gmail.com, macromorgan@hotmail.com,
	michael.opdenacker@rootcommit.com, naoki@radxa.com,
	robh@kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: arm: rockchip: Add ArmSoM Sige7s
Date: Mon, 26 Oct 2026 12:43:10 +0100	[thread overview]
Message-ID: <5520293.6fTUFtlzNn@phil> (raw)
In-Reply-To: <20261026075915.203854-1-liujianfeng1994@gmail.com>

Am Montag, 26. Oktober 2026, 08:59:14 Mitteleuropäische Normalzeit schrieb Jianfeng Liu:
> Hi Krzysztof,
> 
> On 2026-10-26  7:08 UTC, Krzysztof Kozlowski wrote:
> >> The ArmSoM Sige7s is an RK3588S-based single-board computer which
> >> shares its hardware design with the CoolPi 4B.
> >
> >How different devices from different vendors can share design?
> >
> >
> >What is exactly is shared and how did you verify that?
> 
> I confirmed this with ArmSoM. They purchased the original CoolPi 4B
> hardware design from CoolPi and confirmed that no hardware design
> modifications were made for the Sige7s.
> 
> So the Sige7s uses the same hardware design as the CoolPi 4B, rather
> than being independently designed.

if it's the completely same board, just with a different print on
the board, why does it need an empty devicetree. When it's completely
unchanged, what's speaking against just re-using the original one?


Heiko



_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: krzk@kernel.org, Jianfeng Liu <liujianfeng1994@gmail.com>
Cc: HystericalDragons@proton.me, amadeus@jmu.edu.cn,
	conor+dt@kernel.org, devicetree@vger.kernel.org,
	hrushirajg23@gmail.com, krzk+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	liujianfeng1994@gmail.com, macromorgan@hotmail.com,
	michael.opdenacker@rootcommit.com, naoki@radxa.com,
	robh@kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: arm: rockchip: Add ArmSoM Sige7s
Date: Mon, 26 Oct 2026 12:43:10 +0100	[thread overview]
Message-ID: <5520293.6fTUFtlzNn@phil> (raw)
In-Reply-To: <20261026075915.203854-1-liujianfeng1994@gmail.com>

Am Montag, 26. Oktober 2026, 08:59:14 Mitteleuropäische Normalzeit schrieb Jianfeng Liu:
> Hi Krzysztof,
> 
> On 2026-10-26  7:08 UTC, Krzysztof Kozlowski wrote:
> >> The ArmSoM Sige7s is an RK3588S-based single-board computer which
> >> shares its hardware design with the CoolPi 4B.
> >
> >How different devices from different vendors can share design?
> >
> >
> >What is exactly is shared and how did you verify that?
> 
> I confirmed this with ArmSoM. They purchased the original CoolPi 4B
> hardware design from CoolPi and confirmed that no hardware design
> modifications were made for the Sige7s.
> 
> So the Sige7s uses the same hardware design as the CoolPi 4B, rather
> than being independently designed.

if it's the completely same board, just with a different print on
the board, why does it need an empty devicetree. When it's completely
unchanged, what's speaking against just re-using the original one?


Heiko




  reply	other threads:[~2026-10-26 11:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22 12:52 [PATCH 0/3] arm64: dts: rockchip: Add ArmSoM Sige7s support Jianfeng Liu
2026-10-22 12:52 ` Jianfeng Liu
2026-10-22 12:52 ` [PATCH 1/3] dt-bindings: arm: rockchip: Add ArmSoM Sige7s Jianfeng Liu
2026-10-22 12:52   ` Jianfeng Liu
2026-10-26  7:08   ` Krzysztof Kozlowski
2026-10-26  7:08     ` Krzysztof Kozlowski
2026-10-26  7:59     ` Jianfeng Liu
2026-10-26  7:59       ` Jianfeng Liu
2026-10-26 11:43       ` Heiko Stuebner [this message]
2026-10-26 11:43         ` Heiko Stuebner
2026-10-27  2:28         ` Jianfeng Liu
2026-10-27  2:28           ` Jianfeng Liu
2026-10-27  7:48           ` Krzysztof Kozlowski
2026-10-27  7:48             ` Krzysztof Kozlowski
2026-10-27  8:56             ` Jianfeng Liu
2026-10-27  8:56               ` Jianfeng Liu
2026-10-27  9:56               ` Krzysztof Kozlowski
2026-10-27  9:56                 ` Krzysztof Kozlowski
2026-10-28  1:42                 ` Jianfeng Liu
2026-10-28  1:42                   ` Jianfeng Liu
2026-10-27 16:03           ` Quentin Schulz
2026-10-27 16:03             ` Quentin Schulz
2026-10-28  1:50             ` Jianfeng Liu
2026-10-28  1:50               ` Jianfeng Liu
2026-10-22 12:52 ` [PATCH 2/3] arm64: dts: rockchip: Extract common CoolPi 4B board description Jianfeng Liu
2026-10-22 12:52   ` Jianfeng Liu
2026-10-22 12:52 ` [PATCH 3/3] arm64: dts: rockchip: Add ArmSoM Sige7s board Jianfeng Liu
2026-10-22 12:52   ` Jianfeng Liu

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=5520293.6fTUFtlzNn@phil \
    --to=heiko@sntech.de \
    --cc=HystericalDragons@proton.me \
    --cc=amadeus@jmu.edu.cn \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hrushirajg23@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=liujianfeng1994@gmail.com \
    --cc=macromorgan@hotmail.com \
    --cc=michael.opdenacker@rootcommit.com \
    --cc=naoki@radxa.com \
    --cc=robh@kernel.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.