From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from vps0.lunn.ch ([185.16.172.187]:33983 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752692AbeCQOuj (ORCPT ); Sat, 17 Mar 2018 10:50:39 -0400 Date: Sat, 17 Mar 2018 15:50:36 +0100 From: Andrew Lunn To: Frantisek Rysanek Cc: netdev@vger.kernel.org Subject: Re: HW question: i210 vs. BCM5461S over SGMII: no response from PHY to MDIO requests? Message-ID: <20180317145036.GA21704@lunn.ch> References: <5AABF554.3719.302C6988@Frantisek.Rysanek.post.cz> <5AAC2BA1.5854.31008546@Frantisek.Rysanek.post.cz> <20180316210240.GB8735@lunn.ch> <5AACC614.18709.335BD813@Frantisek.Rysanek.post.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5AACC614.18709.335BD813@Frantisek.Rysanek.post.cz> Sender: netdev-owner@vger.kernel.org List-ID: 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