From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Semwal, Sumit" <sumit.semwal@ti.com>,
Robert Morell <rmorell@nvidia.com>, Arnd Bergmann <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"sumit.semwal@linaro.org" <sumit.semwal@linaro.org>
Subject: Re: [PATCH] dma-buf: Use EXPORT_SYMBOL
Date: Wed, 25 Jan 2012 11:48:55 -0200 [thread overview]
Message-ID: <4F200847.3040806@redhat.com> (raw)
In-Reply-To: <4F2007A8.2080301@redhat.com>
Em 25-01-2012 11:46, Mauro Carvalho Chehab escreveu:
> Em 25-01-2012 10:30, Alan Cox escreveu:
>>> Technically speaking, is there no way that the EXPORT_SYMBOL_GPLed
>>> symbols can be used by the binary blobs, possibly with an open-sourced
>>> shim which provides the buffer-sharing interface to the binary blobs?
>>> Are there any reasons to not consider this approach?
>>
>> The GPL requires all the code of a work is source. All of it, no shims no
>> magic glue. EXPORT_SYMBOL isn't an indication you can use it for binary
>> modules. The GPL licence is quite clear on what is covered.
>
> Agreed. Such patch won't change anything. The discussions, patch reviews,
> etc were under the assumption that the code will be GPL'd, plus the
> subsystems that are exposed by this interface also assumes that.
> Any trials to circumvent it seem to violate Kernel owner's rights.
In time, let me rephrase it:
Any trial to circumvent it seems to be an attempt to violate Kernel owner's rights.
>
>> Since you've asked this I'm advised by my lawyer to respond to all such
>> assumptions of legality of binary modules...
>>
>> For a Linux kernel containing any code I own the code is under the GNU
>> public license v2 (in some cases or later), I have never given permission
>> for that code to be used as part of a combined or derivative work which
>> contains binary chunks. I have never said that modules are somehow
>> magically outside the GPL and I am doubtful that in most cases a work
>> containing binary modules for a Linux kernel is compatible with the
>> licensing, although I accept there may be some cases that it is.
>>
>> Alan
>
> I second Alan:
> For a Linux kernel containing any code I own the code is under the GNU
> public license v2 (in a few cases, where explicitly said GPLv2 or later
> or dual GNU/BSD), I have never given permission for that code to be
> used as part of a combined or derivative work which contains binary chunks.
>
> Regards,
> Mauro.
next prev parent reply other threads:[~2012-01-25 13:49 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 15:06 [git pull] dma-buf tree Dave Airlie
2012-01-08 22:08 ` Linus Torvalds
2012-01-09 6:44 ` Sumit Semwal
2012-01-13 9:08 ` Dave Airlie
2012-01-13 9:38 ` Sumit Semwal
2012-01-13 9:40 ` Dave Airlie
2012-01-18 0:08 ` Expanding the use of DMA buffers in 3.3 Robert Morell
2012-01-18 0:08 ` [PATCH] dma-buf: Use EXPORT_SYMBOL Robert Morell
2012-01-18 9:10 ` Semwal, Sumit
2012-01-18 12:14 ` Arnd Bergmann
2012-01-18 12:21 ` Dave Airlie
2012-01-18 12:21 ` Dave Airlie
2012-01-18 13:55 ` Ilija Hadzic
2012-01-18 13:55 ` Ilija Hadzic
2012-01-18 14:00 ` Dave Airlie
2012-01-19 1:11 ` Robert Morell
2012-01-18 14:39 ` Arnd Bergmann
2012-01-18 14:39 ` Arnd Bergmann
2012-01-18 12:23 ` Mauro Carvalho Chehab
2012-01-19 7:26 ` Dave Airlie
2012-01-20 18:04 ` Robert Morell
2012-01-20 18:12 ` Konrad Rzeszutek Wilk
2012-01-21 17:32 ` Daniel Vetter
2012-01-25 5:34 ` Semwal, Sumit
2012-01-25 12:30 ` Alan Cox
2012-01-25 12:30 ` Alan Cox
2012-01-25 13:46 ` Mauro Carvalho Chehab
2012-01-25 13:48 ` Mauro Carvalho Chehab [this message]
2012-01-18 11:48 ` Alan Cox
2012-02-19 21:20 ` Rob Clark
2012-01-18 11:53 ` Expanding the use of DMA buffers in 3.3 Alan Cox
2012-01-18 11:53 ` Alan Cox
2012-01-19 6:43 ` Pekka Enberg
2012-01-19 6:43 ` Pekka Enberg
2012-10-10 15:56 [PATCH] dma-buf: Use EXPORT_SYMBOL Robert Morell
2012-10-10 15:56 ` Robert Morell
2012-10-10 16:23 ` Mauro Carvalho Chehab
2012-10-10 16:23 ` Mauro Carvalho Chehab
2012-10-10 18:17 ` Alan Cox
2012-10-10 21:02 ` Rob Clark
2012-10-11 6:57 ` Hans Verkuil
2012-10-11 6:57 ` Hans Verkuil
2012-10-11 11:34 ` Alan Cox
2012-10-11 11:34 ` Alan Cox
2012-10-11 11:36 ` Hans Verkuil
2012-10-11 12:10 ` Hans Verkuil
2012-10-11 12:52 ` Laurent Pinchart
2012-10-16 21:22 ` Robert Morell
2012-10-17 9:53 ` Alan Cox
2012-10-10 23:22 ` Dave Airlie
2012-10-11 1:11 ` Mauro Carvalho Chehab
2012-10-11 2:50 ` Dave Airlie
2012-10-11 11:37 ` Alan Cox
2012-10-11 7:20 ` Hans Verkuil
2012-10-11 7:51 ` Hans Verkuil
2012-10-11 9:10 ` Maarten Lankhorst
2012-10-11 11:13 ` Mauro Carvalho Chehab
2012-10-11 13:47 ` Rob Clark
2012-10-11 14:55 ` Mauro Carvalho Chehab
2012-10-11 11:30 ` Alan Cox
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=4F200847.3040806@redhat.com \
--to=mchehab@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmorell@nvidia.com \
--cc=sumit.semwal@linaro.org \
--cc=sumit.semwal@ti.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.