From: Frank Rowand <frank_rowand@mvista.com>
To: Dan Malek <dan@mvista.com>
Cc: Matthias Fuchs <matthias.fuchs@esd-electronics.com>,
linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>,
frank@esd-electronics.com
Subject: Re: possible problem in memory management
Date: Wed, 21 Mar 2001 14:03:58 -0800 [thread overview]
Message-ID: <3AB9254E.FE13F585@mvista.com> (raw)
In-Reply-To: 3AB9148A.7F25E9A0@mvista.com
Dan Malek wrote:
>
> Matthias Fuchs wrote:
>
> > CPU: IBM PowerPC 405GP Rev. C at 198 MHz (PLB=99, OPB=49, EBC=33 MHz)
>
> Get yourself an up to date Rev. D CPU. The Rev. C workarounds in
> the kernel were reasonable attempts, but probably aren't complete.
Dan is correct. We did not do an exhaustive scan of the kernel to add
workarounds in all places they might be necesary, just enough to make the
kernel fairly stable and usable. Even in the places where the workarounds
are in place, they are not guaranteed to be 100% effective.
> Since the Rev. D fixes all of these problems, we stopped debugging
> all of the little Rev. C problems because they were just too time
> consuming.
>
> You also need specially patched user libraries for anything older
> than Rev. D, and you can't use these patches libraries on Rev. D,
> so we stopped supporting that as well and simply suggest (require)
> the upgrade to the working Rev. D silicon.
>
> -- Dan
-Frank
--
Frank Rowand <frank_rowand@mvista.com>
MontaVista Software, Inc
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-21 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 14:20 possible problem in memory management Matthias Fuchs
2001-03-21 20:52 ` Dan Malek
2001-03-21 22:03 ` Frank Rowand [this message]
2001-03-22 9:50 ` Kenneth Johansson
2001-03-22 16:13 ` Dan Malek
2001-03-22 18:02 ` Kenneth Johansson
2001-03-22 18:25 ` Inquiry : ECC on embedded system David Chiu
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=3AB9254E.FE13F585@mvista.com \
--to=frank_rowand@mvista.com \
--cc=dan@mvista.com \
--cc=frank@esd-electronics.com \
--cc=frowand@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=matthias.fuchs@esd-electronics.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 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.