From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55387) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIDEH-0001m3-6s for qemu-devel@nongnu.org; Tue, 25 Feb 2014 03:19:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WIDE8-0001NF-HQ for qemu-devel@nongnu.org; Tue, 25 Feb 2014 03:19:05 -0500 Received: from cantor2.suse.de ([195.135.220.15]:36244 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIDE8-0001N4-Ae for qemu-devel@nongnu.org; Tue, 25 Feb 2014 03:18:56 -0500 Message-ID: <530C51EB.6000408@suse.de> Date: Tue, 25 Feb 2014 09:18:51 +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] Add a new hardware List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: atlas khan , qemu-devel Am 21.02.2014 10:34, schrieb atlas khan: > I am working on project in which we have add support of a board in > QEMU. We have to add some virtual devices in QEMU. The question which > I want to ask that what should I do to add virtual device. And after > adding that device in \hw in which file I have to make changes so that > program access that hardware when it need it. Because the device which > I have to add is the device which is already available, but in our > board, this device has different architecture, so we want our program > to access that file which we have made for our board instead of file > which is already available in QEMU.... Your question sounds slightly confused. Either you want to add a new device, then place it in the appropriate subdirectory of hw/ and add it to Makefile.objs - common-obj-y preferably= . Or you want to enable a device that already exists there to another softmmu target, then you need to edit default-configs/*-softmmu.mak. Otherwise, what does the architecture have to do with the device and why would you want to replace some file? All of this would've been much easier to answer had you actually mentioned which file you are talking about and which board/architecture you are working on! Attaching a patch of what you already have (or short of that posting a link to your public repository) would also help to spot what you're missing. Cheers, 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