From: Atilla Filiz <atilla.filiz@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: How to debug Ethernet connectivity
Date: Wed, 11 Dec 2013 10:39:17 +0100 [thread overview]
Message-ID: <CACTZKX7=ycyAhZxHsJ7k6K23HmMOsuYUVFYV8JFFmhr5=g8vyg@mail.gmail.com> (raw)
In-Reply-To: <20131210174536.GA7305@omega>
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.
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).
I will talk to the hardware guys to verify the pin muxing and phy address.
On Tue, Dec 10, 2013 at 6:46 PM, Alexander Aring <alex.aring@gmail.com> wrote:
> On Tue, Dec 10, 2013 at 07:24:40PM +0400, Antony Pavlov wrote:
>> On Tue, 10 Dec 2013 14:31:23 +0100
>> Atilla Filiz <atilla.filiz@gmail.com> wrote:
>>
>> > Ok, then my problem is slightly more clear, that /dev/phy0 does not exist.
>> > I do define a struct fec_platform_data with
>> > xcv_type=PHY_INTERFACE_MODE_MII and register it via imx27_add_fec().
>> >
>> > Now I need to find out why it fails to register the device.
>>
>> There is issue with current barebox.
>>
>> The /dev/phy0 device is unavailable till you use network.
>> You can use this (ugly!) way
>> So just after boot type 'dhcp', next type 'ctrl-c' to interrupt dhcp and check /dev/phy0 presence.
>>
> mh, bad... :( Maybe just try a ping instead of dhcp to bring /dev/phy0
> alive. But that's a ugly hack, too.
>
> Is there no some global(var/env) to enable it?
>
> - Alex
--
Atilla Filiz
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-12-11 9:40 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 [this message]
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='CACTZKX7=ycyAhZxHsJ7k6K23HmMOsuYUVFYV8JFFmhr5=g8vyg@mail.gmail.com' \
--to=atilla.filiz@gmail.com \
--cc=alex.aring@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