From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Igor Mitsyanko" <i.mitsyanko@samsung.com>,
"Evgeny Voevodin" <e.voevodin@samsung.com>,
qemu-devel@nongnu.org, kyungmin.park@samsung.com,
d.solodkiy@samsung.com, "Oleg Ogurtsov" <o.ogurtsov@samsung.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] Exynos4: added RTC device
Date: Mon, 02 Jul 2012 11:46:36 +0200 [thread overview]
Message-ID: <4FF16DFC.2090700@redhat.com> (raw)
In-Reply-To: <CAFEAcA9wYbLsa8SPehVJ-3YL8FPRW6BWgH55SPVNJWCGap7UAQ@mail.gmail.com>
Il 02/07/2012 11:44, Peter Maydell ha scritto:
> On 2 July 2012 10:42, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> > Personally, I believe it'd be best if board descriptions were moved to
>> > hw/ARCH, even if all the required hardware is in hw/ and even if the
>> > file can be moved from obj-y to hw-obj-y. However, this can be left
>> > open to later discussion, and is complicated by the fact that some
>> > boards (e.g. musicpal) include devices and machine models in the same file.
> I don't personally see the distinction between "device model" and
> "machine model" as particularly interesting, and I hope/think that
> with increased QOMification the implementation differences beween
> the two will tend go away.
I agree. The distinction is just that machine models often have a
dependency on target-ARCH/ files, and that would be (for me) the line
between hw/ and hw/ARCH.
Paolo
next prev parent reply other threads:[~2012-07-02 9:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1340610940-923-1-git-send-email-o.ogurtsov@samsung.com>
[not found] ` <1340610940-923-2-git-send-email-o.ogurtsov@samsung.com>
[not found] ` <4FE82E60.5050007@suse.de>
[not found] ` <4FE84FAE.1050709@samsung.com>
[not found] ` <4FE852F7.9060405@suse.de>
[not found] ` <4FE92A16.5060705@samsung.com>
[not found] ` <4FED9EFA.8040402@suse.de>
2012-07-01 15:26 ` [Qemu-devel] [PATCH] Exynos4: added RTC device Paolo Bonzini
2012-07-02 9:08 ` Igor Mitsyanko
2012-07-02 9:31 ` Peter Maydell
2012-07-02 9:37 ` Paolo Bonzini
2012-07-02 9:42 ` Paolo Bonzini
2012-07-02 9:44 ` Peter Maydell
2012-07-02 9:46 ` Paolo Bonzini [this message]
2012-07-02 12:27 ` Andreas Färber
2012-07-02 12:04 ` Andreas Färber
2012-07-02 12:19 ` Peter Maydell
2012-07-02 11:44 ` Andreas Färber
2012-07-02 12:18 ` Igor Mitsyanko
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=4FF16DFC.2090700@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=d.solodkiy@samsung.com \
--cc=e.voevodin@samsung.com \
--cc=i.mitsyanko@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=o.ogurtsov@samsung.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).