From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: barebox@lists.infradead.org
Subject: Fwd: Micrel KSZ9031RN PHY problem
Date: Mon, 18 Apr 2016 16:49:47 +0200 [thread overview]
Message-ID: <CABDcavZZd4AofsfSYMVbEPfjpPyF9rbmv6BXAG_8mLiJhmeL+Q@mail.gmail.com> (raw)
In-Reply-To: <CABDcavZr1PCpFrHVJFFayRQZ6vninf-xFS0H9QKSdA8u53OkDg@mail.gmail.com>
Hello all,
I am playing with barebox on an Atmel SAMA5D3 Xplained board. It is
now working fine for the most part, however after updating to the
latest sources from git I found a problem that I had not seen before.
This board has two Ethernet interfaces; eth0 uses a Micrel KSZ9031RN
PHY, and eth1 uses a Micrel KSZ8081RNB PHY.
It seems that after release 2016.03.0, eth0 does not work anymore with
some routers. Specifically I found this problem with a Comtrend
VG-8050. I have tested other routers and the problem was not present
there.
After some research it seems that the problem is caused by this
commit: http://git.pengutronix.de/?p=barebox.git;a=commit;h=da89ee8f2e04e116410632a185024f58b8262d87
Before this commit eth0 was working fine. After this commit, the link
cannot established anymore:
[...]
barebox:/# ping 192.168.0.128
ping failed: Network is down
Before diving further into this I thought it could be a good idea to
ask, in case someone can shed some light here.
Any feedback is welcome.
Best,
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next parent reply other threads:[~2016-04-18 14:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABDcavZr1PCpFrHVJFFayRQZ6vninf-xFS0H9QKSdA8u53OkDg@mail.gmail.com>
2016-04-18 14:49 ` Guillermo Rodriguez Garcia [this message]
2016-04-19 7:11 ` Sascha Hauer
2016-04-20 15:58 ` Guillermo Rodriguez Garcia
2016-04-21 7:32 ` Sascha Hauer
2016-04-21 11:04 ` Guillermo Rodriguez Garcia
2016-04-26 9:55 ` Guillermo Rodriguez Garcia
2016-04-26 11:10 ` Guillermo Rodriguez Garcia
2016-04-27 5:59 ` Sascha Hauer
2016-04-28 9:51 ` Guillermo Rodriguez Garcia
2016-04-28 21:09 ` Trent Piepho
2016-04-29 11:00 ` Guillermo Rodriguez Garcia
2016-04-29 18:18 ` Trent Piepho
2016-05-03 14:40 ` Guillermo Rodriguez Garcia
2016-05-04 7:43 ` Sascha Hauer
2016-05-04 10:39 ` Guillermo Rodriguez Garcia
2016-06-13 17:29 ` [PATCH] Fix genphy_restart_aneg() for Micrel's ksz9031 Guillermo Rodriguez Garcia
2016-06-14 6:39 ` Sascha Hauer
2016-06-14 7:39 ` Guillermo Rodriguez Garcia
2016-06-15 5:49 ` Sascha Hauer
2016-06-15 7:44 ` Guillermo Rodriguez Garcia
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=CABDcavZZd4AofsfSYMVbEPfjpPyF9rbmv6BXAG_8mLiJhmeL+Q@mail.gmail.com \
--to=guille.rodriguez@gmail.com \
--cc=barebox@lists.infradead.org \
/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