From: Roman Zippel <zippel@linux-m68k•org>
To: paulus@samba•org
Cc: Armin Kuster <akuster@mvista•com>,
ppcdevel <linuxppc-dev@lists•linuxppc.org>
Subject: Re: New API for non cache coherent ppc cpu's
Date: Fri, 23 Nov 2001 00:50:07 +0100 [thread overview]
Message-ID: <3BFD8F2F.247CDF33@linux-m68k.org> (raw)
In-Reply-To: 15357.26322.107051.143144@cargo.ozlabs.ibm.com
Hi,
Paul Mackerras wrote:
> If we have to have a consistent_sync_page, it should be purely a local
> function in our implementation of the official DMA mapping API - see
> Documentation/DMA-mapping.txt. Drivers should be using functions such
> as pci_alloc_consistent, pci_map_single, pci_dma_sync_single,
> pci_unmap_single, etc. The implementation of those routines should do
> the correct cache flushing - if it doesn't then we need to fix it.
This document only describes DMA _mappings_, it doesn't say anything
about cache coherency.
> If you're talking about non-PCI devices, use the pci DMA API but just
> pass NULL for the dev (we need to make sure that will work ok on the
> non-cache-coherent cpus).
That's the other problem, "non-PCI" sounds like ISA there, what about
other buses?
bye, Roman
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-22 23:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 20:13 New API for non cache coherent ppc cpu's Armin Kuster
2001-11-21 11:15 ` Roman Zippel
2001-11-21 18:29 ` Armin Kuster
2001-11-21 20:20 ` Roman Zippel
2001-11-22 20:57 ` Paul Mackerras
2001-11-22 23:07 ` Dan Malek
2001-11-22 23:54 ` Roman Zippel
2001-11-23 1:32 ` Paul Mackerras
2001-11-23 16:08 ` Dan Malek
2001-11-22 23:50 ` Roman Zippel [this message]
2001-11-23 1:09 ` 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=3BFD8F2F.247CDF33@linux-m68k.org \
--to=zippel@linux-m68k$(echo .)org \
--cc=akuster@mvista$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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