Re: [Qemu-devel] [RFC PATCH] arm boot: added QOM device definition

From: Paul Brook <paul@codesourcery.com>
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
Subject: Re: [Qemu-devel] [RFC PATCH] arm boot: added QOM device definition
Date: Wed, 8 Feb 2012 14:20:53 +0000	[thread overview]
Message-ID: <201202081420.54442.paul@codesourcery.com> (raw)
In-Reply-To: <CAEgOgz6js39Q6KC+S_X5V0k-m3G154x07e=-DGMB-hbaJbEUrw@mail.gmail.com>

> 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