From: "Russell McGuire" <rmcguire@videopresence.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: 83xx, ELDK 2.6.23, IP-Config: No network devices
Date: Sun, 30 Dec 2007 16:51:44 -0800 [thread overview]
Message-ID: <000001c84b47$50b0e2b0$6405a8c0@absolut> (raw)
In-Reply-To: <mailman.1.1198890002.24584.linuxppc-embedded@ozlabs.org>
All,
Attempting to get MPC8360 board booted into Linux using a NFS root fs.
I can see the kernel boots up, and registers both the MDIO driver and the
ucc_geth: driver, and with additional debug they encounter no errors.
However, for some reason the probe function never gets called for the MDIO
or the UCC driver. So as a result <assuming> the IP layer never gets a
network device. I am using a National DP83865 PHY device connected directly
to the 83xx QE. I don't see any direct definition for this PHY device, but
it doesn't even look like it queries the ID.
So two questions:
1) Is there some basic kernel feature I am missing? I have enabled the GIGE
UEC GETH driver in the kernel. Perhaps a PHY LIB? Isn't generic MII
supported by default?
2) Is there something in the startup board files, that I need to add to
register my PHY like an of_put_node()? Again I have pretty much copied the
MPC8360E MDS board and it is starting, and defining the par_io port already,
except that my PHY ID <on the iC2 bus, is using dev ID 0x01>. However, I
don't see the probe function being called, so I don't think this is a
concern yet.
Anyway, how do I get the UEC_driver to see my phy device so I can get the
NFS to boot?
-Russ
next parent reply other threads:[~2007-12-31 0:52 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 ` Russell McGuire [this message]
2007-12-31 8:14 ` 83xx, ELDK 2.6.23, IP-Config: No network devices 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
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='000001c84b47$50b0e2b0$6405a8c0@absolut' \
--to=rmcguire@videopresence.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).