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: Sat, 17 Mar 2018 15:50:36 +0100 [thread overview]
Message-ID: <20180317145036.GA21704@lunn.ch> (raw)
In-Reply-To: <5AACC614.18709.335BD813@Frantisek.Rysanek.post.cz>
On Sat, Mar 17, 2018 at 08:39:00AM +0100, Frantisek Rysanek wrote:
> On 16 Mar 2018 at 22:02, Andrew Lunn wrote:
> >
> > Does ethtool -m show anything useful?
> >
>
> Not much. "unsupported".
static int igb_get_module_info(struct net_device *netdev,
struct ethtool_modinfo *modinfo)
{
struct igb_adapter *adapter = netdev_priv(netdev);
struct e1000_hw *hw = &adapter->hw;
u32 status = 0;
u16 sff8472_rev, addr_mode;
bool page_swap = false;
if ((hw->phy.media_type == e1000_media_type_copper) ||
(hw->phy.media_type == e1000_media_type_unknown))
return -EOPNOTSUPP;
Suggests that the driver does not know you have a fibre module.
> Right now I've modded igb_init_i2c() to engage the bit-banging
> i2c driver for the i210 too
I don't think that will work. The datasheet for the i210 talks about
two registers for I2C/MDIO which are not bit-banging. Only the i350
uses bit-banging.
Andrew
next prev parent reply other threads:[~2018-03-17 14:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 16:48 HW question: i210 vs. BCM5461S over SGMII: no response from PHY to MDIO requests? 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 [this message]
2018-03-17 15:20 ` Frantisek Rysanek
-- strict thread matches above, loose matches on Subject: below --
2018-03-17 22:12 Frantisek Rysanek
2018-03-18 14:40 ` Andrew Lunn
2018-03-20 9:02 ` Frantisek Rysanek
2018-03-20 12:09 ` Andrew Lunn
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
2018-03-21 11:50 Frantisek Rysanek
2018-03-21 12:58 ` Andrew Lunn
2018-03-21 14:07 ` 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=20180317145036.GA21704@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).