From: Stefan Hajnoczi <stefanha@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Valentine Sinitsyn <valentine.sinitsyn@gmail.com>,
Pavel Pisa <pisa@cmp.felk.cvut.cz>,
stefandoesinger@gmail.com, Pranith Kumar <bobby.prani@gmail.com>
Subject: [Qemu-devel] Mentor Summit notes
Date: Tue, 1 Nov 2016 02:31:49 -0700 [thread overview]
Message-ID: <CAJSP0QWjPERYwRUUYZYMqVyTJRauMb5q03xoOeA9BhPLdPNa_Q@mail.gmail.com> (raw)
Valentine and I attended Google Summer of Code Mentor Summit on behalf
of QEMU. The event brings together GSoC mentors from all
participating organizations.
A lot of people benefit from QEMU and told me so at the summit. There
are also many who hadn't heard of QEMU before.
I gave a lightning talk about Pranith Kumar's MTTCG project since it's
a good example of a QEMU project:
https://docs.google.com/presentation/d/1kidkMp4k-ak180aI-eZQfWuIEpQoeY-0N-oqt9eZo20/edit?usp=sharing
Feedback from Mentor Summit:
1. Pavel Pisa wants to upstream CAN bus support. I asked him to
rebase and submit the patches. Please take a look when patches are
posted.
2. RTEMS mentioned they sometimes rely on out-of-tree QEMU targets and
want to encourage authors to upstream their code. Xilinx was
mentioned in particular.
3. Wine brainstormed x86 Windows applications on ARM using
qemu-user-x86 + wine (x86). Probably requires multithreaded TCG.
Work required to get OpenGL and other native features passed through.
Talk to Stefan Dösinger (Wine) if interested.
Stefan
next reply other threads:[~2016-11-01 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 9:31 Stefan Hajnoczi [this message]
2016-11-01 16:21 ` [Qemu-devel] Mentor Summit notes Alistair Francis
2016-11-07 10:48 ` Stefan Hajnoczi
2016-11-07 19:18 ` Alistair Francis
2016-11-04 9:35 ` KONRAD Frederic
2016-11-07 10:48 ` 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=CAJSP0QWjPERYwRUUYZYMqVyTJRauMb5q03xoOeA9BhPLdPNa_Q@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=bobby.prani@gmail.com \
--cc=pisa@cmp.felk.cvut.cz \
--cc=qemu-devel@nongnu.org \
--cc=stefandoesinger@gmail.com \
--cc=valentine.sinitsyn@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).