From: "Andreas Färber" <afaerber@suse.de>
To: atlas khan <atlaskhan90@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Add a new hardware
Date: Tue, 25 Feb 2014 09:18:51 +0100 [thread overview]
Message-ID: <530C51EB.6000408@suse.de> (raw)
In-Reply-To: <CAN7x1o5SmVJ-8ZnhYiX8HtRybLjxZ855oiVXzMo3PNgGC=kAYw@mail.gmail.com>
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
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2014-02-25 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 9:34 [Qemu-devel] Add a new hardware atlas khan
2014-02-25 8:18 ` Andreas Färber [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=530C51EB.6000408@suse.de \
--to=afaerber@suse.de \
--cc=atlaskhan90@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).