All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@linuxtv.org>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Abylay Ospan <aospan@netup.ru>, linux-media@vger.kernel.org
Subject: Re: LinuxTV ported to Windows
Date: Wed, 30 Nov 2011 20:58:40 +0100	[thread overview]
Message-ID: <4ED68AF0.8000903@linuxtv.org> (raw)
In-Reply-To: <CAGoCfiw16bAtPHfrtsDDOBL4BeFnH+zMqcz9wBitGGSq_RZtJA@mail.gmail.com>

On 30.11.2011 20:33, Devin Heitmueller wrote:
> On Wed, Nov 30, 2011 at 1:02 PM, Andreas Oberritter <obi@linuxtv.org> wrote:
>>> Am I the only one who thinks this is a legally ambigious grey area?
>>> Seems like this could be a violation of the GPL as the driver code in
>>> question links against a proprietary kernel.
>>
>> Devin, please! Are you implying that the windows kernel becomes a
>> derived work of the driver, or that it's generally impossible to publish
>> windows drivers under the terms of the GPL?
> 
> The simple answer is that "I don't know".  I'm not a lawyer (and as
> far as I know, neither are you).  Nor have I researched the topic to
> significant lengths.  That said though, whether it was the intention
> of either copyright holder it's entirely possible that the two
> software licenses are simply incompatible.  For example, while both
> the Apache group and the FSF never really intended to prevent each
> others' software from being linked against each other, the net effect
> is still that you cannot redistribute such software together since the
> Apache license is incompatible with the GPL.

Neither is Abylay distributing Windows together with this driver, nor is
this driver a library Windows links against, i.e. Windows is able to run
with this driver removed.

>>> I don't want to start a flame war, but I don't see how this is legal.
>>> And you could definitely question whether it goes against the
>>> intentions of the original authors to see their GPL driver code being
>>> used in non-free operating systems.
>>
>> The GPL doesn't cover such intentions.
> 
> This isn't necessarily true.  Anybody who has written a library and
> released it under the GPL instead of the LGPL has made a conscious
> decision that the library is only to be used by software that is GPL
> compatible.  By their actions they have inherently forbidden it's use
> by non-free software.  You could certainly make the same argument
> about a driver -- that they authors intent was to ensure that it only
> be linked against other free software.

That's something completely different than "being used in non-free
operating systems" and not necessarily comparable to a driver, which
implements a well-defined interface.

The point I'm trying to make: Someone made a presumably nice open source
port to a new platform and the first thing you're doing is to play the
GPL-has-been-violated-card, even though you're admitting that you don't
know whether any right is being violated or not. Please don't do that.
It's not very encouraging to someone who just announced free software.

Regards,
Andreas

  reply	other threads:[~2011-11-30 19:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 16:39 LinuxTV ported to Windows Abylay Ospan
2011-11-30 17:23 ` Devin Heitmueller
2011-11-30 18:02   ` Andreas Oberritter
2011-11-30 19:33     ` Devin Heitmueller
2011-11-30 19:58       ` Andreas Oberritter [this message]
2011-11-30 20:11         ` Devin Heitmueller
2011-12-01 19:42         ` Laurent Pinchart
2011-12-01 21:18           ` Steven Toth
2011-12-01 23:10             ` Andreas Oberritter
2011-12-01 23:43               ` Steven Toth
2011-12-01 22:31           ` Andreas Oberritter
2011-12-01  7:05   ` Abylay Ospan
2011-12-02 18:03   ` Rémi Denis-Courmont
2011-12-02 22:10     ` Patrick Dickey
2011-11-30 18:46 ` Walter Van Eetvelt
2011-12-01  7:05   ` Abylay Ospan
  -- strict thread matches above, loose matches on Subject: below --
2011-12-02  9:35 Issa Gorissen
2011-12-02 12:48 ` Felipe Magno de Almeida

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=4ED68AF0.8000903@linuxtv.org \
    --to=obi@linuxtv.org \
    --cc=aospan@netup.ru \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.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 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.