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: Tue, 10 Dec 2013 14:31:23 +0100 [thread overview]
Message-ID: <CACTZKX6kectn-z1NUJFjb=ycM9NTFuVUKmb8xU80k4wbp6DKqA@mail.gmail.com> (raw)
In-Reply-To: <20131206124327.GA22853@omega>
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.
On Fri, Dec 6, 2013 at 1:43 PM, Alexander Aring <alex.aring@gmail.com> wrote:
> On Fri, Dec 06, 2013 at 01:39:25PM +0100, Sascha Hauer wrote:
>> On Fri, Dec 06, 2013 at 01:18:52PM +0100, Atilla Filiz wrote:
>> > Sorry, figured it out. Just most verbose output is funny as well:
>> > :/ miitool -vvv /dev/mc13xxx
>>
>> Don't know what miitool does in this case, but mc13xxx is not your phy,
>> it's your PMIC.
>>
>
> oh, doesn't realize that :D. So reading zeros can make sense in some
> offset. :-)
>
> - 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-10 13:32 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 [this message]
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='CACTZKX6kectn-z1NUJFjb=ycM9NTFuVUKmb8xU80k4wbp6DKqA@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