From: Peter Maydell <peter.maydell@linaro.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Igor Mammedov <imammedo@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ARM cpu object, setting properties from board model
Date: Wed, 20 Nov 2013 15:36:19 +0000 [thread overview]
Message-ID: <CAFEAcA8utcwdrPH5p=d1YTNWtXQSv6awKAEG-xcyoKfCJHepog@mail.gmail.com> (raw)
In-Reply-To: <528CD315.8070700@suse.de>
On 20 November 2013 15:19, Andreas Färber <afaerber@suse.de> wrote:
> My first thought without reviewing the code is to just inline
> object_new() followed by object_property_set_bool() in the machine -
> that's what I've done for my downstream rl78, where I needed to postpone
> realizing the CPU until the firmware blob had been loaded (similar to
> armv7m, you may remember pointing me to that example :)).
OK. We're treating cpu_class_by_name() as a public function
(which just happens to only be called by target-* code at the moment)
then? Just opencoding it is probably simplest, then.
thanks
-- PMM
prev parent reply other threads:[~2013-11-20 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 20:01 [Qemu-devel] ARM cpu object, setting properties from board model Peter Maydell
2013-11-19 20:12 ` Peter Maydell
2013-11-19 20:16 ` Igor Mammedov
2013-11-20 15:19 ` Andreas Färber
2013-11-20 15:36 ` Peter Maydell [this message]
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='CAFEAcA8utcwdrPH5p=d1YTNWtXQSv6awKAEG-xcyoKfCJHepog@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=imammedo@redhat.com \
--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).