From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58804) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vj9pd-000109-Js for qemu-devel@nongnu.org; Wed, 20 Nov 2013 10:36:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vj9pY-0003rS-ND for qemu-devel@nongnu.org; Wed, 20 Nov 2013 10:36:45 -0500 Received: from mail-lb0-f182.google.com ([209.85.217.182]:48583) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vj9pY-0003pY-H3 for qemu-devel@nongnu.org; Wed, 20 Nov 2013 10:36:40 -0500 Received: by mail-lb0-f182.google.com with SMTP id u14so4077428lbd.27 for ; Wed, 20 Nov 2013 07:36:39 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <528CD315.8070700@suse.de> References: <528CD315.8070700@suse.de> From: Peter Maydell Date: Wed, 20 Nov 2013 15:36:19 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] ARM cpu object, setting properties from board model List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?Q?Andreas_F=C3=A4rber?= Cc: Igor Mammedov , QEMU Developers On 20 November 2013 15:19, Andreas F=C3=A4rber wrote: > My first thought without reviewing the code is to just inline > object_new() followed by object_property_set_bool() in the machine - > that's what I've done for my downstream rl78, where I needed to postpone > realizing the CPU until the firmware blob had been loaded (similar to > armv7m, you may remember pointing me to that example :)). OK. We're treating cpu_class_by_name() as a public function (which just happens to only be called by target-* code at the moment) then? Just opencoding it is probably simplest, then. thanks -- PMM