From: Andrew Lunn <andrew@lunn.ch>
To: Sasha Neftin <sasha.neftin@intel.com>
Cc: "Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
Ricky Wu <en-wei.wu@canonical.com>,
netdev@vger.kernel.org, rickywu0421@gmail.com,
linux-kernel@vger.kernel.org, edumazet@google.com,
intel-wired-lan@lists.osuosl.org, kuba@kernel.org,
anthony.l.nguyen@intel.com, pabeni@redhat.com,
davem@davemloft.net, "Lifshits,
Vitaly" <vitaly.lifshits@intel.com>,
"naamax.meir" <naamax.meir@linux.intel.com>,
"Avivi, Amir" <amir.avivi@intel.com>,
"Keller, Jacob E" <jacob.e.keller@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH v2 2/2] e1000e: fix link fluctuations problem
Date: Fri, 10 May 2024 14:32:22 +0200 [thread overview]
Message-ID: <5669c185-db96-4ac2-81d5-2198060ae77d@lunn.ch> (raw)
In-Reply-To: <b288926e-f9d6-48d5-9851-078a6c9912bf@intel.com>
> > It would be interesting to see what the link partner sees. What does
> > it think the I219-LM is advertising? Is it advertising 1000BaseT_Half?
>
> i219 parts come with LSI PHY. 1000BASE-T half-duplex is not supported.
> 1000BASET half-duplex not advertised in IEEE 1000BASE-T Control Register 9.
That is the theory. But in practice? What does the link partner really
see? I've come across systems which get advertisement wrong. However,
in that case, i suspect it is the software above the PHY, not the PHY
itself which was wrong.
Andrew
next prev parent reply other threads:[~2024-05-10 12:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 10:18 [PATCH v2 2/2] e1000e: fix link fluctuations problem Ricky Wu
2024-05-07 12:31 ` Andrew Lunn
2024-05-08 5:05 ` [Intel-wired-lan] " Sasha Neftin
2024-05-09 9:13 ` Ruinskiy, Dima
2024-05-09 13:46 ` Andrew Lunn
2024-05-09 17:40 ` En-Wei WU
2024-05-10 9:55 ` Sasha Neftin
2024-05-10 12:32 ` Andrew Lunn [this message]
2024-05-13 6:04 ` Sasha Neftin
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=5669c185-db96-4ac2-81d5-2198060ae77d@lunn.ch \
--to=andrew@lunn.ch \
--cc=amir.avivi@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dima.ruinskiy@intel.com \
--cc=edumazet@google.com \
--cc=en-wei.wu@canonical.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naamax.meir@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rickywu0421@gmail.com \
--cc=sasha.neftin@intel.com \
--cc=vitaly.lifshits@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).