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: Sat, 18 May 2013 15:55:36 +0200	[thread overview]
Message-ID: <51978858.3010205@redhat.com> (raw)
In-Reply-To: <F4D6D4ABB762B1409DB18951E7BD0E105073FDAF@SN2PRD0410MB358.namprd04.prod.outlook.com>

Il 17/05/2013 22:29, Rempel, Cynthia ha scritto:> Hi Qemu-Devel,
> I am part of the RTEMS development community.
> 
> The RTEMS development community is considering having a Google Summer
> of Code student test LinCAN on a simulated RTEMS target board using
> QEMU, and have some questions:
> 
> 1. What guidelines should the student follow when writing the device > simulation, so the device simulation will be "upstreamed"/accepted by
> the QEMU project?
> 2. Is there additional documentation on how to write a device
> simulation?

Unfortunately there is not much documentation.  Would this interact with
something in the host (e.g. emulating the sensors)?  Or is it like USB
where QEMU has emulation of both controllers and devices (e.g. tablets
or storage)?

There are lots of different devices in QEMU; a student with good code
reading abilities should be able to find what he needs, but if you are
writing an entire emulation subsystem it's going to be a lot of work.

> 3. Could we get a co-mentor from qemu-devel to help the student with
> technical questions, or if not, would this mailing list be willing to
> help us out?

I don't know if someone is available to mentor the project, but the
mailing list would surely be of help.

Paolo

  reply	other threads:[~2013-05-18 13:55 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 [this message]
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
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=51978858.3010205@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).