From: Josef Angermeier <Josef.Angermeier@informatik.stud.uni-erlangen.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Re: Rx-buffer overlow
Date: Tue, 28 Feb 2006 09:56:06 +0100 [thread overview]
Message-ID: <20060228085606.GB4849@false> (raw)
In-Reply-To: <20060228084306.AEAC813590@sc8-sf-spam2.sourceforge.net>
> In message <20060228081735.GA4849@false> you wrote:
> >=20
> > fec_recv[249] err: 802
> > fec_recv[249] err: 2802
> > fec_recv[249] err: 802
> >=20
> > According to the Rx-buffer-status bits, an overlow takes place. So ping
> > just works if there is less network traffic. But why ? - is the receiv=
> e
> > buffer to small, the CPU to slow ?=20
> At which clock frequency are you running your CPU?
the MPC875 is running at 40MHz!
Btw, ethernet just works in 10MB half duplex mode (probably failure in
hardware). Maybe this is also related to that problem!
U-Boot 1.1.3 (Feb 28 2006 - 09:27:50)
CPU: MPC885ZPnn at 40 MHz [40.0...50.0 MHz]
8 kB I-Cache 8 kB D-Cache FEC present
You made sure it's an ESM this is running on, right?
DRAM: 64 MB
FLASH: 16 MB
In: serial
Out: serial
Err: serial
Net: FEC ETHERNET
> Best regards,
> Wolfgang Denk
Best regards,
Josef
parent reply other threads:[~2006-02-28 8:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20060228084306.AEAC813590@sc8-sf-spam2.sourceforge.net>]
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=20060228085606.GB4849@false \
--to=josef.angermeier@informatik.stud.uni-erlangen.de \
--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