Subject: Re: HW question: i210 vs. BCM5461S over SGMII: no response from PHY to MDIO requests?

From: Andrew Lunn <[email-masked]>
Date: Sat, 17 Mar 2018 15:50:36 +0100

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