linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jochen Friedrich <jochen@scram.de>
To: rmcguire@videopresence.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 83xx, ucc_geth, kernel 2.6.23, IP-Config: No network devices
Date: Mon, 07 Jan 2008 14:52:47 +0100	[thread overview]
Message-ID: <47822EAF.1000803@scram.de> (raw)
In-Reply-To: <000401c8512d$3b9d93a0$6405a8c0@absolut>

Hi Russell,

> Next question, I can see that 'quick' mods I have made to the Marvell driver
> are indeed matching up with the device ID that the Freescale MII device is
> pulling back from my 'National' part. <I'll make a real phy driver once I
> get this working>. I.e. I can see the phy_probe get called when this Id is
> registered.  You can see the extra debug messages above the National DP83865
> device registration, and the probe returns 0 for success I assume. <err =
> 0>.
> 
> I am still getting the "IP-Config: No network devices" error before the NFS
> boot tries to take place.

I would add some more debugging printk output to check where the device
initialisation fails. Or if the phy runs without any initialisation, you
could use the fixed-phy patches from Vitali Bordug and hardcode the speed and
duplex settings in the device tree until you real phy driver is finished.

thanks,
Jochen

      reply	other threads:[~2008-01-07 13:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1198890002.24584.linuxppc-embedded@ozlabs.org>
2007-12-31  0:51 ` 83xx, ELDK 2.6.23, IP-Config: No network devices Russell McGuire
2007-12-31  8:14   ` Vitaly Bordug
2008-01-07 10:54     ` 83xx, ucc_geth, kernel " Russell McGuire
2008-01-07 11:17       ` Jochen Friedrich
2008-01-07 12:59         ` Russell McGuire
2008-01-07 13:52           ` Jochen Friedrich [this message]

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=47822EAF.1000803@scram.de \
    --to=jochen@scram.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rmcguire@videopresence.com \
    /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).