From: Atilla Filiz <atilla.filiz@gmail.com>
To: barebox@lists.infradead.org
Subject: How to debug Ethernet connectivity
Date: Fri, 6 Dec 2013 11:21:25 +0100 [thread overview]
Message-ID: <CACTZKX4PZ1NKB=4am7hik-w6V+CXApDHbEcAAmp6PakXGK5V0A@mail.gmail.com> (raw)
Hello
I have been tasked to debug a port of Barebox to our custom board. It
has one Ethernet interface. All network related(dhcp, ping ...) tasks
fail with "Network is down" error, although the link lights on my
switch are on. So I did this on 2013.06:
--- barebox-2013.06.0.orig/net/
eth.c 2013-06-02 12:24:06.000000000 +0200
+++ barebox-2013.06.0/net/eth.c 2013-12-03 16:52:40.428089000 +0100
@@ -142,12 +142,16 @@
if (force || is_timeout(last_link_check, 5 * SECOND) ||
!eth_current->phydev->link) {
ret = phy_update_status(eth_current->phydev);
if (ret)
return ret;
last_link_check = get_time_ns();
}
+ return 0;
return eth_current->phydev->link ? 0 : -ENETDOWN;
}
This bypasses link detection and assumes the link is always up. This
way, I got dhcp, ping and tftp working.
How can I debug this further to hunt down the Ethernet problem?
Something seems wrong with my PHY settings. This is an iMX27 based
board. Which files/functions/structures do I need to check?
--
Atilla Filiz
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2013-12-06 10:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 10:21 Atilla Filiz [this message]
2013-12-06 10:34 ` Sascha Hauer
2013-12-06 10:52 ` Antony Pavlov
2013-12-06 12:17 ` Atilla Filiz
2013-12-06 12:18 ` Atilla Filiz
2013-12-06 12:21 ` Alexander Aring
2013-12-06 12:39 ` Sascha Hauer
2013-12-06 12:43 ` Alexander Aring
2013-12-10 13:31 ` Atilla Filiz
2013-12-10 15:24 ` Antony Pavlov
2013-12-10 17:46 ` Alexander Aring
2013-12-11 9:39 ` Atilla Filiz
2013-12-11 10:28 ` Sascha Hauer
2013-12-10 15:30 ` Antony Pavlov
2013-12-11 10:25 ` Sascha Hauer
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='CACTZKX4PZ1NKB=4am7hik-w6V+CXApDHbEcAAmp6PakXGK5V0A@mail.gmail.com' \
--to=atilla.filiz@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