[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <39ce904c-91cd-e651-fe21-b13056e67ff8@gmail.com>
Date: Mon, 11 Mar 2019 11:11:11 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Marc Kleine-Budde <mkl@...gutronix.de>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
ptx kernel <kernel@...gutronix.de>,
Heiner Kallweit <hkallweit1@...il.com>,
Andrew Lunn <andrew@...n.ch>
Subject: Re: BUG: "13d0ab6750b2 net: phy: check return code when requesting
PHY driver module" breaks NFS-Root
On 3/11/19 11:04 AM, Marc Kleine-Budde wrote:
> On 3/11/19 1:23 PM, Marc Kleine-Budde wrote:
>> Hello,
>>
>> I'm on next-next/master and noticed that the following patch:
>>
>> | 13d0ab6750b2 net: phy: check return code when requesting PHY
>> | driver module
>>
>> breaks NFS Root for my embedded device (riotboard). The kernel dhcp
>> fails to get an address and thus no NFS Root.
>
> Just noticed that problem was fixed by commit:
>
> | 21e194425abd net: phy: fix issue with loading PHY driver w/o initramfs
>
> I continued bisecting and found a bad commit in the riotboard's phy
> driver. I'll send a separate mail for this.
>
> | cd28d1d6e52e net: phy: at803x: Disable phy delay for RGMII mode
If your problem is with this driver, keep in mind that the at803x PHY
driver incorrectly acted on the 'phy-mode'/phy_interface_t type and you
may need DTS changes to be conforming. Of course, there is no way to
programmatically detect any of that, which adds to the fun.
--
Florian
Powered by blists - more mailing lists