From: Ben Menchaca <ben.menchaca@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Liu Dave-R63238 <DaveLiu@freescale.com>
Subject: Re: 83xx: Marking or Allocating Pages as Cache-Inhibited
Date: Sat, 7 Mar 2009 21:15:13 -0600 [thread overview]
Message-ID: <64ac01180903071915lf27669fq813a5e3842c0c2a1@mail.gmail.com> (raw)
In-Reply-To: <1236462686.7260.161.camel@pasglop>
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
On Sat, Mar 7, 2009 at 3:51 PM, Benjamin Herrenschmidt <
benh@kernel.crashing.org> wrote:
> On Fri, 2009-03-06 at 10:12 -0600, Ben Menchaca wrote:
> > Testing now...it looks like it (almost) works, though! Why does
> > setting no-snoop cause snooping to work? More on the effect on
> > setting that bit in a few minutes...need more testing.
>
> Maybe they got the documentation for that bit backward ? :-)
For posterity...it does appear that this is the case. I don't have a bus
analyzer to watch the transaction, but a JTAG trigger caught the update
happening if and only if bit 3 was set in the (R|W)DMA descriptor. My FAE
at FS said he is watching this thread, so hopefully some doc errata can be
generated so others can avoid my confusion :-).
- Ben
[-- Attachment #2: Type: text/html, Size: 1091 bytes --]
next prev parent reply other threads:[~2009-03-08 3:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 4:32 83xx: Marking or Allocating Pages as Cache-Inhibited Ben Menchaca
2009-03-06 5:22 ` Liu Dave-R63238
2009-03-06 5:27 ` Liu Dave-R63238
2009-03-06 5:38 ` Ben Menchaca
2009-03-06 5:40 ` Liu Dave-R63238
2009-03-06 6:10 ` Ben Menchaca
2009-03-06 6:30 ` Liu Dave-R63238
2009-03-06 16:12 ` Ben Menchaca
2009-03-06 16:30 ` Ben Menchaca
2009-03-09 2:30 ` Liu Dave-R63238
2009-03-09 2:56 ` Liu Dave-R63238
2009-03-09 3:27 ` Ben Menchaca
2009-03-07 21:51 ` Benjamin Herrenschmidt
2009-03-08 3:15 ` Ben Menchaca [this message]
2009-03-06 5:49 ` Liu Dave-R63238
2009-03-08 15:19 ` Timur Tabi
2009-03-09 2:33 ` Liu Dave-R63238
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=64ac01180903071915lf27669fq813a5e3842c0c2a1@mail.gmail.com \
--to=ben.menchaca@gmail.com \
--cc=DaveLiu@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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