From: Marek Behun <marek.behun@nic.cz>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>, andrew@lunn.ch
Cc: netdev@vger.kernel.org, olteanv@gmail.com, pavana.sharma@digi.com
Subject: Re: mv88e6xxx: 2500base-x inband AN is broken on Amethyst? what to do?
Date: Wed, 13 Jan 2021 05:22:48 +0100 [thread overview]
Message-ID: <20210113052248.53f6032c@nic.cz> (raw)
In-Reply-To: <20210113011823.3e407b31@kernel.org>
It seems this problem can manifest somehow with Peridot as well, at
least when in combination with 88X3310 PHY.
I will do some more experiments and try to come up with a solution.
Marek
next prev parent reply other threads:[~2021-01-13 4:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 0:18 mv88e6xxx: 2500base-x inband AN is broken on Amethyst? what to do? Marek Behún
2021-01-13 4:22 ` Marek Behun [this message]
2021-01-13 10:28 ` Russell King - ARM Linux admin
2021-01-13 17:03 ` Marek Behún
2021-01-13 20:08 ` Marek Behún
2021-01-13 21:21 ` Russell King - ARM Linux admin
2021-01-13 21:37 ` Marek Behún
2021-01-13 21:48 ` Russell King - ARM Linux admin
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=20210113052248.53f6032c@nic.cz \
--to=marek.behun@nic.cz \
--cc=andrew@lunn.ch \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pavana.sharma@digi.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 NNTP newsgroup(s).