From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60897) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SyMdd-0005sn-Q4 for qemu-devel@nongnu.org; Mon, 06 Aug 2012 08:42:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SyMdZ-0007sX-O9 for qemu-devel@nongnu.org; Mon, 06 Aug 2012 08:42:25 -0400 Received: from mailout1.w1.samsung.com ([210.118.77.11]:57033) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SyMdZ-0007pR-FJ for qemu-devel@nongnu.org; Mon, 06 Aug 2012 08:42:21 -0400 Received: from eusync3.samsung.com (mailout1.w1.samsung.com [210.118.77.11]) by mailout1.w1.samsung.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTP id <0M8C009B23B9ST60@mailout1.w1.samsung.com> for qemu-devel@nongnu.org; Mon, 06 Aug 2012 13:42:45 +0100 (BST) Received: from [106.109.9.232] by eusync3.samsung.com (Oracle Communications Messaging Server 7u4-23.01(7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPA id <0M8C0027L3AG1K70@eusync3.samsung.com> for qemu-devel@nongnu.org; Mon, 06 Aug 2012 13:42:17 +0100 (BST) Message-id: <501FBBA8.2010109@samsung.com> Date: Mon, 06 Aug 2012 16:42:16 +0400 From: Igor Mitsyanko MIME-version: 1.0 References: <81b9e406e0b0292ccd3168385ab6a73a78a0ada5.1344218410.git.peter.crosthwaite@petalogix.com> In-reply-to: Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v5 09/15] hw: Added generic FIFO API. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: stefanha@gmail.com, qemu-devel@nongnu.org, "Peter A. G. Crosthwaite" , paul@codesourcery.com, edgar.iglesias@gmail.com, john.williams@petalogix.com On 08/06/2012 01:48 PM, Peter Maydell wrote: > On 6 August 2012 03:16, Peter A. G. Crosthwaite > wrote: >> Added a FIFO API that can be used to create and operate byte FIFOs. > I'm not asking for actual conversions, but it would be nice to see a > list of some devices that could in principle be moved to using this FIFO, > as an indication of its general utility. > > Would it make sense for the FIFO to be a QOM object, or is that a > silly idea? > > -- PMM > FIFO introspection capability could be useful I think, and we could implement device-specific fifo "mutants" then (for example, PL330 fifo could be a general FIFO object + "tag" variable).