From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:50452) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoXft-00023v-Eq for qemu-devel@nongnu.org; Wed, 03 Aug 2011 05:23:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QoXfs-00045P-Jy for qemu-devel@nongnu.org; Wed, 03 Aug 2011 05:23:37 -0400 Received: from mx1.redhat.com ([209.132.183.28]:20547) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoXfs-000458-Bo for qemu-devel@nongnu.org; Wed, 03 Aug 2011 05:23:36 -0400 Message-ID: <4E391392.4040200@redhat.com> Date: Wed, 03 Aug 2011 12:23:30 +0300 From: Avi Kivity MIME-Version: 1.0 References: <4E381EA7.2070809@redhat.com> <4E383C55.5050703@redhat.com> <4E38647F.3010509@codemonkey.ws> <4E38B1A7.4090403@codemonkey.ws> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] modelling omap_gpmc with the hierarchical memory API List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers On 08/03/2011 12:10 PM, Peter Maydell wrote: > [*] I did convince myself that you do want a sysbus bus on each > chip select, because in theory in the hardware you could put an > external address decoder on the gpmc_a[] bus and hang multiple > devices off one chipselect. So that's a sysbus, really. No, you've added a device which is yet another bus. -- error compiling committee.c: too many arguments to function