From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53906) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjUY1-0000HI-Ie for Qemu-devel@nongnu.org; Wed, 29 Oct 2014 10:48:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XjUXv-000578-B3 for Qemu-devel@nongnu.org; Wed, 29 Oct 2014 10:48:29 -0400 Received: from cantor2.suse.de ([195.135.220.15]:40459 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjUXv-000574-4P for Qemu-devel@nongnu.org; Wed, 29 Oct 2014 10:48:23 -0400 Message-ID: <5450FE34.9060907@suse.de> Date: Wed, 29 Oct 2014 15:48:20 +0100 From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= MIME-Version: 1.0 References: <2753E2F1-FF07-467C-8DCC-569A5BCDA915@livius.net> <5200B6C9-6E30-4B71-9DEB-42BBCD873FC9@livius.net> <0ECC542D-7CF1-4D17-B689-46DF4CCE8F7D@livius.net> <6D1EF190-C2DB-461E-8C6B-F8C62FC167CE@livius.net> <0B379F7E-389F-4A60-9054-B40873694CB9@livius.net> <593EFF26-1CFD-44AF-BD34-BB99F39B5A92@livius.net> <5450EB82.3000205@codeaurora.org> In-Reply-To: <5450EB82.3000205@codeaurora.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Better Cortex-M support? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christopher Covington Cc: Peter Maydell , QEMU Developers , Liviu Ionescu Am 29.10.2014 um 14:28 schrieb Christopher Covington: > On 10/28/2014 01:08 PM, Peter Maydell wrote: >> On 28 October 2014 16:38, Liviu Ionescu wrote: >>> I'm not sure what the QEMU definition of '-machine' stands for, a dev= ice >>> or a board, but I think that the ARM definitions are good candidates = for >>> QEMU emulation names. >> >> -machine specifies a board name. We don't care how you build the binar= y >> for the board or what library you choose to use for hardware abstracti= on. >> >>> once the core Cortex-M emulation is fully functional, it should be >>> easier to add support for specific devices, by configuring some of >>> the parameters (flash/ram, add some peripherals, etc). >> >> QEMU doesn't conveniently support runtime flexible specification >> of what is present in an emulated board (beyond very basic things >> like "how much RAM"). What the .c file in the QEMU sources defines >> is what you get. >=20 > I've sometimes thought it might be cool if QEMU could consume a DTB and > emulate whatever is described, assuming the devices and configurations = are > supported. I've yet to come up with a real problem to motivate this > "solution", though. Xilinx already implemented something along those lines in their branch. Cheers, Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=C3=B6rffer; HRB 16746 AG N=C3=BC= rnberg