From: Igor Mitsyanko <i.mitsyanko@samsung.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: peter.maydell@linaro.org,
"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 13:08:05 +0400 [thread overview]
Message-ID: <4FF164F5.90302@samsung.com> (raw)
In-Reply-To: <4FF06C3C.2070706@redhat.com>
On 07/01/2012 07:26 PM, Paolo Bonzini wrote:
> Il 29/06/2012 14:26, Andreas Färber ha scritto:
>>>>
>>>> Oh, I see. Should we place this device to hw/Makefile.objs in v2?
>> That would've been nice, but I'll do it as a follow-up now.
>
> Yes, so we can also use Anthony's new CONFIG_ARCH_ARM (introducing
> CONFIG_EXYNOS can be done later).
>
> Paolo
>
>
>
So, what's the consensus here, for now new devices go to
hw/arm/Makefile.objs while somebody moves all new and old not
cpu-specific devices (not just exynos-related) from hw/arm/Makefile.objs
to hw/Makefile.objs with one commit? Because having one RTC device
compile through hw/Makefile.objs while all other exynos devices are
compiled through hw/arm/Makefile.objs doesn't makes much sense.
And also its not clear whether you're planning to compile these devices
through obj-y or through hw-obj-y, because we still have
target_phys_addr_t in our memory API.
next prev parent reply other threads:[~2012-07-02 9:08 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 [this message]
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
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=4FF164F5.90302@samsung.com \
--to=i.mitsyanko@samsung.com \
--cc=afaerber@suse.de \
--cc=d.solodkiy@samsung.com \
--cc=e.voevodin@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=o.ogurtsov@samsung.com \
--cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.