From: Vitaly Bordug <vitb@kernel.crashing.org>
To: rmcguire@videopresence.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 83xx, ELDK 2.6.23, IP-Config: No network devices
Date: Mon, 31 Dec 2007 11:14:43 +0300 [thread overview]
Message-ID: <20071231111443.4c6d8691@kernel.crashing.org> (raw)
In-Reply-To: <000001c84b47$50b0e2b0$6405a8c0@absolut>
On Sun, 30 Dec 2007 16:51:44 -0800
Russell McGuire wrote:
> 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?
>
yes you will need phylib
> 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.
I think you will need to write a driver for your specific PHY access to get it covered by phy abstraction layer.
Generic mii thing is useful when it has access to phy regs somehow (live examples are some BCM phys that do not have specs
available but the thing works using generic mii and standard phy regs).
--
Sincerely, Vitaly
next prev parent reply other threads:[~2007-12-31 8:14 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 [this message]
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=20071231111443.4c6d8691@kernel.crashing.org \
--to=vitb@kernel.crashing.org \
--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).