mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Atilla Filiz <atilla.filiz@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: How to debug Ethernet connectivity
Date: Tue, 10 Dec 2013 19:24:40 +0400	[thread overview]
Message-ID: <20131210192440.cbffc0bed7dd71d3f0e36f79@gmail.com> (raw)
In-Reply-To: <CACTZKX6kectn-z1NUJFjb=ycM9NTFuVUKmb8xU80k4wbp6DKqA@mail.gmail.com>

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.

> 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


-- 
-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-12-10 15:17 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 [this message]
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=20131210192440.cbffc0bed7dd71d3f0e36f79@gmail.com \
    --to=antonynpavlov@gmail.com \
    --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