From: Dan Malek <dan@mvista.com>
To: Kevin Fry <kevin@carts.com>
Cc: linuxppc emb3dd3d list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 8260 Communications Proccessor overload??
Date: Wed, 10 Oct 2001 14:02:49 -0400 [thread overview]
Message-ID: <3BC48D49.6FB5279@mvista.com> (raw)
In-Reply-To: 3BC3BC07.D6158215@carts.com
Kevin Fry wrote:
>
> Has anyone ever run all 3 FCC ports at the same time with a
> 100Mbit link?
Yeah.....
> .... I think I'm seeing the Communications Processor get
> overloaded, but Motorola claims there is no problem.
What clock speeds are you running? Are they full or half duplex
connections?
> the Ethernet PHY (AM79C874) indicates no errors, but the MAC is
> reporting
> CRC errors.
Hmmm...Do you ever see any buffering problems on the Linux driver
side, like the CPU can't keep up with the data?
> .... I have captured the MAC --> PHY transfers on a logic
> analyzer
> and am decoding them at present (I hate computing a CRC-32 by hand). I
> was
> hoping someone else has experience relative to this situation.
I have seen some noise problems with some boards between the MAC and
PHY. Some crappy looking layouts worked great, some really pretty
ones had trouble :-). I don't know if this would be represented as
a CRC error or something else.
Good Luck! Keep us posted :-).
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-10 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 3:09 8260 Communications Proccessor overload?? Kevin Fry
2001-10-10 18:02 ` Dan Malek [this message]
2001-10-11 18:11 ` Trevor Coolidge
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=3BC48D49.6FB5279@mvista.com \
--to=dan@mvista.com \
--cc=kevin@carts.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).