From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60796) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SldDT-0008RS-97 for qemu-devel@nongnu.org; Mon, 02 Jul 2012 05:46:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SldDM-0007vk-6G for qemu-devel@nongnu.org; Mon, 02 Jul 2012 05:46:46 -0400 Received: from mail-wg0-f53.google.com ([74.125.82.53]:65400) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SldDL-0007vP-U7 for qemu-devel@nongnu.org; Mon, 02 Jul 2012 05:46:40 -0400 Received: by wgbfm10 with SMTP id fm10so4564978wgb.10 for ; Mon, 02 Jul 2012 02:46:38 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <4FF16DFC.2090700@redhat.com> Date: Mon, 02 Jul 2012 11:46:36 +0200 From: Paolo Bonzini MIME-Version: 1.0 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> <4FF164F5.90302@samsung.com> <4FF16BF0.7010905@redhat.com> <4FF16D01.5020207@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] Exynos4: added RTC device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Igor Mitsyanko , Evgeny Voevodin , qemu-devel@nongnu.org, kyungmin.park@samsung.com, d.solodkiy@samsung.com, Oleg Ogurtsov , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= Il 02/07/2012 11:44, Peter Maydell ha scritto: > On 2 July 2012 10:42, Paolo Bonzini 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