From: Sascha Hauer <s.hauer@pengutronix.de>
To: Atilla Filiz <atilla.filiz@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: How to debug Ethernet connectivity
Date: Wed, 11 Dec 2013 11:28:37 +0100 [thread overview]
Message-ID: <20131211102837.GC24559@pengutronix.de> (raw)
In-Reply-To: <CACTZKX7=ycyAhZxHsJ7k6K23HmMOsuYUVFYV8JFFmhr5=g8vyg@mail.gmail.com>
On Wed, Dec 11, 2013 at 10:39:17AM +0100, Atilla Filiz wrote:
> My problem is, /dev/phy0 never appears when I give the correct phy address.
>
> Unable to find a PHY (unknown ID?)
> dhcp failed: I/O error
> dhcp: I/O error
>
> Also, fec_probe function for fec_imx driver never gets called.
If that's the case...
> Ironically, I do not get an I/O error when I give the wrong phy
> address. Still nothing gets detected and no device node appears, but
> ethernet works(by forcing the line detect functions to return 0).
...your ethernet can't possibly work.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-12-11 10:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 10:21 Atilla Filiz
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 [this message]
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=20131211102837.GC24559@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=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