qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Brajesh Sharma <s.brajesh@mobiveil.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Regarding QEMU API's to interact with hardware peripherals like Memory
Date: Fri, 14 Feb 2014 16:05:06 +0100	[thread overview]
Message-ID: <20140214150506.GM17391@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CALJoR0JRShB_1q9ESQqMQr5JTENG2eRgv1xBNRCRcg7U_X787w@mail.gmail.com>

On Wed, Feb 12, 2014 at 12:14:58PM +0530, Brajesh Sharma wrote:
> I am new to Qemu Emulator i need some Info regarding this .  I am working
> on something which needs Qemu to interact with hardware peripherals . I
> want to know what are those API to communicate with hardware and how can i
> find and see them .

Please be specific, otherwise we cannot answer your question.

What piece of hardware?  What are you trying to do?

Stefan

      reply	other threads:[~2014-02-14 15:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  6:44 [Qemu-devel] Regarding QEMU API's to interact with hardware peripherals like Memory Brajesh Sharma
2014-02-14 15:05 ` Stefan Hajnoczi [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=20140214150506.GM17391@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=s.brajesh@mobiveil.com \
    /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).