From: Andrew Lunn <andrew@lunn.ch>
To: Daniel Walker <danielwa@cisco.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Andy Fleming <afleming@freescale.com>,
Harini Katakam <harini.katakam@xilinx.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
HEMANT RAMDASI <hramdasi@cisco.com>,
"Julius Hemanth Pitti -X (jpitti - MONTA VISTA SOFTWARE INC at
Cisco)" <jpitti@cisco.com>,
"GokulChand Casheekar (gcasheek)" <gcasheek@cisco.com>
Subject: Re: Marvell phy errata origins?
Date: Tue, 25 Sep 2018 17:34:48 +0200 [thread overview]
Message-ID: <20180925153448.GC1676@lunn.ch> (raw)
In-Reply-To: <84bfdc12-800c-2f63-3eff-416cf560e18c@cisco.com>
> I've added Gokul who reported the issue to me. Is it possible that Harini
> and Cisco have different m88e1111 phys? Maybe there's an issue with how they
> are hooked up ?
Hi Daniel
The lower 4 bits of the ID registers normally indicate the revision of
the PHY. It might be worth checking if everybody has the same
revision, or the problems are limited to just one revision.
Andrew
next prev parent reply other threads:[~2018-09-25 21:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 13:16 Marvell phy errata origins? Daniel Walker
2017-04-18 14:04 ` Andrew Lunn
2017-04-18 14:18 ` Daniel Walker
2017-04-18 14:31 ` Harini Katakam
2017-04-18 14:35 ` Daniel Walker
2017-04-18 14:41 ` Harini Katakam
2017-04-18 14:56 ` Daniel Walker
2017-04-18 15:09 ` Harini Katakam
2017-05-09 13:58 ` Daniel Walker
2017-05-09 14:24 ` Andrew Lunn
2018-09-25 15:16 ` Daniel Walker
2018-09-25 15:34 ` Andrew Lunn [this message]
2018-09-25 15:39 ` Andrew Lunn
2018-09-25 17:30 ` Harini Katakam
2018-09-26 5:42 ` Harini Katakam
2018-09-26 15:35 ` Daniel Walker
2018-10-01 10:26 ` GokulChand Casheekar (gcasheek)
2018-10-04 7:27 ` GokulChand Casheekar (gcasheek)
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=20180925153448.GC1676@lunn.ch \
--to=andrew@lunn.ch \
--cc=afleming@freescale.com \
--cc=danielwa@cisco.com \
--cc=f.fainelli@gmail.com \
--cc=gcasheek@cisco.com \
--cc=harini.katakam@xilinx.com \
--cc=hramdasi@cisco.com \
--cc=jpitti@cisco.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.