From: Andrew Lunn <andrew@lunn.ch>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Yixun Lan <dlan@gentoo.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Maxime Ripard <mripard@kernel.org>,
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>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 4/5] arm64: dts: allwinner: a527: add EMAC0 to Radxa A5E board
Date: Thu, 24 Apr 2025 15:32:12 +0200 [thread overview]
Message-ID: <caad87f2-8243-4571-8236-6aa3d4fb9fab@lunn.ch> (raw)
In-Reply-To: <20250424142006.021d6ab4@donnerap.manchester.arm.com>
> Speaking of which: do you know of a good method to verify the delay
> timing? Is there *something* which is sensitive to those timings and which
> can be easily checked and qualified?
Not really. If you are on the edge, you might get more ethernet FCS
errors. For iperf3 in UDP mode, that would translate to packet loss.
Or ethtool -S might report checksum errors, depending on the driver.
From what i've heard from others there is a pretty sharp cut off from
broken to working. Just stay away from the cliff and it should be
O.K. for −40°C to 85°C, or whatever the temperate range is supposed to
be.
Andrew
next prev parent reply other threads:[~2025-04-24 14:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 14:03 [PATCH 0/5] allwinner: Add EMAC0 support to A523 variant SoC Yixun Lan
2025-04-23 14:03 ` [PATCH 1/5] dt-bindings: sram: sunxi-sram: Add A523 compatible Yixun Lan
2025-04-24 0:46 ` Andre Przywara
2025-04-23 14:03 ` [PATCH 2/5] dt-bindings: arm: sunxi: Add A523 EMAC0 compatible Yixun Lan
2025-04-24 0:48 ` Andre Przywara
2025-04-23 14:03 ` [PATCH 3/5] arm64: dts: allwinner: a523: Add EMAC0 ethernet MAC Yixun Lan
2025-04-24 0:43 ` Andre Przywara
2025-04-24 3:28 ` Yixun Lan
2025-04-24 10:28 ` Chen-Yu Tsai
2025-04-23 14:03 ` [PATCH 4/5] arm64: dts: allwinner: a527: add EMAC0 to Radxa A5E board Yixun Lan
2025-04-23 16:58 ` Andrew Lunn
2025-04-24 0:42 ` Andre Przywara
2025-04-24 10:05 ` Yixun Lan
2025-04-24 12:05 ` Andre Przywara
2025-04-24 12:19 ` Andrew Lunn
2025-04-24 13:20 ` Andre Przywara
2025-04-24 13:32 ` Andrew Lunn [this message]
2025-04-24 12:16 ` Andrew Lunn
2025-04-24 12:41 ` Andre Przywara
2025-04-24 12:57 ` Andrew Lunn
2025-04-24 14:00 ` Andre Przywara
2025-04-24 18:38 ` Jernej Škrabec
2025-04-24 19:02 ` Andrew Lunn
2025-04-24 19:05 ` Chen-Yu Tsai
2025-04-24 19:21 ` Jernej Škrabec
2025-04-24 22:56 ` Andre Przywara
2025-04-25 2:01 ` Andrew Lunn
2025-04-25 13:22 ` Andre Przywara
2025-04-24 0:43 ` Andre Przywara
2025-04-24 3:24 ` Yixun Lan
2025-04-25 3:30 ` Chukun Pan
2025-04-25 7:46 ` Yixun Lan
2025-04-25 10:00 ` Chukun Pan
2025-04-23 14:03 ` [PATCH 5/5] arm64: dts: allwinner: t527: add EMAC0 to Avaoto-A1 board Yixun Lan
2025-04-23 16:59 ` Andrew Lunn
2025-04-24 1:17 ` Andre Przywara
2025-04-24 3:25 ` 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=caad87f2-8243-4571-8236-6aa3d4fb9fab@lunn.ch \
--to=andrew@lunn.ch \
--cc=andre.przywara@arm.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=edumazet@google.com \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.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).