On 18/07/13 14:44, Alexander Graf wrote:
What I would do, however, is to complete even the INPUT/OUTPUT_MORE
commands only at the end of the whole request. This is definitely
allowed behaviour, and it ensures that a memory region isn't already
reused by the OS while e.g. a write request is
Am 17.07.2013 um 22:12 hat Mark Cave-Ayland geschrieben:
On 17/07/13 14:35, Kevin Wolf wrote:
Okay, so I've had a quick look at that DMA controller, and it seems that
for a complete emulation, there's no way around using a bounce buffer
(and calling directly into the block layer instead of
On 18.07.2013, at 09:41, Kevin Wolf wrote:
Am 17.07.2013 um 22:12 hat Mark Cave-Ayland geschrieben:
On 17/07/13 14:35, Kevin Wolf wrote:
Okay, so I've had a quick look at that DMA controller, and it seems that
for a complete emulation, there's no way around using a bounce buffer
(and
Am 18.07.2013 um 15:44 hat Alexander Graf geschrieben:
On 18.07.2013, at 09:41, Kevin Wolf wrote:
Am 17.07.2013 um 22:12 hat Mark Cave-Ayland geschrieben:
On 17/07/13 14:35, Kevin Wolf wrote:
Okay, so I've had a quick look at that DMA controller, and it seems that
for a complete
On 17/07/13 09:16, Kevin Wolf wrote:
Hi Kevin,
Thanks for the reply - CC to qemu-devel as requested.
I've been testing some of Alex Graf's patches for running Darwin
under QEMU PPC and have been experiencing some timeout problems on
block devices. My attention is drawn to this commit in
On 17.07.2013, at 14:52, Mark Cave-Ayland wrote:
On 17/07/13 09:16, Kevin Wolf wrote:
Hi Kevin,
Thanks for the reply - CC to qemu-devel as requested.
I've been testing some of Alex Graf's patches for running Darwin
under QEMU PPC and have been experiencing some timeout problems on
On 17/07/13 14:35, Kevin Wolf wrote:
Okay, so I've had a quick look at that DMA controller, and it seems that
for a complete emulation, there's no way around using a bounce buffer
(and calling directly into the block layer instead of using
dma-helpers.c) for the general case.
You can have a
