From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:34373) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RvAGZ-0007JC-MI for qemu-devel@nongnu.org; Wed, 08 Feb 2012 11:21:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RvAGT-0002P2-JV for qemu-devel@nongnu.org; Wed, 08 Feb 2012 11:21:07 -0500 Received: from mail-pw0-f45.google.com ([209.85.160.45]:45094) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RvAGT-0002Ok-6p for qemu-devel@nongnu.org; Wed, 08 Feb 2012 11:21:01 -0500 Received: by pbbro12 with SMTP id ro12so816632pbb.4 for ; Wed, 08 Feb 2012 08:20:59 -0800 (PST) Message-ID: <4F32A0E7.9000009@codemonkey.ws> Date: Wed, 08 Feb 2012 10:20:55 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <1328687721-16030-1-git-send-email-peter.crosthwaite@petalogix.com> <201202081456.08096.paul@codesourcery.com> <201202081557.48450.paul@codesourcery.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: qemu-devel@nongnu.org, peter.maydell@linaro.org, aliguori@us.ibm.com, Paul Brook , Alexander Graf On 02/08/2012 10:03 AM, Peter Crosthwaite wrote: > 2012/2/9 Paul Brook > >>> 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". A lot of refactoring is needed to make this a reality. Please read through the various QOM threads for details of what needs to be done. Regards, Anthony Liguori