From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M7YLn-0000Xu-Fu for qemu-devel@nongnu.org; Fri, 22 May 2009 13:16:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M7YLi-0000V2-QS for qemu-devel@nongnu.org; Fri, 22 May 2009 13:16:07 -0400 Received: from [199.232.76.173] (port=56970 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M7YLi-0000Uu-I8 for qemu-devel@nongnu.org; Fri, 22 May 2009 13:16:02 -0400 Received: from mx20.gnu.org ([199.232.41.8]:27722) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M7YLi-0003tW-D6 for qemu-devel@nongnu.org; Fri, 22 May 2009 13:16:02 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M7YLh-0005xD-An for qemu-devel@nongnu.org; Fri, 22 May 2009 13:16:01 -0400 From: Paul Brook Subject: Re: [Qemu-devel] Windows runtime error Date: Fri, 22 May 2009 18:15:54 +0100 References: <4A16D44C.7000805@codemonkey.ws> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905221815.55261.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Blue Swirl , Consul > 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