From: Jos Beck <jos_beck@euronet.nl>
To: Dan Malek <dan@embeddededge.com>, linuxppc-embedded@lists.linuxppc.org
Subject: FCC Ethernet MDIO interface
Date: Fri, 16 Apr 2004 08:54:10 +0200 [thread overview]
Message-ID: <407F8312.3070702@euronet.nl> (raw)
In-Reply-To: <407DEC4A.3080305@embeddededge.com>
Dear Dan,
We are trying to use U-boot for a new MPC8250 circuit.
When looking at cpu/mpc8260/ether_fcc.c I cannot find any reference to
the control of the MDC and MDIO lines of the MII interface to the PHY.
Where can I find the code that controls MDIO? (e.g. to defive which CPM
pins are used)
Is the MDIO interface used/supported anyhow in u-boot or the kernel?
Best Regards,
Jos Beck
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-16 6:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 20:54 Slow down with recent linux kernel Richard Laing
2004-04-15 1:58 ` Dan Malek
2004-04-16 6:54 ` Jos Beck [this message]
2004-04-16 13:00 ` FCC Ethernet MDIO interface Dan Malek
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=407F8312.3070702@euronet.nl \
--to=jos_beck@euronet.nl \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.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).