From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46217) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6SCk-0005NX-0c for qemu-devel@nongnu.org; Thu, 23 Jan 2014 16:52:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W6SCe-00036f-Ls for qemu-devel@nongnu.org; Thu, 23 Jan 2014 16:52:53 -0500 Received: from cantor2.suse.de ([195.135.220.15]:51446 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6SCe-00036b-9I for qemu-devel@nongnu.org; Thu, 23 Jan 2014 16:52:48 -0500 Message-ID: <52E18F2B.7090201@suse.de> Date: Thu, 23 Jan 2014 22:52:43 +0100 From: =?ISO-8859-1?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Emulating Ethernet controller based on Cortex-A15 platforms List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: rajan pathak Cc: Peter Maydell , QEMU Developers , Stefan Hajnoczi Am 23.01.2014 21:02, schrieb rajan pathak: >> I'm not clear what you're trying to do here; could >> you try rephrasing your question? Are you just trying >> to use the existing working QEMU emulation of a >> Cortex-A15 board and ethernet controller, or to do >> something else? >=20 > To be very specific I am trying to emulate Ethernet controller of > KeyStone 2 device from TI >=20 > http://processors.wiki.ti.com/index.php/MCSDK_User_Guide_for_KeyStone_I= I >=20 > It is based on CortexA-15 Processor series. So I thought I can use > vexpress_defconfig and can call > my Emulated Ethernet controller instead of LAN9118 from vexpress.c. >=20 > After that I will place my Emulated Ethernet controller code(which > haven't started) inside hw/net . >=20 > Is the right way to go forward? No, it isn't. If you want to emulate the KeyStone II SoC, then please do just that. You will find recent examples on the list of new SoCs that have been added, including sunxi/A10 and DIGIC. So, the Ethernet controller would be a new device in hw/net/, it is initialized by a SoC device in hw/arm/ and to use it you need a standard machine definition, such as the EVMK2Hx in your case (some evaluation/reference board rather than custom industry boards). Then test that code using a Linux (or firmware or other OS) that runs on the real board. Regards, Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg