All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>, Consul <void@aleksoft.net>
Subject: Re: [Qemu-devel] Windows runtime error
Date: Fri, 22 May 2009 18:15:54 +0100	[thread overview]
Message-ID: <200905221815.55261.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580905220953l9d71efev48d32dc4e74f57f4@mail.gmail.com>

> It would be nice to avoid this restriction. For example, fdc init
> could take pointers to the DMA functions as parameters.

It, could, but it'll need rewriting anyway when it gets converted to the new 
device API. What we really want is a consistent way of transferring data 
between devices (aka "DMA channels"). We already have several different ad-hoc 
implementations. pcnet, etraxf_eth and omap_dss and pxa2xx_dma are ones that 
spring to mind.

Paul

      reply	other threads:[~2009-05-22 17:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 21:58 [Qemu-devel] Windows runtime error Consul
2009-05-22  2:11 ` Anthony Liguori
2009-05-22 12:04   ` Paul Brook
2009-05-22 13:07     ` Anthony Liguori
2009-05-22 13:15       ` Paul Brook
2009-05-22 15:48         ` Anthony Liguori
2009-05-22 16:12           ` Blue Swirl
2009-05-22 16:39             ` Anthony Liguori
2009-05-22 15:55         ` Blue Swirl
2009-05-22 16:36           ` Anthony Liguori
2009-05-24  9:14           ` Avi Kivity
2009-05-27 22:39             ` Anthony Liguori
2009-05-22 15:51   ` Blue Swirl
2009-05-22 16:35     ` Anthony Liguori
2009-05-22 16:53       ` Blue Swirl
2009-05-22 17:15         ` Paul Brook [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=200905221815.55261.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=void@aleksoft.net \
    /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.