linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Russell McGuire" <rmcguire@videopresence.com>
To: "'Jochen Friedrich'" <jochen@scram.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: 83xx, ucc_geth, kernel 2.6.23, IP-Config: No network devices
Date: Mon, 7 Jan 2008 04:59:52 -0800	[thread overview]
Message-ID: <000401c8512d$3b9d93a0$6405a8c0@absolut> (raw)
In-Reply-To: <47820A60.2040500@scram.de>

Joch,

Thanks, apparently I had a conditional that was not matching up around that
call. So now that I 'am' calling the of_platform_bus_probe(). I can see all
the probe functions getting called.  Thank you very much.

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.

BootLog:

RWM DEBUG, uec_mdio_init:278
RWM DEBUG, uec_mdio_probe:145
UCC Ethernet Controller MII Bus: probed
UCC Ethernet Controller MII Bus: Registered
ucc_geth: QE UCC Gigabit Ethernet Controller
Marvell 88E1101: Registered new driver
Marvell 88E1112: Registered new driver
Marvell 88E1111: Registered new driver
RWM DEBUG: phy_probe:635
RWM DEBUG: phy_probe:663 err = 0
National DP83865: Registered new driver
Marvell 88E1145: Registered new driver
HDLC support module revision 1.21
usbmon: debugfs is not available
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
WDT driver for MPC83xx initialized. mode:reset timeout=65535 (16 seconds)
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
lec.c: Dec 18 2007 15:30:33 initialized
mpc.c: Dec 18 2007 15:30:31 initialized
IP-Config: No network devices available.
.... NFS boot fails

-Russ
> -----Original Message-----
> From: Jochen Friedrich [mailto:jochen@scram.de]
> Sent: Monday, January 07, 2008 3:18 AM
> To: rmcguire@videopresence.com
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: 83xx, ucc_geth, kernel 2.6.23, IP-Config: No network devices
> 
> Hi Russell,
> 
> > I would appear all the appropriate entries are in the .dts file
> > for each the different parts (mdio, ucc_geth, ucc_geth_mdio, phy0).
> >
> > And yet still no probe functions get called for any of those drivers?
> 
> Do you export the subtree using of_platform_bus_probe()?
> 
> Thanks,
> Jochen

  reply	other threads:[~2008-01-07 13:00 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 [this message]
2008-01-07 13:52           ` Jochen Friedrich

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='000401c8512d$3b9d93a0$6405a8c0@absolut' \
    --to=rmcguire@videopresence.com \
    --cc=jochen@scram.de \
    --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).