From: DENX Support System <support@denx.de>
To: u-boot@lists.denx.de
Subject: [DNX#2006040142001392] [U-Boot-Users] Re: Re: Rx-buffer overlow
Date: Sat, 1 Apr 2006 02:00:09 +0200 [thread overview]
Message-ID: <1143849609.396277.791018962@castor.denx.de> (raw)
Hello list,
inside the automatic U-Boot patch tracking system a new ticket
[DNX#2006040142001392] was created:
<snip>
>
> > 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
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
</snip>
Your U-Boot support team
reply other threads:[~2006-04-01 0:00 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=1143849609.396277.791018962@castor.denx.de \
--to=support@denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.