From: Adrian Cox <adrian@humboldt.co.uk>
To: Paul Mackerras <paulus@samba.org>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH][2.4.27] PowerPC 745x data corruption bug fix
Date: Mon, 16 Aug 2004 10:15:39 +0100 [thread overview]
Message-ID: <1092647739.959.63.camel@localhost> (raw)
In-Reply-To: <16672.30991.27709.349218@cargo.ozlabs.ibm.com>
On Mon, 2004-08-16 at 10:06, Paul Mackerras wrote:
> Adrian Cox writes:
>
> > Pages should be marked coherent for the MPC106 as well as the MPC107,
> The MPC106 has an internal cache? I had a quick look in the 106 and
> 107 manuals and I couldn't see in either one where it talks about a
> cache. Do you know where I should be looking?
MPC106UM, section 8.1.3.1: PCI to System Memory Read Buffer (PCMRB)
MPC107UM, section 12.1.3.1.1: PCI to Local Memory Read Buffer (PCMRB)
It's not a big cache, but it's large enough to hold the transmit
descriptor of a pcnet32 ethernet. It's easy to miss this in the manual,
and I only noticed it when my first 7450 board wouldn't work with NFS
root.
- Adrian Cox
Humboldt Solutions Ltd.
next prev parent reply other threads:[~2004-08-16 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 2:54 [PATCH][2.4.27] PowerPC 745x data corruption bug fix Mikael Pettersson
2004-08-16 7:40 ` Adrian Cox
2004-08-16 9:06 ` Paul Mackerras
2004-08-16 9:15 ` Adrian Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-16 10:04 Mikael Pettersson
2004-08-16 17:05 ` Tom Rini
2004-08-18 11:10 ` 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=1092647739.959.63.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 \
/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.