From: David Vrabel <david.vrabel@citrix.com>
To: Artem Mygaiev <artem.mygaiev@globallogic.com>, xen-devel@lists.xen.org
Subject: Re: Automotive PV drivers project request
Date: Thu, 5 Jun 2014 14:17:44 +0100 [thread overview]
Message-ID: <53906DF8.2050403@citrix.com> (raw)
In-Reply-To: <CALQdcA+XazbLamek3H89XafhaHZS-XixfOjicsj0bvgM2WchAA@mail.gmail.com>
On 04/06/14 14:04, Artem Mygaiev wrote:
> As a part of effort on bringing Xen into Automotive (and thus Embedded)
> space, we are working on a set of PV drivers needed to share
> peripherals between domains.
> * PV audio - new driver using ALSA
> * PV USB - based on old existing PV USB solution
> * PV framebuffer - modifications and improvements for existing FB
> * PV events - new driver for sharing HIDs across domains (touchscreen,
> keyb, etc.)
> This list is not final, other things are to be added later on. Each
> driver consists, obviously, of frontend and backend which may be
> implemented for different OSes. So far only Linux is supported, QNX is
> wip, ArcCore or similar being considered. Due to this, each driver has
> following structure (sample):
> /pv_audio
> /linux-alsa-be
> /linux-fe
> /qnx-be
> /qnx-fe
> Linux kernel code is developed under GPLv2 license, userspace
> components like some backends are under Apache 2 license, so can be
> integrated into software with commercial licenses. QNX and other OSes
> will have licenses that are required by corresponding regulations, some
> may be not open nevertheless we tend to make all parts of the code
> available to the Xen community.
I don't want to see Linux drivers languishing in a sub-project -- they
should all be merged into Linux proper.
David
next prev parent reply other threads:[~2014-06-05 13:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 13:04 Automotive PV drivers project request Artem Mygaiev
2014-06-04 14:22 ` [Need Input] (informal) Automotive PV drivers subproject request Lars Kurth
2014-06-04 16:35 ` Dario Faggioli
2014-06-05 12:47 ` Artem Mygaiev
2014-06-05 13:32 ` Dario Faggioli
2014-06-06 8:59 ` Ian Campbell
2014-06-06 13:05 ` Lars Kurth
2014-06-06 15:08 ` Ian Campbell
2014-06-06 19:49 ` Artem Mygaiev
2014-06-06 22:01 ` Dario Faggioli
2014-06-09 10:18 ` Stefano Stabellini
2014-06-09 12:25 ` Lars Kurth
2014-06-09 12:30 ` Ian Campbell
2014-06-09 13:14 ` Lars Kurth
2014-06-09 12:37 ` Lars Kurth
2014-06-09 13:12 ` Ian Jackson
2014-06-09 13:31 ` Lars Kurth
2014-06-10 14:22 ` Artem Mygaiev
2014-06-10 14:51 ` Lars Kurth
2014-06-09 12:15 ` Lars Kurth
2014-06-11 11:37 ` Lars Kurth
2014-06-04 14:36 ` Automotive PV drivers project request Roger Pau Monné
2014-06-04 15:21 ` [Need Input] (informal) Automotive PV drivers subproject request Lars Kurth
2014-06-04 15:34 ` Roger Pau Monné
2014-06-05 13:07 ` Artem Mygaiev
2014-06-05 13:17 ` David Vrabel [this message]
2014-06-05 13:22 ` Automotive PV drivers project request Artem Mygaiev
2014-06-10 12:38 ` David Vrabel
2014-06-10 14:09 ` Lars Kurth
2014-06-10 14:18 ` Artem Mygaiev
2014-06-11 10:10 ` Stefano Stabellini
2014-06-11 15:08 ` Automotive PV drivers project request (need more input) Lars Kurth
2014-06-12 9:34 ` Stefano Stabellini
2014-06-12 13:43 ` Paul Durrant
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=53906DF8.2050403@citrix.com \
--to=david.vrabel@citrix.com \
--cc=artem.mygaiev@globallogic.com \
--cc=xen-devel@lists.xen.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).