From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:54289) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rv8OU-0007xP-7B for qemu-devel@nongnu.org; Wed, 08 Feb 2012 09:21:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rv8OK-0002bR-An for qemu-devel@nongnu.org; Wed, 08 Feb 2012 09:21:10 -0500 Received: from relay1.mentorg.com ([192.94.38.131]:47411) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rv8OK-0002bL-4y for qemu-devel@nongnu.org; Wed, 08 Feb 2012 09:21:00 -0500 From: Paul Brook Date: Wed, 8 Feb 2012 14:20:53 +0000 References: <1328687721-16030-1-git-send-email-peter.crosthwaite@petalogix.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Message-Id: <201202081420.54442.paul@codesourcery.com> Subject: Re: [Qemu-devel] [RFC PATCH] arm boot: added QOM device definition List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Crosthwaite Cc: peter.maydell@linaro.org, aliguori@us.ibm.com, Alexander Graf , qemu-devel@nongnu.org > So if we consider this bootloader a device and its -dtb argument a property > of that device, then what you are implying is that every device property of > every device in a machine must be managed by the machine model? Isn't the > dynamic machine model work that is in progress is trying to get away the > approach where fixed machine models have to micromanage all their attached > devices? with the ultimate goal of -no-machine how will the bootloader get > this dtb argument? My expectation is that we have some way for the machine description to tag objects/properties that pap to the generic commandline options. In the same way that we'd probably want to tag the default PCI bus, or UARTs for matching with the -serial commandline. Some of these can be guessed, others you need the machine description to tell you. Paul