[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6ca63f35-05c4-472d-a412-74e5c7ffeefb@lunn.ch>
Date: Tue, 18 Mar 2025 17:54:06 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Rajaganesh Rathinasabapathi <rrathina@....com>
Cc: Rajaganesh Rathinasabapathi <Rajaganesh.Rathinasabapathi@....com>,
devicetree@...r.kernel.org, openbmc@...ts.ozlabs.org,
joel@....id.au, andrew@...econstruct.com.au, robh+dt@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-aspeed@...ts.ozlabs.org,
linux-kernel@...r.kernel.org,
Supreeth Venkatesh <supreeth.venkatesh@....com>, jothayot@....com
Subject: Re: [PATCH v3 2/2] ARM:dts:aspeed: Initial device tree for AMD Onyx
Platform
On Tue, Mar 18, 2025 at 10:18:46PM +0530, Rajaganesh Rathinasabapathi wrote:
> On 3/18/25 19:38, Andrew Lunn wrote:
> > Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
> >
> >
> >> +&mac3 {
> >> + status = "okay";
> >> + phy-mode = "rgmii";
> >
> > Does the PCB have extra long clock lines to insert the 2ns RGMII
> > delay? Or are you another victim of aspeeds broken MAC/SCU driver?
> >
> > Andrew
> We're following Aspeed SDK and referred other dts based on ast2600.
Which are all broken.
At the moment, you are joining NVIDIA and IBM waiting for Aspeed to
sort out this mess. Maybe you can apply some pressure...
Andrew
Powered by blists - more mailing lists