From: Robert Gadsdon <rhgadsdon@gmail.com>
To: Giuseppe CAVALLARO <peppe.cavallaro@st.com>,
John Keeping <john@metanate.com>
Cc: Gabriel Fernandez <gabriel.fernandez@linaro.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] stmmac: Fix phy without MDIO subnode
Date: Wed, 30 Mar 2016 11:22:42 -0700 [thread overview]
Message-ID: <56FC1972.9050704@gmail.com> (raw)
In-Reply-To: <56F4F9F6.8070103@st.com>
I have applied this to my Rock2 - Kernel 4.6-rc1 - and eth0 is present,
now, but no network traffic gets through:
To rock2:
$ ping rgrock2
PING rgrock2 (192.168.0.xx) 56(84) bytes of data.
^C
--- rgrock2 ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 7999ms
>From rock2:
# ping 192.168.0.x
PING 192.168.0.x (192.168.0.2) 56(84) bytes of data.
>From 192.168.0.xx icmp_seq=1 Destination Host Unreachable
>From 192.168.0.xx icmp_seq=2 Destination Host Unreachable
>From 192.168.0.xx icmp_seq=3 Destination Host Unreachable
>From 192.168.0.xx icmp_seq=4 Destination Host Unreachable
>From 192.168.0.xx icmp_seq=5 Destination Host Unreachable
>From 192.168.0.xx icmp_seq=6 Destination Host Unreachable
>From 192.168.0.xx icmp_seq=7 Destination Host Unreachable
>From 192.168.0.xx icmp_seq=8 Destination Host Unreachable
--- 192.168.0.x ping statistics ---
9 packets transmitted, 0 received, +8 errors, 100% packet loss, time 8001ms
Everything worked OK with kernel 4.5-rc7, and with 4.5 Final with the
-rc7 versions of stmmac_platform.c and stmmac_mdio.c substituted..
Robert Gadsdon. March 30, 2016
next prev parent reply other threads:[~2016-03-30 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 10:56 [PATCH] stmmac: Fix phy without MDIO subnode John Keeping
2016-03-24 12:56 ` Giuseppe CAVALLARO
2016-03-24 17:01 ` John Keeping
2016-03-25 8:42 ` Giuseppe CAVALLARO
2016-03-30 18:22 ` Robert Gadsdon [this message]
2016-03-31 7:40 ` Giuseppe CAVALLARO
2016-03-31 17:30 ` Robert Gadsdon
2016-03-24 13:00 ` Sergei Shtylyov
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=56FC1972.9050704@gmail.com \
--to=rhgadsdon@gmail.com \
--cc=gabriel.fernandez@linaro.org \
--cc=john@metanate.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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 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).