From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54103) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VQdfn-0000pO-Vf for qemu-devel@nongnu.org; Mon, 30 Sep 2013 09:38:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VQdfg-0001OF-36 for qemu-devel@nongnu.org; Mon, 30 Sep 2013 09:38:03 -0400 Received: from cantor2.suse.de ([195.135.220.15]:38245 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VQdff-0001O5-Tn for qemu-devel@nongnu.org; Mon, 30 Sep 2013 09:37:56 -0400 Message-ID: <52497EB0.7020906@suse.de> Date: Mon, 30 Sep 2013 15:37:52 +0200 From: =?windows-1252?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <005f01cebdb3$131a9d30$394fd790$@gmail.com> In-Reply-To: <005f01cebdb3$131a9d30$394fd790$@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Minimal Qemu build for Plan9 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ashish Kaila , qemu-devel@nongnu.org Cc: maneets@andrew.cmu.edu Hi, Am 30.09.2013 10:00, schrieb Ashish Kaila: > I am a graduate student from CMU and currently working on trying to por= t > Qemu on plan9. I was trying to initially build a minimal Qemu with the > least set of devices that are necessary to support a machine, however I > noticed that I couldn=92t understand some of the dependencies such as > requiring an audio driver during initialization. I am currently trying > to port just the i386-softmmu version of Qemu to plan9 to keep things > simple, here I noticed that pc_init1() initializes a host of devices o= n > the PCI bus like the NIC card etc and was wondering if there is a bare > minimum set of devices that Qemu needs to be built with ? Configuring with --target-list=3Di386-softmmu should already give you a minimal set of devices, omitting those that are irrelevant for x86 but including a few optional ones. However I don't understand why devices emulated in C code would pose a porting problem for you? If the code is not using portable POSIX constructs or suitable #ifdefs then please post patches to fix that rather than working around those type of things. > Additionally if someone could point me to a to-do list of things to loo= k > out for while porting Qemu on a new platform (new OS/hardware), I would > be extremely grateful. osdep.c and related files come to mind, configure obviously. 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