From: "David S. Miller" <davem@redhat.com>
To: Martin Diehl <lists@mdiehl.de>
Cc: lists@mdiehl.de, noah@caltech.edu,
irda-users@lists.sourceforge.net, netdev@oss.sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [irda-users] [PATCH] Make VLSI FIR depend on X86
Date: Tue, 21 Oct 2003 00:12:41 -0700 [thread overview]
Message-ID: <20031021001241.390a16df.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0310210858550.4246-100000@notebook.home.mdiehl.de>
On Tue, 21 Oct 2003 09:12:53 +0200 (CEST)
Martin Diehl <lists@mdiehl.de> wrote:
> Last time I checked pci_dma_sync was meant to sync the mapping when
> ownership gets transferred from busmaster to cpu, i.e. after hardware
> used/modified the buffer. What about the other direction when the cpu
> filled a reused streaming map to device and wants to pass ownership to the
> busmaster - we need to flush cpu caches to make sure the busmaster sees
> the modified data.
That's absolutely correct.
Several times I've noted that this is a BUG in the API, that there
is no way to sync the other way, someone just has to add the interface
hooks then all the platform maintainers will implement it.
Here, do this, add a new interface called pci_dma_sync_to_device()
with the appropriate args. Add a NOP implementation to asm-i386/pci.h
and suitable documentation changes to Documentation/DMA-mapping.txt
When you send me that patch, I'll work with the platform maintainers
to take care of the rest.
Deal?
next prev parent reply other threads:[~2003-10-21 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 6:41 [PATCH] Make VLSI FIR depend on X86 Noah J. Misch
2003-10-20 17:30 ` [irda-users] " Martin Diehl
2003-10-21 4:17 ` David S. Miller
2003-10-21 7:12 ` Martin Diehl
2003-10-21 7:12 ` David S. Miller [this message]
2003-10-21 7:33 ` Martin Diehl
2003-10-21 8:13 ` David S. Miller
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=20031021001241.390a16df.davem@redhat.com \
--to=davem@redhat.com \
--cc=irda-users@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@mdiehl.de \
--cc=netdev@oss.sgi.com \
--cc=noah@caltech.edu \
/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).