From: jerome.arbez-gindre@laposte.net (Jérôme Arbez-Gindre)
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: DMA transfer failing most of the time
Date: 22 Sep 2006 15:33:06 +0200 [thread overview]
Message-ID: <87irjgni0d.fsf@bibi.net> (raw)
In-Reply-To: <87fyels3aw.fsf@bibi.net>
jerome.arbez-gindre@laposte.net (Jérôme Arbez-Gindre) writes:
> Hi,
> I'm writing a PCI board emulation in Qemu 0.8.1. (i386)
> I'm also writing the corresponding Linux 2.6 driver.
>
> In the emulation, I'm performing DMA transfers by calls to
>
> cpu_physical_memory_rw()
>
> and then, I'm generating a interrupt.
>
> In the Linux driver, in the interrupt handler, when I check the
> transferred data, the most of the time they are not updated and when
> after waiting a little (10ms), I check again the transferred data,
> and they are OK (most of the time).
>
> In your opinion, is their something I'm missing ?
>
> Any help would be appreciated.
>
> Thanks,
>
> Jérôme.
I have found my mistake, which had nothing to do with Qemu.
Thanks and apologies.
Jérôme
prev parent reply other threads:[~2006-09-22 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 14:27 [Qemu-devel] DMA transfer failing most of the time Jérôme Arbez-Gindre
2006-09-22 13:33 ` Jérôme Arbez-Gindre [this message]
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=87irjgni0d.fsf@bibi.net \
--to=jerome.arbez-gindre@laposte.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.