From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: linux-media@vger.kernel.org
Subject: Re: [RFC] vtunerc - virtual DVB device driver
Date: Tue, 21 Jun 2011 12:06:19 -0300 [thread overview]
Message-ID: <4E00B36B.5010806@redhat.com> (raw)
In-Reply-To: <87wrgf8c7i.fsf@nemi.mork.no>
Em 21-06-2011 11:56, Bjørn Mork escreveu:
> Devin Heitmueller <dheitmueller@kernellabs.com> writes:
>
>> The introduction of this patch makes it trivial for a third party to
>> provide closed-source userland support for tuners while reusing all
>> the existing GPL driver code that makes up the framework.
>
> Wouldn't it be just as trivial to bundle the closed-source tuner support
> with this patch or a similar GPL licensed driver? This doesn't change
> anything wrt closed source drivers.
Yes, but adding some code into a GPL licensed code is derivative work,
The end result is also covered by GPL (not only the kernelspace, but also
the userspace counterpart). If some company is doing things like that
and not providing the entire driver under GPL, if going to court, the judge
will likely consider this as an explicitly attempt to violate the legal
property of someone's else's copyright.
Mauro
next prev parent reply other threads:[~2011-06-21 15:06 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 0:10 [RFC] vtunerc - virtual DVB device driver HoP
2011-06-20 17:37 ` Rémi Denis-Courmont
2011-06-20 17:41 ` Devin Heitmueller
2011-06-20 18:17 ` HoP
2011-06-20 18:24 ` Devin Heitmueller
2011-06-20 19:10 ` Sébastien RAILLARD (COEXSI)
2011-06-20 19:36 ` Devin Heitmueller
2011-06-20 19:56 ` HoP
2011-06-20 20:02 ` Devin Heitmueller
2011-06-20 20:24 ` HoP
2011-06-20 20:47 ` Mauro Carvalho Chehab
2011-06-20 21:31 ` HoP
2011-06-21 1:35 ` Mauro Carvalho Chehab
2011-06-21 11:04 ` Andreas Oberritter
2011-06-21 12:05 ` Mauro Carvalho Chehab
2011-06-21 12:34 ` Andreas Oberritter
2011-06-21 12:54 ` Issa Gorissen
2011-06-21 12:34 ` HoP
2011-06-21 12:59 ` Mauro Carvalho Chehab
2011-06-21 13:44 ` Devin Heitmueller
2011-06-21 14:15 ` Andreas Oberritter
2011-06-21 14:34 ` Devin Heitmueller
2011-06-21 14:35 ` Mauro Carvalho Chehab
2011-06-21 15:09 ` Andreas Oberritter
2011-06-21 17:10 ` Mauro Carvalho Chehab
2011-06-21 17:38 ` HoP
2011-06-22 1:06 ` Markus Rechberger
2011-06-22 6:08 ` HoP
2011-06-22 12:17 ` Mauro Carvalho Chehab
2011-06-22 12:30 ` Andreas Oberritter
2011-06-22 12:55 ` Mauro Carvalho Chehab
2011-06-22 13:07 ` Andreas Oberritter
2011-06-22 13:21 ` HoP
2011-06-22 12:37 ` HoP
2011-06-22 13:03 ` Mauro Carvalho Chehab
2011-06-22 13:13 ` Andreas Oberritter
2011-06-22 13:45 ` Mauro Carvalho Chehab
2011-06-22 14:03 ` HoP
2011-06-22 14:23 ` Mauro Carvalho Chehab
2011-06-22 14:24 ` Andreas Oberritter
2011-06-22 15:19 ` Mauro Carvalho Chehab
2011-06-22 15:45 ` Andreas Oberritter
2011-06-22 19:18 ` Rémi Denis-Courmont
2011-06-22 22:24 ` Mauro Carvalho Chehab
2011-06-21 14:56 ` Bjørn Mork
2011-06-21 15:06 ` Mauro Carvalho Chehab [this message]
2011-06-21 14:59 ` Mauro Carvalho Chehab
2011-06-21 17:12 ` Markus Rechberger
2011-06-21 11:41 ` HoP
2011-06-22 16:20 ` Steven Toth
2011-06-20 22:11 ` Bjørn Mork
2011-06-20 22:36 ` HoP
2011-06-20 22:43 ` Devin Heitmueller
2011-06-20 19:40 ` Rémi Denis-Courmont
2011-06-22 17:08 ` Michael Krufky
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=4E00B36B.5010806@redhat.com \
--to=mchehab@redhat.com \
--cc=bjorn@mork.no \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox