linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "robert lazarski" <robertlazarski@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 85xx Device tree problems: e0024520:02 not found
Date: Wed, 14 Nov 2007 14:18:30 -0500	[thread overview]
Message-ID: <f87675ee0711141118h3281b79dpaa49c6da7d57d891@mail.gmail.com> (raw)
In-Reply-To: <473A0A1B.3020302@anagramm.de>

On Nov 13, 2007 3:33 PM, Clemens Koller <clemens.koller@anagramm.de> wrote:
> robert lazarski schrieb:
>  > Hi all,
>  >
>  > I'm trying to bring up a new 8548 board on 2.6.23.1 . When booting,
>  > Some times I can get as far mounting over nfs. However, it gets stuck
>  > here:
>  >
>  > NET: Registered protocol family 1
>  > NET: Registered protocol family 17
>  > e0024520:02 not found
>  > eth2: Could not attach to PHY
>  > IP-Config: Failed to open eth2
>  > IP-Config: Device `eth2' not found.
>
> As already written in the u-boot-users list,
> you could give the pauilis.git tree a try.
>
> There have been recently (last month) several
> PHY related changes. 2.6.23.1 seems to be too
> "old".
>

I'm now running pauilis.git and 2.6.24rc2, along with a new custom
board. I still can't attach to the phy though. I know the phy works
because it works fine in u-boot. Clemens, IIRC you are using the
88e1111 - is that with the gianfar driver? I'm having problems getting
soft reboot to work with pauilis.git from some reason so debugging is
slow going - might someone have some hints?

Thanks,
Robert

  reply	other threads:[~2007-11-14 19:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 20:17 85xx Device tree problems: e0024520:02 not found robert lazarski
2007-11-13 20:33 ` Clemens Koller
2007-11-14 19:18   ` robert lazarski [this message]
2007-11-14 19:37     ` Clemens Koller
2007-11-14 20:23     ` Clemens Koller
2007-11-14 21:33       ` Clemens Koller
2007-11-14 22:00         ` robert lazarski

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=f87675ee0711141118h3281b79dpaa49c6da7d57d891@mail.gmail.com \
    --to=robertlazarski@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).