From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:43644) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RvABK-0004rC-V3 for qemu-devel@nongnu.org; Wed, 08 Feb 2012 11:15:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RvABE-0001JF-Cs for qemu-devel@nongnu.org; Wed, 08 Feb 2012 11:15:42 -0500 Received: from relay1.mentorg.com ([192.94.38.131]:64175) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RvABE-0001Is-5b for qemu-devel@nongnu.org; Wed, 08 Feb 2012 11:15:36 -0500 From: Paul Brook Date: Wed, 8 Feb 2012 16:15:30 +0000 References: <1328687721-16030-1-git-send-email-peter.crosthwaite@petalogix.com> <201202081557.48450.paul@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Message-Id: <201202081615.30937.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 > Ok, that sounds more workable :). So i would add my initrd_addr property to > the bootloader as a qdev prop as I suggested before, then something like: > > qemu-system-arm -M verstailepb -property > /foo/bar/arm_linux_loader.0,initrd_addr=0x10000000 Yes. There are various implementation/syntax details to resolve, but in principle I think it should work a lot like that. Paul