From: "Rémi Denis-Courmont" <remi@remlab.net>
To: linux-media@vger.kernel.org
Subject: Re: LinuxTV ported to Windows
Date: Fri, 2 Dec 2011 20:03:28 +0200 [thread overview]
Message-ID: <201112022003.28737.remi@remlab.net> (raw)
In-Reply-To: <CAGoCfiwShvPSgAPHKaxj=sMG-Fs9RdH0_3mLHYWuY96Z33AOag@mail.gmail.com>
Hello,
A GPL troll, as the "Vicious Nokia Employee [that got] VLC Removed from Apple
App Store" I cannot resist...
Le mercredi 30 novembre 2011 19:23:26 Devin Heitmueller, vous avez écrit :
> 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.
If you have any doubt, I would suggest you ask the SFLC. They tend to give
valuable insights into that sort of problems. It might be intricate and/or not
what you want to hear from them though (Been there done that).
> 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.
As long as the distributed binaries do not include any GPL-incompatible code
(presumably from Microsoft), there should be no GPL contamination problem. So
it boils down to whether the driver binary has non-GPL code in it. I don't see
how the license of the Windows code is relevant, so long as NetUp is not
distributing the Windows OS alongside the driver (or vice versa).
And while I do not know the Windows DDK license, I doubt it cares much about
the driver license, so long as Microsoft does not need to distribute nor
certify the driver.
There may however be problems with the toolchain. The driver binary must be
recompilable with just the GPL'd source code and "anything that is normally
distributed with the operating system". VisualStudio is not distributed with
Windows. In fact, it is sold as a separate product, except for restrictive
freeware versions.
So unless this driver can be compiled with a GPL-compatible toolchain (and the
toolchain is provided by NetUp), it might not be possible to distribute binary
copies of the driver.
Then again, I am not a laywer. Someone that cares, please ask SFLC or friends.
--
Rémi Denis-Courmont
http://www.remlab.net/
http://fi.linkedin.com/in/remidenis
next prev parent reply other threads:[~2011-12-02 18:03 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
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 [this message]
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=201112022003.28737.remi@remlab.net \
--to=remi@remlab.net \
--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.