All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
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>,
	Paolo Bonzini <pbonzini@redhat.com>,
	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 22:15:09 +0200	[thread overview]
Message-ID: <5197E14D.6020408@weilnetz.de> (raw)
In-Reply-To: <F4D6D4ABB762B1409DB18951E7BD0E1050740E6E@SN2PRD0410MB358.namprd04.prod.outlook.com>

Am 18.05.2013 20:24, schrieb Rempel, Cynthia:
>>> 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 following the guidance in:
> http://lists.gnu.org/archive/html/qemu-devel/2011-07/msg00842.html
> increase the probability the device simulation would be committed to qemu?

Yes, I think so.

Here is also some help which shows the fundamental
requirements for new contributions:

http://wiki.qemu.org/Contribute/SubmitAPatch

Are you planning to emulate an existing CAN controller,
or do you want to design a new virtual CAN controller
from scratch?

Regards,
Stefan Weil

  reply	other threads:[~2013-05-18 20:15 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 [this message]
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=5197E14D.6020408@weilnetz.de \
    --to=sw@weilnetz.de \
    --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=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.