[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cfb43b2c-79f3-48b7-8466-e7f52d20ee56@lunn.ch>
Date: Sat, 14 Sep 2024 16:50:02 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Stefan Eichenberger <eichest@...il.com>
Cc: Niklas Söderlund <niklas.soderlund+renesas@...natech.se>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Dimitri Fedrau <dima.fedrau@...il.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
netdev@...r.kernel.org, linux-renesas-soc@...r.kernel.org
Subject: Re: [net-next 3/3] net: phy: marvell-88q2xxx: Enable auto
negotiation for mv88q2110
> master, I can normally do:
> ethtool -s end1 speed 1000 master-slave forced-slave
You might want to try adding 'autoneg off'
If the new default is to perform autoneg, speed 1000 tells it to try
to autoneg only advertising 1000. If the link partner is not actually
performing autoneg, it will never succeed.
This is the regression i was talking about. For this device, due to
its history, we might want to default to autoneg off.
Andrew
Powered by blists - more mailing lists