linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul White <pwhite@networkrobots.com>
To: jtm@smoothsmoothie.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: (allocating non-cachable memory) (or More on the i82596)
Date: Fri, 29 Jun 2001 10:55:29 -0700	[thread overview]
Message-ID: <200106291751.f5THpK810528@stimpy.networkrobots.com> (raw)
In-Reply-To: <20010629113055.A30951@shamus.smoothsmoothie.com>


Jay,

Basically, on any CPU, DMA requires either no cache, or at least a cache
coherent
system.  Cache Coherency is a two-part thing, the CPU must support it, the
memory (system) controller.  If the memory controller doesn't generate the
proper
cache coherency snoop cycles, the CPU still has no idea to flush or invalidate
cache lines.

Paul W.



At 11:30 AM 6/29/2001 -0500, jtm@smoothsmoothie.com wrote:
>
>On Fri, Jun 29, 2001 at 03:39:57AM -0400, Dan Malek wrote:
>>
>> jtm@smoothsmoothie.com wrote:
>>
>> > .... The buffer memory will get filled
>> > via DMA, and therefore must not be cached.
>>
>> Huh????  The 8260 is cache coherent, you don't need to do that.
>
>OK. I've had more experience with the 860, and just assumed the
>8260 had the same no cache requirement on DMA. Thanks.
>
>--
>Jay Monkman	    The truth knocks on the door and you say "Go away, I'm
>monkman@jump.net    looking for the truth," and so it goes away. Puzzling.
>		     - from _Zen_and_the_Art_of_Motorcycle_Maintenance_
>
>
-------------------------------------------------------------
Network Robots, Inc.         /--\               Paul H. White
                           / ____ \
4695 Chabot Dr. #200      / ( oo ) \       Software Developer
Pleasanton, CA 94588     /   ----   \             Engineering
(925) 924-8600           \   ----   /          (925) 580-4883
                          \  V--V  /
                           \      /
                             \--/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-06-29 17:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26 10:22 (allocating non-cachable memory) (or More on the i82596) Justin (Gus) Hurwitz
2001-06-26 21:08 ` jtm
2001-06-28  8:52   ` Justin (Gus) Hurwitz
2001-06-29  7:39   ` Dan Malek
2001-06-29  5:21     ` Justin (Gus) Hurwitz
2001-06-29  6:58     ` Justin (Gus) Hurwitz
2001-07-01  5:04       ` Dan Malek
2001-06-29 16:30     ` jtm
2001-06-29 17:55       ` Paul White [this message]
2001-06-29 17:45     ` Paul White
2001-06-29 17:48     ` Paul White
2001-06-29 15:41       ` Matt Porter
2001-07-01  5:07         ` Dan Malek
2001-07-05 10:11         ` Justin (Gus) Hurwitz
2001-07-05 20:00           ` Dan Malek
2001-07-01  5:09       ` Dan Malek
2001-07-01  6:45         ` Paul White
     [not found] <200106281622.f5SGMW810376@stimpy.networkrobots.com>
2001-06-28 10:43 ` Justin (Gus) Hurwitz
     [not found] ` <Pine.LNX.3.95.1010628062229.5112E-100000@november.bhjjh.er ols.com>
2001-06-29  0:13   ` Paul White
2001-06-29  9:16     ` Justin (Gus) Hurwitz
     [not found]     ` <Pine.LNX.3.95.1010629042746.5292E-100000@november.bhjjh.er ols.com>
2001-06-29 17:53       ` Paul White
2001-06-29 12:11         ` Justin (Gus) Hurwitz
2001-07-01  5:17           ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2001-06-28 16:28 Paul White

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=200106291751.f5THpK810528@stimpy.networkrobots.com \
    --to=pwhite@networkrobots.com \
    --cc=jtm@smoothsmoothie.com \
    --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 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).