From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:56955) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rv9u9-0006tb-D0 for qemu-devel@nongnu.org; Wed, 08 Feb 2012 10:57:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rv9u8-0006Hg-7I for qemu-devel@nongnu.org; Wed, 08 Feb 2012 10:57:57 -0500 Received: from relay1.mentorg.com ([192.94.38.131]:61554) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rv9u8-0006HT-2t for qemu-devel@nongnu.org; Wed, 08 Feb 2012 10:57:56 -0500 From: Paul Brook Date: Wed, 8 Feb 2012 15:57:46 +0000 References: <1328687721-16030-1-git-send-email-peter.crosthwaite@petalogix.com> <201202081456.08096.paul@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Message-Id: <201202081557.48450.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 here are some of the problems im trying to solve with the bootloader: > > Smp bootstrap secondary CPUs while loading an elf (currently elfs will be > assumed to be not kernels). > Change the kernel, initrd and dtb load address on the command line. > Use my own SMP secondary bootloop. > > My intention with this patch was to set myself to do boot parameterizations > on the command line by just adding them as qdev props to the > arm_linux_loader and set them using -device instantiation. E.G. -device > arm_boot_loader,initrd_addr=0x10000000. But if I take the approach you are > suggesting, the for this initrd load address option, I would need to add > myself a command line option, fetch that command line option in every arm > machine model and then pass it to arm_load_kernel. No. You just set/override properties on the device that the machine created. I thought we already had this, but it looks like the closest we have is -global. Something like "-property /devicepath/propertyname=value". This is something we need anyway. Creating new devices with -device is of very limited value if you can't link existing device properties to that new device. Remember that in the new world order we don't have magic bus-device, everything is done via link properlties. Paul