All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Ken Phillis Jr <kphillisjr@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] drm: add SimpleDRM driver
Date: Thu, 4 Aug 2016 22:01:56 +0200	[thread overview]
Message-ID: <20160804200156.GW6232@phenom.ffwll.local> (raw)
In-Reply-To: <CACiKS=TWCsyUrGOVZxkPDgwJ1QMYx8CgA-Ev_3vxXx9qiqBF5g@mail.gmail.com>

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

> 
> 
> [1]https://opensource.org/licenses/mit-license.html
> [2]https://opensource.org/licenses/BSD-2-Clause
> [3]https://opensource.org/licenses/BSD-3-Clause

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


-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-08-04 20:02 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 [this message]
2016-08-04 20:07   ` David Herrmann
2016-08-04 23:34     ` Ken Phillis Jr
2016-08-05  8:28     ` Jani Nikula
  -- 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=20160804200156.GW6232@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --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.