From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:34042) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SlccH-0005fL-Op for qemu-devel@nongnu.org; Mon, 02 Jul 2012 05:08:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Slcc7-0006Hh-Sa for qemu-devel@nongnu.org; Mon, 02 Jul 2012 05:08:21 -0400 Received: from mailout4.w1.samsung.com ([210.118.77.14]:58810) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Slcc7-0006HU-My for qemu-devel@nongnu.org; Mon, 02 Jul 2012 05:08:11 -0400 Received: from eusync2.samsung.com (mailout4.w1.samsung.com [210.118.77.14]) by mailout4.w1.samsung.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTP id <0M6J00LXE02N9580@mailout4.w1.samsung.com> for qemu-devel@nongnu.org; Mon, 02 Jul 2012 10:08:47 +0100 (BST) Received: from [106.109.9.244] by eusync2.samsung.com (Oracle Communications Messaging Server 7u4-23.01(7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPA id <0M6J00L4101H9N70@eusync2.samsung.com> for qemu-devel@nongnu.org; Mon, 02 Jul 2012 10:08:06 +0100 (BST) Date: Mon, 02 Jul 2012 13:08:05 +0400 From: Igor Mitsyanko In-reply-to: <4FF06C3C.2070706@redhat.com> Message-id: <4FF164F5.90302@samsung.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-15; format=flowed Content-transfer-encoding: QUOTED-PRINTABLE References: <1340610940-923-1-git-send-email-o.ogurtsov@samsung.com> <1340610940-923-2-git-send-email-o.ogurtsov@samsung.com> <4FE82E60.5050007@suse.de> <4FE84FAE.1050709@samsung.com> <4FE852F7.9060405@suse.de> <4FE92A16.5060705@samsung.com> <4FED9EFA.8040402@suse.de> <4FF06C3C.2070706@redhat.com> Subject: Re: [Qemu-devel] [PATCH] Exynos4: added RTC device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: peter.maydell@linaro.org, Evgeny Voevodin , qemu-devel@nongnu.org, kyungmin.park@samsung.com, d.solodkiy@samsung.com, Oleg Ogurtsov , =?ISO-8859-15?Q?Andreas_F=E4rber?= On 07/01/2012 07:26 PM, Paolo Bonzini wrote: > Il 29/06/2012 14:26, Andreas F=E4rber 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=20 hw/arm/Makefile.objs while somebody moves all new and old not=20 cpu-specific devices (not just exynos-related) from hw/arm/Makefile.o= bjs=20 to hw/Makefile.objs with one commit? Because having one RTC device= =20 compile through hw/Makefile.objs while all other exynos devices are= =20 compiled through hw/arm/Makefile.objs doesn't makes much sense. And also its not clear whether you're planning to compile these devic= es=20 through obj-y or through hw-obj-y, because we still have=20 target_phys_addr_t in our memory API.