From: Max Hsu <max.hsu@sifive.com>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Samuel Holland <samuel.holland@sifive.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Thomas Gleixner <tglx@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Conor Dooley <conor@kernel.org>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Paul Walmsley <paul.walmsley@sifive.com>,
Max Hsu <max.hsu@sifive.com>
Subject: [PATCH 4/5] riscv: dts: sifive: fu740: Use correct ethernet compatible string
Date: Fri, 20 Feb 2026 16:27:08 +0800 [thread overview]
Message-ID: <20260220-fu740-v1-4-c8af54130c58@sifive.com> (raw)
In-Reply-To: <20260220-fu740-v1-0-c8af54130c58@sifive.com>
Update the ethernet node compatible string from "sifive,fu540-c000-gem"
to "sifive,fu740-c000-gem" to comply with the SiFive IP versioning
scheme documented in sifive-blocks-ip-versioning.txt.
The versioning scheme requires SoC-specific compatible strings even when
IP blocks are functionally identical.
Signed-off-by: Max Hsu <max.hsu@sifive.com>
---
arch/riscv/boot/dts/sifive/fu740-c000.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/riscv/boot/dts/sifive/fu740-c000.dtsi b/arch/riscv/boot/dts/sifive/fu740-c000.dtsi
index 6150f3397bff..15e11a03582a 100644
--- a/arch/riscv/boot/dts/sifive/fu740-c000.dtsi
+++ b/arch/riscv/boot/dts/sifive/fu740-c000.dtsi
@@ -273,7 +273,7 @@ spi0: spi@10050000 {
status = "disabled";
};
eth0: ethernet@10090000 {
- compatible = "sifive,fu540-c000-gem";
+ compatible = "sifive,fu740-c000-gem";
interrupt-parent = <&plic0>;
interrupts = <55>;
reg = <0x0 0x10090000 0x0 0x2000>,
--
2.43.0
next prev parent reply other threads:[~2026-02-20 8:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 8:27 [PATCH 0/5] riscv: dts: sifive: fu740: Fix compatible strings per IP versioning Max Hsu
2026-02-20 8:27 ` [PATCH 1/5] dt-bindings: net: macb: Add SiFive FU740-C000 support Max Hsu
2026-02-20 9:29 ` Conor Dooley
2026-02-20 18:42 ` Max Hsu
2026-02-20 8:27 ` [PATCH 2/5] dt-bindings: interrupt-controller: Add SiFive FU740-C000 PLIC Max Hsu
2026-02-20 9:23 ` Conor Dooley
2026-02-20 18:49 ` Max Hsu
2026-02-20 22:33 ` Conor Dooley
2026-02-20 8:27 ` [PATCH 3/5] net: macb: Add support for SiFive FU740-C000 Max Hsu
2026-02-20 13:13 ` Andrew Lunn
2026-02-20 18:35 ` Max Hsu
2026-02-20 22:00 ` Conor Dooley
2026-02-20 8:27 ` Max Hsu [this message]
2026-02-20 8:27 ` [PATCH 5/5] riscv: dts: sifive: fu740: Use correct PLIC compatible string Max Hsu
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=20260220-fu740-v1-4-c8af54130c58@sifive.com \
--to=max.hsu@sifive.com \
--cc=alex@ghiti.fr \
--cc=andrew+netdev@lunn.ch \
--cc=aou@eecs.berkeley.edu \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@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®