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:56:07 +0000 [thread overview]
Message-ID: <201202081456.08096.paul@codesourcery.com> (raw)
In-Reply-To: <CAEgOgz7xDQeQeWVwwrUOuQL1AH5Japz7fD_2GD+kPcNS2F1_9Q@mail.gmail.com>
> 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
next prev parent reply other threads:[~2012-02-08 14:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 7:55 [Qemu-devel] [RFC PATCH] arm boot: added QOM device definition Peter A. G. Crosthwaite
2012-02-08 9:06 ` Paul Brook
2012-02-08 10:11 ` Peter Crosthwaite
2012-02-08 10:44 ` Paul Brook
2012-02-08 11:10 ` Peter Crosthwaite
2012-02-08 11:39 ` Paul Brook
2012-02-08 11:59 ` Peter Crosthwaite
2012-02-08 12:27 ` Paul Brook
2012-02-08 12:41 ` Alexander Graf
2012-02-08 13:04 ` Peter Crosthwaite
2012-02-08 13:10 ` Alexander Graf
2012-02-08 13:30 ` Peter Crosthwaite
2012-02-08 13:35 ` Alexander Graf
2012-02-08 14:05 ` Peter Crosthwaite
2012-02-08 14:17 ` Alexander Graf
2012-02-08 14:20 ` Paul Brook
2012-02-08 14:39 ` Peter Crosthwaite
2012-02-08 14:56 ` Paul Brook [this message]
2012-02-08 15:14 ` Peter Crosthwaite
2012-02-08 15:57 ` Paul Brook
2012-02-08 16:03 ` Peter Crosthwaite
2012-02-08 16:15 ` Paul Brook
2012-02-08 16:35 ` Anthony Liguori
2012-02-09 1:22 ` Peter Crosthwaite
2012-02-09 12:03 ` Paul Brook
2012-02-08 16:20 ` Anthony Liguori
2012-02-08 13:47 ` Anthony Liguori
2012-02-20 19:43 ` Peter Maydell
2012-02-20 19:51 ` Andreas Färber
2012-02-20 19:56 ` Peter Maydell
2012-02-21 9:15 ` Peter Crosthwaite
2012-02-21 10:20 ` Peter Maydell
2012-02-08 13:41 ` Anthony Liguori
2012-02-09 13:22 ` Andreas Färber
2012-02-10 2:11 ` Peter Crosthwaite
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201202081456.08096.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=peter.crosthwaite@petalogix.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).