From: Dan Malek <dan@mvista.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Erratum 51 bugfix?
Date: Mon, 17 Sep 2001 12:32:03 -0400 [thread overview]
Message-ID: <3BA62583.55E48A97@mvista.com> (raw)
In-Reply-To: 20010917152316.O3851@zax
David Gibson wrote:
>
> According to the ppc405gp errata, the workaround for erratum 51 is
> incorrect.
Got it, thanks. I actually went to read the 4xx errata this time instead
of just blindly accepting the patch as I did last time. There are some
other nasty things we should consider fixing. The worst is #67, and now
they have told us about #77 so we can fix up the ATOMIC_SYNC_FIX....
Of all the errata, #77 is the only one we have seen with Linux. I guess
you could force #51 to occur, but whether you call ITLBmiss or DTLBmiss
probably doesn't matter because they end up at the same place. We are
somewhat lucky with #67 because I don't think we have mapping situations
where this can occur. Although, some days I read it and think otherwise.....
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-17 16:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 5:23 Erratum 51 bugfix? David Gibson
2001-09-17 16:32 ` Dan Malek [this message]
2001-09-18 0:29 ` Errata 67/77 / walnut bugs (was: Re: Erratum 51 bugfix?) David Gibson
2001-09-18 18:52 ` Dan Malek
2001-09-19 2:19 ` David Gibson
2001-09-19 2:23 ` Mark Hatle
2001-09-19 6:41 ` Dan Malek
2001-09-19 10:45 ` Ralph Blach
2001-09-19 6:39 ` Dan Malek
2001-09-21 4:36 ` David Gibson
2001-09-21 5:23 ` Dan Malek
2001-09-21 5:33 ` David Gibson
2001-09-21 6:24 ` Dan Malek
2001-09-21 8:04 ` 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=3BA62583.55E48A97@mvista.com \
--to=dan@mvista.com \
--cc=david@gibson.dropbear.id.au \
--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 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.