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:37:52 +0200 [thread overview]
Message-ID: <4FF16BF0.7010905@redhat.com> (raw)
In-Reply-To: <CAFEAcA_mOrFrxx0_UdA+wPksH41fyiS55C1_LjMDNM5RRFETsQ@mail.gmail.com>
Il 02/07/2012 11:31, Peter Maydell ha scritto:
> On 2 July 2012 10:08, Igor Mitsyanko <i.mitsyanko@samsung.com> wrote:
>> 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.
>
> I don't want things moved piecemeal, especially not one file from
> a whole board model.
>
> I'd also like to see a nice clear summary of the ground rules first
> (ie how you decide which makefile / target / whatever a file should
> be in). At the moment I'm not really sure what the rules are, which
> means I can't properly review those bits of patches.
For now nothing should change compared to the past, except that obj-y
should appear in hw/ARCH/Makefile.objs rather than Makefile.target.
This is because there is still no mechanism to guard the build of
ARM-only devices from hw/Makefile.objs. When Anthony's patch lands, we
can start moving files to hw/Makefile.objs using CONFIG_ARCH_ARM; I
understood Andreas is going to do that.
For new boards, you may want to request a new CONFIG_* symbol (e.g.
CONFIG_EXYNOS) so that new boards can already compile their devices from
hw/Makefile.objs. However, that's up to you and definitely shouldn't be
done for one file from a whole board model, as you said.
Paolo
next prev parent reply other threads:[~2012-07-02 9:38 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 [this message]
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=4FF16BF0.7010905@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).