From: Yixun Lan <dlan@gentoo.org>
To: Hendrik Hammernet <hendrik.hamerlinck@hammernet.be>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
paul.walmsley@sifive.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
palmer@dabbelt.com, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linux.dev, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] riscv: dts: spacemit: Add OrangePi RV2 board device tree
Date: Wed, 16 Jul 2025 19:33:54 +0800 [thread overview]
Message-ID: <20250716113354-GYB546922@gentoo> (raw)
In-Reply-To: <95125019-8eaa-4242-8e68-78771ce85947@hammernet.be>
Hi Hendrik,
On 11:37 Wed 16 Jul , Hendrik Hammernet wrote:
> Hello,
>
> Thank you for the review.
>
> On 7/15/25 12:25, Yixun Lan wrote:
> > On 20:32 Fri 11 Jul , Hendrik Hamerlinck wrote:
> >
> >> +/* Copyright (c) 2023 Ky, Inc */
> > Copyright should cover current year, which is 2025..
> > what's "Ky" stand for? Can you give a full description here
> Regarding the original copyright:
> This file was based on a version from the Ky, Inc downstream kernel, which
> itself appears to be adapted from earlier SpacemiT sources (dated 2023).
> The Orange Pi RV2 board, however, was only released in 2025, suggesting
> that the Ky version was likely copied and renamed from earlier generic
> SpacemiT files.
>
> In reviewing the Ky downstream tree, I also noticed that several files had
> their copyright statements overwritten with "Ky, Inc", while the original
> years (e.g., 2023) remained unchanged. This makes the provenance a bit
> unclear.
>
> Since I've significantly reworked the file for the actual Orange Pi RV2
> hardware, I’d prefer to attribute it under my own name, unless retaining
> the original "Ky, Inc" is required.
>
Personally, your approach looks good to me
> Please let me know what would be appropriate here.
>
I'm no expert on this, unless people want the more strict way..
Personally, the dts file already has correct Copyright info with
the "SPDX-License-Identifier" line, additional info gives credits
for people who really contributed on this..
> >> + memory@0 {
> >> + device_type = "memory";
> >> + reg = <0x0 0x00000000 0x0 0x80000000>;
> >> + };
> >> +
> >> + memory@100000000 {
> >> + device_type = "memory";
> >> + reg = <0x1 0x00000000 0x0 0x80000000>;
> >> + };
> >> +
> > for the memory nodes, there are 2/4/8GB variants from the Link [1], and
> > you couldn't cover all of them in one dt
> >
> > besides, I thought bootloader (u-boot) will populate these info, right?
> > so the above nodes isn't really necessary
> >
> You're absolutely right, U-Boot does populate this information correctly
> at runtime. I will remove the memory nodes in the next version.
>
> I also noticed that the aliases section is missing in this version, which
> means the chosen.stdout-path = "serial0" reference won’t resolve unless
> serial0 = &uart0; is defined. I didn't encounter issues during testing
> because I'm overriding the boot command in my Buildroot setup, but I’ll
> add the proper aliases node in the next version to ensure upstream
> compatibility.
>
right, please!
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2025-07-16 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 18:32 [PATCH 0/2] riscv: dts: spacemit: Add initial support for OrangePi RV2 Hendrik Hamerlinck
2025-07-11 18:32 ` [PATCH 1/2] dt-bindings: riscv: spacemit: Add OrangePi RV2 board Hendrik Hamerlinck
2025-07-15 3:25 ` Rob Herring (Arm)
2025-07-11 18:32 ` [PATCH 2/2] riscv: dts: spacemit: Add OrangePi RV2 board device tree Hendrik Hamerlinck
2025-07-15 10:25 ` Yixun Lan
2025-07-16 9:37 ` Hendrik Hammernet
2025-07-16 11:33 ` Yixun Lan [this message]
2025-07-15 10:30 ` [PATCH 0/2] riscv: dts: spacemit: Add initial support for OrangePi RV2 Yixun Lan
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=20250716113354-GYB546922@gentoo \
--to=dlan@gentoo.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hendrik.hamerlinck@hammernet.be \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=spacemit@lists.linux.dev \
/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