qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Rempel, Cynthia" <cynt6007@vandals.uidaho.edu>
Cc: Gedare Bloom <gedare@rtems.org>, Amar Takhar <verm@darkbeer.org>,
	Petr Benes <petben@petben.net>,
	Thomas Doerfler <Thomas.Doerfler@embedded-brains.de>,
	"Sebastian.Huber@embedded-brains.de"
	<Sebastian.Huber@embedded-brains.de>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Jennifer Averett <Jennifer.Averett@oarcorp.com>,
	Chris Johns <chrisj@rtems.org>,
	Cl?udio Silva <claudiodcsilva@gmail.com>,
	Joel Sherrill <joel.sherrill@oarcorp.com>,
	Pavel Pisa <pisa@cmp.felk.cvut.cz>
Subject: Re: [Qemu-devel] Writing a CAN driver for QEMU
Date: Sun, 19 May 2013 14:58:48 +0200	[thread overview]
Message-ID: <5198CC88.1090709@redhat.com> (raw)
In-Reply-To: <F4D6D4ABB762B1409DB18951E7BD0E1050740E6E@SN2PRD0410MB358.namprd04.prod.outlook.com>

Il 18/05/2013 20:24, Rempel, Cynthia ha scritto:
> we want to be able to verify a guest OS's CAN driver has been integrated properly and is sending CAN packets... 
> 
> Perhaps along the lines of two calls:
> qemu-system-arm -hda linux1.img -can student-implemented-device
> qemu-system-arm -hda linux2.img -can student-implemented-device

You would probably use either -net, or -netdev and -device (see
docs/qdev-device-use.txt).

> Then using a network protocol analyzer (such as Wireshark) with a custom filter to recognize CAN packets,
> OR
> qemu-system-arm -hda linux1.img -can student-implemented-device
> then attaching a real CAN device to the host computer and verifying that the output is being recognized be real hardware.

Is this CAN device just an Ethernet device?  QEMU does not support other
link-level protocols.  Adding them would be possible and interesting,
however it would add a bit to the complexity.

> Whichever is more feasible to implement...

Both would be the same.  In the first case, you'd probably use "-netdev
socket" to share a virtual network between two virtual machines.  In the
second, you would use something like "-netdev tap" (again assuming it's
just an Ethernet device).

Paolo

  parent reply	other threads:[~2013-05-19 12:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17 20:29 [Qemu-devel] Writing a CAN driver for QEMU Rempel, Cynthia
2013-05-18 13:55 ` Paolo Bonzini
2013-05-18 18:24   ` Rempel, Cynthia
2013-05-18 20:15     ` Stefan Weil
2013-05-18 21:23       ` Rempel, Cynthia
2013-05-19  0:44         ` Pavel Pisa
2013-05-19  6:58           ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-19  7:23             ` Peter Maydell
2013-05-19  9:21               ` Stefan Weil
2013-05-19 12:58     ` Paolo Bonzini [this message]
2013-05-19 13:19       ` Paolo Bonzini
2013-05-19 16:14         ` Stefan Weil
2013-05-19 18:23     ` Andreas Färber
2013-05-19 19:06       ` Pavel Pisa
2013-05-20 16:15         ` Andreas Färber

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=5198CC88.1090709@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=Jennifer.Averett@oarcorp.com \
    --cc=Sebastian.Huber@embedded-brains.de \
    --cc=Thomas.Doerfler@embedded-brains.de \
    --cc=chrisj@rtems.org \
    --cc=claudiodcsilva@gmail.com \
    --cc=cynt6007@vandals.uidaho.edu \
    --cc=gedare@rtems.org \
    --cc=joel.sherrill@oarcorp.com \
    --cc=petben@petben.net \
    --cc=pisa@cmp.felk.cvut.cz \
    --cc=qemu-devel@nongnu.org \
    --cc=verm@darkbeer.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).