From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:40961) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T6LuT-00045X-Ur for qemu-devel@nongnu.org; Tue, 28 Aug 2012 09:32:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T6LuP-0004Hc-Cx for qemu-devel@nongnu.org; Tue, 28 Aug 2012 09:32:49 -0400 Received: from relay1.mentorg.com ([192.94.38.131]:45482) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T6LuP-0004HT-6r for qemu-devel@nongnu.org; Tue, 28 Aug 2012 09:32:45 -0400 From: Paul Brook Date: Tue, 28 Aug 2012 14:32:39 +0100 References: <1346099868-7774-1-git-send-email-meadori@codesourcery.com> <201208281358.23742.paul@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-ID: <201208281432.40361.paul@codesourcery.com> Subject: Re: [Qemu-devel] [PATCH v1 3/4] hw: Deduce the default machine from the specified CPU model List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Meador Inge , qemu-devel@nongnu.org > >> Just to pick an obvious example, you can't stick a core > >> which supports VFPv4 (the A15 is the only one we have) into > >> the integratorcp > > > > Yes you can. > > No you can't. integratorcp.c doesn't create the parts of the CPU > which live in QEMU's 'a15mpcore_priv' device, so the resulting > mess is liable to just fall over. If anybody reports bugs in > QEMU in such a configuration I will tell them to go away and > use a supported configuration instead. The A15 core itself will work just fine. The core is completely independent of the interrupt controller. Unlike the M profile cores where the NVIC is inherently part of the CPU exception handling mechanism. Paul