xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth@xen.org>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
	"Artem Mygaiev" <artem.mygaiev@globallogic.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"Andrii Tseglytskyi" <andrii.tseglytskyi@globallogic.com>
Subject: Re: [Need Input] (informal) Automotive PV drivers subproject request
Date: Wed, 04 Jun 2014 16:21:00 +0100	[thread overview]
Message-ID: <538F395C.2000400@xen.org> (raw)
In-Reply-To: <538F2EFD.1020909@citrix.com>

 > Which allows them to be imported/shared with other OSes. Could you 
consider
 > releasing the Linux drivers under this kind of license?

@Roger: Can you explain why this is a good idea? Apart from consitency
I think I know, but am not 100% sure. I suppose there are benefits for 
the likes of MiniOS, BSD, ...

Lars

On 04/06/2014 15:36, Roger Pau Monné wrote:
> On 04/06/14 15: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.
> Hello,
>
> Most of the Xen PV frontends/backends inside of the Linux kernel are
> under a dual-license like the following (this one is from blkfront):
>
>   * This program is free software; you can redistribute it and/or
>   * modify it under the terms of the GNU General Public License version 2
>   * as published by the Free Software Foundation; or, when distributed
>   * separately from the Linux kernel or incorporated into other
>   * software packages, subject to the following license:
>   *
>   * Permission is hereby granted, free of charge, to any person obtaining a copy
>   * of this source file (the "Software"), to deal in the Software without
>   * restriction, including without limitation the rights to use, copy, modify,
>   * merge, publish, distribute, sublicense, and/or sell copies of the Software,
>   * and to permit persons to whom the Software is furnished to do so, subject to
>   * the following conditions:
>   *
>   * The above copyright notice and this permission notice shall be included in
>   * all copies or substantial portions of the Software.
>   *
>   * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
>   * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
>   * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
>   * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
>   * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
>   * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
>   * IN THE SOFTWARE.
>
> Which allows them to be imported/shared with other OSes. Could you
> consider releasing the Linux drivers under this kind of license?
>
> Thanks, Roger.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2014-06-04 15:21 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   ` Lars Kurth [this message]
2014-06-04 15:34     ` [Need Input] (informal) Automotive PV drivers subproject request Roger Pau Monné
2014-06-05 13:07       ` Artem Mygaiev
2014-06-05 13:17 ` Automotive PV drivers project request David Vrabel
2014-06-05 13:22   ` 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=538F395C.2000400@xen.org \
    --to=lars.kurth@xen.org \
    --cc=andrii.tseglytskyi@globallogic.com \
    --cc=artem.mygaiev@globallogic.com \
    --cc=roger.pau@citrix.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).