From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>,
kvm-devel@lists.sourceforge.net,
andrzej zaborowski <balrogg@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 2/6] PCI DMA API (v2)
Date: Sun, 6 Apr 2008 19:40:36 -0500 [thread overview]
Message-ID: <200804061940.37403.paul@codesourcery.com> (raw)
In-Reply-To: <fb249edb0804061001k2d3aac0brb4eaac23e381cdd4@mail.gmail.com>
> As a note, the DMA controllers in the ARM system-on-chip's can
> byte-swap, do 90deg rotation of 2D arrays, transparency (probably
> intened for image blitting, but still available on any kind of
> transfers), etc., and most importantly issue interrupts on reaching
> different points of a transfer. It is not worth worrying about them
> in this API. I have been for some time wanting to make a separate api
> called soc_dma whose task would be using simply memcpy (or zero-copy)
> in the most basic case (interrupts off, no transparency,
> same-endianness endpoints), as these properties are common for DMA on
> the TI OMAPs, the Intel PXAs and the Samsung S3Cs (which otherwise
> have little in common).
Are you sure you aren't confusing the DMA engine itelf (which is just annother
peripheral) with a mechanism for allowing dma engines access to the system.
Paul
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
WARNING: multiple messages have this Message-ID (diff)
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>, kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-devel] [Qemu-devel] [PATCH 2/6] PCI DMA API (v2)
Date: Sun, 6 Apr 2008 19:40:36 -0500 [thread overview]
Message-ID: <200804061940.37403.paul@codesourcery.com> (raw)
In-Reply-To: <fb249edb0804061001k2d3aac0brb4eaac23e381cdd4@mail.gmail.com>
> As a note, the DMA controllers in the ARM system-on-chip's can
> byte-swap, do 90deg rotation of 2D arrays, transparency (probably
> intened for image blitting, but still available on any kind of
> transfers), etc., and most importantly issue interrupts on reaching
> different points of a transfer. It is not worth worrying about them
> in this API. I have been for some time wanting to make a separate api
> called soc_dma whose task would be using simply memcpy (or zero-copy)
> in the most basic case (interrupts off, no transparency,
> same-endianness endpoints), as these properties are common for DMA on
> the TI OMAPs, the Intel PXAs and the Samsung S3Cs (which otherwise
> have little in common).
Are you sure you aren't confusing the DMA engine itelf (which is just annother
peripheral) with a mechanism for allowing dma engines access to the system.
Paul
next prev parent reply other threads:[~2008-04-07 0:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 4:02 [PATCH 1/6] Use ram_addr_t for cpu_get_physical_page_desc (v2) Anthony Liguori
2008-04-05 4:02 ` [Qemu-devel] " Anthony Liguori
2008-04-05 4:02 ` [PATCH 2/6] PCI DMA API (v2) Anthony Liguori
2008-04-05 4:02 ` [Qemu-devel] " Anthony Liguori
2008-04-05 4:02 ` [PATCH 3/6] virtio for QEMU (v2) Anthony Liguori
2008-04-05 4:02 ` [Qemu-devel] " Anthony Liguori
2008-04-05 4:02 ` [PATCH 4/6] virtio network driver (v2) Anthony Liguori
2008-04-05 4:02 ` [Qemu-devel] " Anthony Liguori
2008-04-05 4:02 ` [PATCH 5/6] virtio block " Anthony Liguori
2008-04-05 4:02 ` [Qemu-devel] " Anthony Liguori
2008-04-05 4:02 ` [PATCH 6/6] virtio balloon " Anthony Liguori
2008-04-05 4:02 ` [Qemu-devel] " Anthony Liguori
2008-04-06 6:57 ` [Qemu-devel] [PATCH 2/6] PCI DMA API (v2) Blue Swirl
2008-04-06 6:57 ` Blue Swirl
2008-04-06 15:22 ` Anthony Liguori
2008-04-06 15:22 ` [kvm-devel] " Anthony Liguori
2008-04-06 17:01 ` andrzej zaborowski
2008-04-06 17:01 ` [kvm-devel] " andrzej zaborowski
2008-04-06 17:46 ` Anthony Liguori
2008-04-06 17:46 ` [kvm-devel] " Anthony Liguori
2008-04-07 0:40 ` Paul Brook [this message]
2008-04-07 0:40 ` Paul Brook
2008-04-07 8:32 ` andrzej zaborowski
2008-04-07 8:32 ` [kvm-devel] " andrzej zaborowski
2008-04-07 15:44 ` Paul Brook
2008-04-07 15:44 ` [Qemu-devel] " Paul Brook
2008-04-07 3:41 ` [Qemu-devel] [PATCH 1/6] Use ram_addr_t for cpu_get_physical_page_desc (v2) Paul Brook
2008-04-07 13:22 ` Anthony Liguori
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=200804061940.37403.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=balrogg@gmail.com \
--cc=blauwirbel@gmail.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.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.