From: Dinh Nguyen <dinguyen@opensource.altera.com>
To: Romain Perier <romain.perier@gmail.com>
Cc: <preid@electromag.com.au>,
"David S. Miller" <davem@davemloft.net>, robh <robh@kernel.org>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
<peppe.cavallaro@st.com>
Subject: Re: commit e34d65696d2e broke stmmac ethernet on socfpga
Date: Mon, 4 Jan 2016 09:19:02 -0600 [thread overview]
Message-ID: <568A8D66.3080000@opensource.altera.com> (raw)
In-Reply-To: <CABgxDo+uTgYVYE-E6gQCoeWaeV=GKZVw-99JEHChDr3QAs9TkA@mail.gmail.com>
On 01/01/2016 02:49 AM, Romain Perier wrote:
> Hi all,
>
> Same here on rockchip.
> See "[PATCH] stmmac: Don't exit mdio registration when mdio subnode is
> not found in the DTS"
>
> Regards,
> Romain
>
> 2015-12-18 18:45 GMT+01:00 Dinh Nguyen <dinguyen@opensource.altera.com>:
>> Hi,
>>
>> It appears that commit e34d65696d2e 'stmmac: create of compatible mdio
>> bus for
>> stmmac driver' is causing this error on the SoCFPGA platform:
>>
>> [ 1.767246] libphy: PHY stmmac-0:ffffffff not found
>> [ 1.772106] eth0: Could not attach to PHY
>> [ 1.776129] stmmac_open: Cannot attach to PHY (error: -19)
>> [ 1.781590] IP-Config: Failed to open eth0
>> [ 1.785681] IP-Config: No network devices available
>>
>> Doing a revert of this commit fixes the issue. Will try to debug further.
>>
There error is here:
[ 0.663275] socfpga-dwmac ff702000.ethernet eth0: NO MDIO subnode
It appears that his commit requires an update to DTS files, which will
subsequently break legacy DTS.
Also, this commit is only in linux-next.
Dinh
prev parent reply other threads:[~2016-01-04 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 17:45 commit e34d65696d2e broke stmmac ethernet on socfpga Dinh Nguyen
2016-01-01 8:49 ` Romain Perier
2016-01-04 15:19 ` Dinh Nguyen [this message]
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=568A8D66.3080000@opensource.altera.com \
--to=dinguyen@opensource.altera.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=preid@electromag.com.au \
--cc=robh@kernel.org \
--cc=romain.perier@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.