From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:52639)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Paul_Brook@mentor.com>) id 1Rv8wX-0005FZ-41
	for qemu-devel@nongnu.org; Wed, 08 Feb 2012 09:56:26 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Paul_Brook@mentor.com>) id 1Rv8wO-0002D2-5j
	for qemu-devel@nongnu.org; Wed, 08 Feb 2012 09:56:21 -0500
Received: from relay1.mentorg.com ([192.94.38.131]:51864)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Paul_Brook@mentor.com>) id 1Rv8wN-0002Cp-Tm
	for qemu-devel@nongnu.org; Wed, 08 Feb 2012 09:56:12 -0500
From: Paul Brook <paul@codesourcery.com>
Date: Wed, 8 Feb 2012 14:56:07 +0000
References: <1328687721-16030-1-git-send-email-peter.crosthwaite@petalogix.com>
	<201202081420.54442.paul@codesourcery.com>
	<CAEgOgz7xDQeQeWVwwrUOuQL1AH5Japz7fD_2GD+kPcNS2F1_9Q@mail.gmail.com>
In-Reply-To: <CAEgOgz7xDQeQeWVwwrUOuQL1AH5Japz7fD_2GD+kPcNS2F1_9Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-6"
Content-Transfer-Encoding: 7bit
Message-Id: <201202081456.08096.paul@codesourcery.com>
Subject: Re: [Qemu-devel] [RFC PATCH] arm boot: added QOM device definition
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
Cc: peter.maydell@linaro.org, aliguori@us.ibm.com, Alexander Graf <agraf@suse.de>, qemu-devel@nongnu.org

> Its the other problem I am more worried about, i.e. when I -device
> instantiate my bootloader with an existing machine how do I get my ram_size
> and board_ID? The no machine opts for devices policy makes this impossible
> such that I would have to pass in board_id and ram_size to
> the boot-loader on the command line. Is there any acceptable way where the
> machine model can make something globally available to devices for the
> purpose of instantiating them with -device?

I'm not convinved this is a problem worth solving. i.e. is it really worth 
consirering the bootloader a user-replaceable part of the machine (without 
actually changing the machine description)?  Making our bootloader not suck 
seems a better option.

Paul