From: Stefan Hajnoczi <stefanha@gmail.com>
To: rajan pathak <rajanpatha34@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Simulate different network card vendors
Date: Wed, 22 Jan 2014 09:58:48 -0600 [thread overview]
Message-ID: <20140122155848.GA11886@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CACXtFMgEQu=PrFjeY1VrKbnTZc7nwxgf0=FZ7R1q9Bduc0iexA@mail.gmail.com>
On Wed, Jan 22, 2014 at 06:30:42PM +0530, rajan pathak wrote:
> But I don't know what are the steps to emulate it for QEMU.
>
> Would you suggest me some links where I can get some idea of how emulating
> a Device for QEMU?
Look at existing code in hw/net/*.c, for example e1000.c.
Stefan
prev parent reply other threads:[~2014-01-22 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 7:57 [Qemu-devel] Simulate different network card vendors rajan pathak
2014-01-16 6:29 ` Stefan Hajnoczi
2014-01-18 17:19 ` rajan pathak
2014-01-20 16:22 ` Stefan Hajnoczi
2014-01-22 13:00 ` rajan pathak
2014-01-22 15:58 ` 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=20140122155848.GA11886@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rajanpatha34@gmail.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).