From: Joshua Milas <josh.milas@gmail.com>
To: Michael Opdenacker <michael.opdenacker@rootcommit.com>
Cc: tglx@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, pjw@kernel.org, samuel.holland@sifive.com,
unicorn_wang@outlook.com, inochiama@gmail.com,
daniel.lezcano@linaro.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr,
liujingqi@lanxincomputing.com, alexander.sverdlin@gmail.com,
rabenda.cn@gmail.com, dlan@kernel.org, chao.wei@sophgo.com,
anup@brainfault.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
sophgo@lists.linux.dev, hanguidong02@gmail.com
Subject: Re: [PATCH v4 0/5] Add initial Milk-V Duo S board support
Date: Thu, 2 Apr 2026 08:29:10 -0400 [thread overview]
Message-ID: <ac5hFgLav_4oB2QA@sleek> (raw)
In-Reply-To: <88400fa8-4545-49eb-af04-d82b94a89757@rootcommit.com>
Hi Michael,
Thanks for testing this. I am not seeing that issue on my arm64 or riscv side.
I am able to add an IP and do anything I can think of on the arm64 side.
[ 96.618687] stmmaceth 4070000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0
[ 96.633977] stmmaceth 4070000.ethernet eth0: PHY [mdio_mux-0.0:01] driver [Generic PHY] (irq=POLL)
[ 96.676436] dwmac1000: Master AXI performs any burst length
[ 96.702852] stmmaceth 4070000.ethernet eth0: No Safety Features support found
[ 96.748740] stmmaceth 4070000.ethernet eth0: IEEE 1588-2002 Timestamp supported
[ 96.772880] stmmaceth 4070000.ethernet eth0: configuring for phy/internal link mode
[ 1359.377528] stmmaceth 4070000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
I can do the same on the riscv side but get a unhandled signal for TLS traffic
which I believe is unrelated as it doesn't happen on adding an IP.
I'll send over my configs to see if that helps.
Have a great day,
- Joshua Milas
next prev parent reply other threads:[~2026-04-02 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 17:34 [PATCH v4 0/5] Add initial Milk-V Duo S board support Joshua Milas
2026-03-28 17:34 ` [PATCH v4 1/5] dt-bindings: soc: sophgo: add Milk-V Duo S board compatibles Joshua Milas
2026-03-28 17:34 ` [PATCH v4 2/5] arm64: dts: sophgo: add initial Milk-V Duo S board support Joshua Milas
2026-03-29 20:21 ` Michael Opdenacker
2026-04-02 12:14 ` Joshua Milas
2026-03-28 17:34 ` [PATCH v4 3/5] dt-bindings: soc: sophgo: add sg2000 plic and clint documentation Joshua Milas
2026-03-28 17:34 ` [PATCH v4 4/5] riscv64: dts: sophgo: add SG2000 dtsi Joshua Milas
2026-03-28 17:34 ` [PATCH v4 5/5] riscv64: dts: sophgo: add initial Milk-V Duo S board support Joshua Milas
2026-03-29 21:14 ` [PATCH v4 0/5] Add " Michael Opdenacker
2026-04-02 12:29 ` Joshua Milas [this message]
2026-04-02 13:47 ` Michael Opdenacker
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=ac5hFgLav_4oB2QA@sleek \
--to=josh.milas@gmail.com \
--cc=alex@ghiti.fr \
--cc=alexander.sverdlin@gmail.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=chao.wei@sophgo.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=hanguidong02@gmail.com \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liujingqi@lanxincomputing.com \
--cc=michael.opdenacker@rootcommit.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rabenda.cn@gmail.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=sophgo@lists.linux.dev \
--cc=tglx@kernel.org \
--cc=unicorn_wang@outlook.com \
/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