All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: David Herrmann <dh.herrmann@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	Ken Phillis Jr <kphillisjr@gmail.com>
Subject: Re: [PATCH 0/2] drm: add SimpleDRM driver
Date: Fri, 05 Aug 2016 11:28:36 +0300	[thread overview]
Message-ID: <87a8groc0b.fsf@intel.com> (raw)
In-Reply-To: <CANq1E4T-7c33svG-WF9w-pjJN5d3vv4CtW9Gg0+DXOV1HwD3HA@mail.gmail.com>

On Thu, 04 Aug 2016, David Herrmann <dh.herrmann@gmail.com> wrote:
> Hi
>
> On Thu, Aug 4, 2016 at 10:01 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Thu, Aug 04, 2016 at 02:50:37PM -0500, Ken Phillis Jr wrote:
>>> I believe this driver is extremely useful, and I see possible issues with
>>> the fact that the driver is GPL Only. This driver is critical for devices
>>> that lack a proper DRM driver, and locking it into GPL Only could lead to
>>> issues with porting the system over to platforms like FreeBSD,
>>> DragonFlyBSD, etc.  Is there any chance the code placed in the
>>> "drivers/gpu/drm/simpledrm" folder be placed under a more permissive
>>> license setup. I would suggest using MIT[1], BSD 2-Clause[2], or BSD
>>> 3-clause[3]. Also as a quick note it is possible to enable this under a
>>> dual-license setup with GPLv2/BSD-3 Clause. An example a dual licensed
>>> driver is the Intel iwlwifi driver ( see:
>>> drivers/net/wireless/intel/iwlwifi/iwl-8000.c )
>>
>> tbh, most if not all arm drivers are gpl only, and due to code sharing and
>> refactoring I'd say a lot of that has leaked all over drm. IANAL and all
>> that, but personally I believe that the entire idea of drm being MIT is
>> walking on ever thinner ice. And personally I'm not going to extend effort
>> to slow this down or prevent it outright, since I think all that code
>> sharing with arm folks is extremely beneficial for everyone. At least here
>> on Linux.
>> -Daniel
>
> On top of that: Feel free to copy SimpleDRM in any way possible.
> Consider my original implementation public domain.

N.b. the improvements by others on top of that, at least once included
in the kernel tree, will not be public domain. IANAL etc.

BR,
Jani.


>
> Thanks
> David
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-08-05  8:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 19:50 [PATCH 0/2] drm: add SimpleDRM driver Ken Phillis Jr
2016-08-04 20:01 ` Daniel Vetter
2016-08-04 20:07   ` David Herrmann
2016-08-04 23:34     ` Ken Phillis Jr
2016-08-05  8:28     ` Jani Nikula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-08-04 14:03 Noralf Trønnes
2016-08-04 14:03 ` Noralf Trønnes
2016-08-04 14:15 ` Luc Verhaegen
2016-08-04 14:15   ` Luc Verhaegen
2016-08-04 15:08   ` Daniel Vetter
2016-08-04 15:34     ` Luc Verhaegen
2016-08-04 15:44       ` David Herrmann
2016-08-04 15:44         ` David Herrmann
2016-08-04 15:59         ` Luc Verhaegen
2016-08-04 17:10           ` Daniel Vetter
2016-08-04 18:08     ` One Thousand Gnomes
2016-08-04 18:08       ` One Thousand Gnomes
2016-08-04 16:58   ` Noralf Trønnes
2016-08-04 16:58     ` Noralf Trønnes
2016-08-04 18:12     ` Luc Verhaegen
2016-08-05  7:18       ` Hans de Goede
2016-08-04 14:36 ` Daniel Vetter
2016-08-04 17:30   ` Noralf Trønnes

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=87a8groc0b.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dh.herrmann@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kphillisjr@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 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.