From: Arturas Moskvinas <arturas.moskvinas@gmail.com>
To: Jonas Karlman <jonas@kwiboo.se>
Cc: Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: rockchip: Add Xunlong Orange Pi 3B
Date: Sat, 8 Mar 2025 21:03:59 +0200 [thread overview]
Message-ID: <5bb045fe-89c3-46dd-bd9a-dee8800a6d58@gmail.com> (raw)
In-Reply-To: <29739e60-15f5-4361-a57a-2e6b93fba09c@kwiboo.se>
On 3/8/25 6:34 PM, Jonas Karlman wrote:
> This is because of a reset issue with Ethernet PHYs in Linux, see [1].
>
> Two workarounds:
> 1. Let boot firmware reset the PHY before Linux, i.e. use U-Boot
> v2024.10 or newer.
> 2. Use a ethernet-phy-id compatible with correct phy-id to force Linux
> to attach the PHY.
>
> I suggest you try to wipe U-Boot from SPI flash on your board and update
> to use U-Boot v2025.01 and try again.
Wiping board SPI flash which contained old U-boot and using 2025.01 from
SD card fixed issue hence DTS is OK.
Though I do not remember that I ever wrote anything into SPI flash in
first place (I touched board almost year ago so potentially forgot about
it) maybe it was shipped like that with the board...
Arturas Moskvinas
next prev parent reply other threads:[~2025-03-08 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 23:03 [PATCH v2 0/2] arm64: dts: rockchip: Add Xunlong Orange Pi 3B Jonas Karlman
2024-06-26 23:03 ` [PATCH v2 1/2] dt-bindings: arm: " Jonas Karlman
2024-06-27 7:47 ` Krzysztof Kozlowski
2024-06-26 23:03 ` [PATCH v2 2/2] arm64: dts: " Jonas Karlman
2024-06-28 0:01 ` kernel test robot
2024-06-28 10:49 ` kernel test robot
2025-03-08 14:53 ` Arturas Moskvinas
2025-03-08 16:34 ` Jonas Karlman
2025-03-08 19:03 ` Arturas Moskvinas [this message]
2024-06-27 14:34 ` [PATCH v2 0/2] " Rob Herring (Arm)
2024-07-08 22:27 ` Heiko Stuebner
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=5bb045fe-89c3-46dd-bd9a-dee8800a6d58@gmail.com \
--to=arturas.moskvinas@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).