netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Heiner Kallweit' <hkallweit1@gmail.com>,
	"Jia, Fang" <fang.jia@windriver.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"David S. Miller" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: phy: fixed link 1000 or 100 set with autoneg off
Date: Mon, 23 Oct 2023 14:57:43 +0000	[thread overview]
Message-ID: <1fc7704bfd664746bf93c65591efa071@AcuMS.aculab.com> (raw)
In-Reply-To: <c23dcdb0-f493-453d-82b9-b498f4d3c88b@gmail.com>

From: Heiner Kallweit
> Sent: 23 October 2023 08:52
> 
> On 23.10.2023 09:01, Jia, Fang wrote:
> > Hi Experts,
> >
> > We use NXP LS1046 board and face an issue about the eth interface speed.
> >
> > 1) Scenario
> >
> > we set fixed link 1000Mb/s in device tree.
> >
> > However, after we set the auto-neg off, then the eth1's speed changed to 10M and Duplex changed to Half.
> > The value of /sys/class/net/eth1/speed is 10 and /sys/class/net/eth1/duplex is half
> >
> Why do you set aneg to off? Leave aneg on, that's the only supported
> mode in swphy. 1000Mbps requires aneg anyway per standard.

Limiting the advertised modes has always worked better than
trying to set a fixed mode.
Although connect to a 10M hub (that sends out single link test pulses)
and you'll end up 10M/HDX regardless of the ANAR register. 

Not least of the problems is that you need to get the far end
to use exactly the same mode.

Otherwise it is very easy to get a mismatch.
In the 'old days' a HDX/FDX mismatch was easy to get and very confusing.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

      parent reply	other threads:[~2023-10-23 14:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23  7:01 phy: fixed link 1000 or 100 set with autoneg off Jia, Fang
2023-10-23  7:42 ` Bagas Sanjaya
2023-10-23  7:52 ` Heiner Kallweit
2023-10-23  8:34   ` Jia, Fang
2023-10-23 14:28     ` Andrew Lunn
2023-10-26  2:41       ` Jia, Fang
2023-10-23 14:57   ` David Laight [this message]

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=1fc7704bfd664746bf93c65591efa071@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=fang.jia@windriver.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).