From: Adrian Cox <adrian@humboldt.co.uk>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org,
paulus@samba.org
Subject: Re: [PATCH][2.4.27] PowerPC 745x data corruption bug fix
Date: Wed, 18 Aug 2004 12:10:48 +0100 [thread overview]
Message-ID: <1092827448.10314.10.camel@localhost> (raw)
In-Reply-To: <20040816170534.GA7303@smtp.west.cox.net>
On Mon, 2004-08-16 at 18:05, Tom Rini wrote:
> On Mon, Aug 16, 2004 at 12:04:08PM +0200, Mikael Pettersson wrote:
> > So previously a CPU got _PAGE_COHERENT on SMP.
> > Now a CPU gets _PAGE_COHERENT on (SMP || 745x).
> >
> > I suspect the CONFIG_MPC10X_BRIDGE is an attempt to enable
> > the fix in some other cases too.
>
> The reason CPU_FTR_NEED_COHERENT was added was to work around an MPC107
> (now Tsi107) errata. See
> http://216.239.57.104/search?q=cache:1MDn1X8ieUUJ:www.geocrawler.com/archives/3/8358/2002/9/100/9559482/+%22Adrian+Cox%22+errata&hl=en
> (original is conn refused right now).
I've now written some notes to explain these issues, in case it comes up
again:
http://www.humboldt.co.uk/Notes/mpc107cache.html
- Adrian Cox
Humboldt Solutions Ltd.
next prev parent reply other threads:[~2004-08-18 11:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 10:04 [PATCH][2.4.27] PowerPC 745x data corruption bug fix Mikael Pettersson
2004-08-16 17:05 ` Tom Rini
2004-08-18 11:10 ` Adrian Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-16 2:54 Mikael Pettersson
2004-08-16 7:40 ` Adrian Cox
2004-08-16 9:06 ` Paul Mackerras
2004-08-16 9:15 ` Adrian Cox
2004-08-15 11:16 Mikael Pettersson
2004-08-15 22:13 ` Paul Mackerras
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=1092827448.10314.10.camel@localhost \
--to=adrian@humboldt.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mikpe@csd.uu.se \
--cc=paulus@samba.org \
--cc=trini@kernel.crashing.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 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).