From: Andrew Lunn <andrew@lunn.ch>
To: Frantisek Rysanek <Frantisek.Rysanek@post.cz>
Cc: netdev@vger.kernel.org
Subject: Re: HW question: i210 vs. BCM5461S over SGMII: no response from PHY to MDIO requests?
Date: Tue, 20 Mar 2018 13:09:36 +0100 [thread overview]
Message-ID: <20180320120936.GA19142@lunn.ch> (raw)
In-Reply-To: <5AB0CE14.3307.431B163E@Frantisek.Rysanek.post.cz>
> i2cdetect has found three i2c slaves (identical layout in both SFP's)
> at addresses 0x50, 0x51 and 0x56.
> What are they? EEPROM, DDM and "MDIO over i2c" ?
> The SFP's likely lack a proper SFP MSA data structure.
0x50 and 0x51 are EEPROM like. See drivers/net/phy/sfp.c. The standard
at24 EEPROM driver can also read it. And so should the SFP code in the
igb driver!
> Does this make sense as some sort of proprietary standard
> (Cisco, if I should take the vendor's label at face value),
> or is this likely some "3rd-party innovation thinko", not worth
> implementing?
See if drivers/net/phy/mdio-i2c.c is useful. I'm just guessing here.
Andrew
next prev parent reply other threads:[~2018-03-20 12:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 22:12 HW question: i210 vs. BCM5461S over SGMII: no response from PHY to MDIO requests? Frantisek Rysanek
2018-03-18 14:40 ` Andrew Lunn
2018-03-20 9:02 ` Frantisek Rysanek
2018-03-20 12:09 ` Andrew Lunn [this message]
2018-03-20 12:23 ` Frantisek Rysanek
2018-03-21 10:47 ` Frantisek Rysanek
2018-03-21 13:08 ` Andrew Lunn
2018-03-20 12:02 ` Frantisek Rysanek
-- strict thread matches above, loose matches on Subject: below --
2018-03-21 11:50 Frantisek Rysanek
2018-03-21 12:58 ` Andrew Lunn
2018-03-21 14:07 ` Frantisek Rysanek
2018-03-16 16:48 Frantisek Rysanek
2018-03-16 18:42 ` Andrew Lunn
2018-03-16 20:40 ` Frantisek Rysanek
2018-03-16 21:02 ` Andrew Lunn
2018-03-17 7:39 ` Frantisek Rysanek
2018-03-17 14:50 ` Andrew Lunn
2018-03-17 15:20 ` Frantisek Rysanek
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=20180320120936.GA19142@lunn.ch \
--to=andrew@lunn.ch \
--cc=Frantisek.Rysanek@post.cz \
--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).