From: Dragan Simic <dsimic@manjaro.org>
To: Himanshu Bhavani <himanshu.bhavani@siliconsignals.io>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>, Lorenz Brun <lorenz@brun.one>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: add &gmac2phy in rk3328-rock64
Date: Fri, 15 Mar 2024 20:04:11 +0100 [thread overview]
Message-ID: <0f674cf37d01e1a6651068b0402e766c@manjaro.org> (raw)
In-Reply-To: <PN3PR01MB10135290B74FD411720E431989A282@PN3PR01MB10135.INDPRD01.PROD.OUTLOOK.COM>
On 2024-03-15 16:02, Himanshu Bhavani wrote:
>> Unfortunately, this isn't an acceptable change to the Rock64 dts file.
>> Yes, there's the second built-in Ethernet interface in the RK3328 SoC,
>> but the Rock64 layout doesn't expose it as a separate physical network
>> interface, i.e. it isn't available as a port.
>
> I was wondering if the Rock64 lacks a port.
> According to this link: https://pine64.org/devices/rock64/,
> it seems that there is a physical network interface available on the
> sbc.
As I already described in my previous response, there's another Ethernet
interface in the RK3328 SoC, which the Rock64 is based on, but there's
no
second Ethernet port on the actual printed circuit board. That's simply
how the Rock64 was designed and manufactured.
>> Such a change would be fine to be applied to the dts by hand, by
>> someone
>> who actually adds a second physical network port to their Rock64.
prev parent reply other threads:[~2024-03-15 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 8:40 Himanshu Bhavani
2024-03-15 8:56 ` Dragan Simic
2024-03-15 15:02 ` Himanshu Bhavani
2024-03-15 19:04 ` Dragan Simic [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=0f674cf37d01e1a6651068b0402e766c@manjaro.org \
--to=dsimic@manjaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=himanshu.bhavani@siliconsignals.io \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lorenz@brun.one \
--cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®