From: Pantelis Antoniou <panto@intracom.gr>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [patch #5/11] FEC driver update for 8xx
Date: Tue, 30 Mar 2004 17:48:31 +0300 [thread overview]
Message-ID: <406988BF.7090105@intracom.gr> (raw)
Hello
The following patch improves and fixes various things
in the FEC driver on the 8xx series of processors.
The changes are as following:
1. The new 87x and 88x series of processors have two FECs,
and the new driver supports them both.
2. Another change in the 87x/88x series is support for
the RMII (Reduced MII) interface. However numerous
changes are needed to make it work since the PHYs
are connected to the same lines. That means that
you have to address them correctly over the MII
interface.
3. We now correctly match the MII/RMII interface
configuration to what the PHY reports.
The following new defines are supported:
CONFIG_ETHER_ON_FEC[12]
Enable FEC on given FEC
CONFIG_FEC[12]_PHY
Assign PHY address to FEC. If -1 means probe.
CONFIG_FEC[12]_PHY_NORXERR
The PHY does not have a RXERR line (RMII only).
CONFIG_RMII
Enable RMII mode common for any activated FECs.
For compatibility reasons the name of the first
interface remains unchanged at 'FEC ETHERNET' while
the second is name 'FEC2 ETHERNET'.
Regards
Pantelis
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: fec.diffstat
Url: http://lists.denx.de/pipermail/u-boot/attachments/20040330/9f102327/attachment.txt
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: fec.diff
Url: http://lists.denx.de/pipermail/u-boot/attachments/20040330/9f102327/attachment-0001.txt
next reply other threads:[~2004-03-30 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 14:48 Pantelis Antoniou [this message]
2004-04-15 21:32 ` [U-Boot-Users] Re: [patch #5/11] FEC driver update for 8xx Wolfgang Denk
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=406988BF.7090105@intracom.gr \
--to=panto@intracom.gr \
--cc=u-boot@lists.denx.de \
/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