From: Ken MacLeod <ken@bitsko.slc.ut.us>
To: linuxppc-dev@lists.ozlabs.org
Cc: Vitaly Bordug <vbordug@ru.mvista.com>
Subject: fs_enet/mac-fcc: RMII, 10Mb Ethernet not clocking right
Date: Tue, 4 May 2010 11:48:30 -0500 [thread overview]
Message-ID: <o2u7ee95fff1005040948s29c5113el18d43c4a59045621@mail.gmail.com> (raw)
Short version:
Can anyone confirm 10Mb Ethernet works with fs_enet/mac-fcc? with
RMII? with a KS8721 PHY?
Long version:
I have an MPC8247 connected via an externally clocked RMII to a Micrel
KS8721 PHY using the Generic PHY driver, running either MontaVista
2.6.18+ or mainline 2.6.30 (I don't see any relevant changes up to
current mainline). 100Mb Ethernet works fine.
When I use a 10Mb hub (not switch), the PHY registers, mii-tool, and
ethtool all report 10baseT-HD, no autonegotiation. mac-fcc, restart()
sets the FCC GFEMR CLK bit and clears the FCC FPSMR FDE and LPB bits
(the FCC FPSMR RMII bit is set in all cases).
>From that perspective, it looks like everything is set up correctly to
work at 10Mb. However, no outgoing packets are received by other
hosts and I see a 1:1 count of incoming errors for the ARP requests
sent by my other host (frame errors, reported as RxBD[NO] nonoctet
aligned errors).
When I connect a scope to the transmit line, I'm seeing the same
timing for both 10Mb and 100Mb. I would have expected the 10Mb to be
10x longer.
The MPC8272 Reference Manual is confusing on this point, for the FCC
GFEMR CLK field it says "RMII reference clock rate for 50-MHz input
clock from external oscillator (Ethernet mode): 0 == 50MHz (for Fast
Ethernet), 1 == 5MHz (for 10BaseT)" The RMII spec and the KS8721
datasheet both say REF_CLK should be 50MHz at all times, but I don't
see anything other than the CLK bit to indicate 10Mb cycle timing for
the RMII.
Am I missing something? What next to try?
Thanks,
-- Ken
reply other threads:[~2010-05-04 16:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=o2u7ee95fff1005040948s29c5113el18d43c4a59045621@mail.gmail.com \
--to=ken@bitsko.slc.ut.us \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=vbordug@ru.mvista.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).