From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:38133) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ScvG1-0007JB-SG for qemu-devel@nongnu.org; Fri, 08 Jun 2012 05:13:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ScvFv-0006H9-74 for qemu-devel@nongnu.org; Fri, 08 Jun 2012 05:13:25 -0400 Received: from relay1.mentorg.com ([192.94.38.131]:56235) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ScvFv-0006Gm-1I for qemu-devel@nongnu.org; Fri, 08 Jun 2012 05:13:19 -0400 From: Paul Brook Date: Fri, 8 Jun 2012 10:13:08 +0100 References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201206081013.09756.paul@codesourcery.com> Subject: Re: [Qemu-devel] [RFC] QOMification of AXI stream List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Crosthwaite Cc: Michal Simek , Anthony Liguori , "qemu-devel@nongnu.org Developers" , "Edgar E. Iglesias" , Andreas =?iso-8859-1?q?F=E4rber?= , John Williams > Im looking to QOMifying and refactoring the AXI stream interfaces > between the AXI ethernet and AXI DMA modules. I could use some > guidance on how to do this as I can think of about 6 different > solutions. Sources are hw/xilinx_axienet.c and hw/xilinx_axidma.c. > >... > > So what im proposing is AXI stream is implemented as a unidirectional > point to point bus. The xilinx ethernet system would consist of two of > these buses one for tx, one for rx. I thought the idea was that with QOM the bus/device model would go away. The DMA controller implements an AXIDMA interface, and the device has a AXIDMA link that's connected to that interface. Of course we then hit the usual problem with QOM that we can only link to objects, and it's impossible to expose multiple interfaces of the same type. The DMA controller probably needs a proxy object for each DMA channel. Paul