From: Wolfgang Denk <wd@denx.de>
To: Dan Malek <dan@embeddededge.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Kernel Mode Software Emulation NIP: 00001FFC - cache coherency problem on m8xx processors
Date: Fri, 26 Mar 2004 10:04:16 +0100 [thread overview]
Message-ID: <20040326090421.B103EC118A@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 26 Mar 2004 01:51:44 EST." <4063D300.2060006@embeddededge.com>
In message <4063D300.2060006@embeddededge.com> Dan Malek wrote:
>
> Let's put a big comment around this. Indicate it was a problem for one
> person with an 855T. I don't have any 855T parts, if anyone else has
> some and can do some heavy network testing, I'd appreciate knowing the
Can you define which sort of network load is suitable to sfficiently
stress the system? We ave many kinds of systems of all types in the
lab, and I can easily run such a test.
But I actually doubt that we would see any problem, as we perform
such testing on a regular base, and never had any such problems on
8xx systems.
> results. Like I keep saying, I've seen similar problems on the 860T
> parts, but it was clearly my fault programming the UPM. Once that was
> fixed, problem solved.
I agree 100%.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Quantum Mechanics is God's version of "Trust me."
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-26 9:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 23:13 Kernel Mode Software Emulation NIP: 00001FFC - cache coherency problem on m8xx processors Marcelo Tosatti
2004-03-26 6:51 ` Dan Malek
2004-03-26 9:04 ` Wolfgang Denk [this message]
2004-03-26 13:44 ` Dan Malek
2004-03-26 7:23 ` LC Geldenhuys
2004-03-26 8:07 ` Dan Malek
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=20040326090421.B103EC118A@atlas.denx.de \
--to=wd@denx.de \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=marcelo.tosatti@cyclades.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).