qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 20 Jan 2014 17:22:29 +0100	[thread overview]
Message-ID: <20140120162229.GA3446@stefanha-thinkpad> (raw)
In-Reply-To: <CACXtFMh0nKbARsuUn3odD7S2uP5noGDup0mm8eSVASbwX3hprw@mail.gmail.com>

On Sat, Jan 18, 2014 at 09:19:43AM -0800, rajan pathak wrote:
> I am looking forward to emulate single-chip Ethernet controller.
> 
> I can find some of its source code online and it has two main part Ethernet
> PHY (any 1GB SGMII compatible)
> and Ethernet MAC .
> 
> So ,DO I need to simply put the corresponding source files of PHY and MAC
> in hw/net directory of QEMU?

I'm not sure what you mean.  Do you have source code for QEMU emulation
of the network card?

If you have some other source code like a driver for the card, or
emulation for the card but not for QEMU, then a lot more work would be
necessary to emulate the card in QEMU.

> Also ,do I need to take care of underlying Ethernet controller(of my
> machine where I am trying to do this) from
> Broadcom in any way?

QEMU uses mechanisms to send raw packets from userspace, like the
tun/tap driver that many OSes have.  Therefore the physical NIC doesn't
matter, it's abstracted by the tun/tap interface that the host kernel
provides.

  reply	other threads:[~2014-01-21 21:09 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 [this message]
2014-01-22 13:00       ` rajan pathak
2014-01-22 15:58         ` Stefan Hajnoczi

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=20140120162229.GA3446@stefanha-thinkpad \
    --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).