From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Rob Clark <rob@ti.com>, Robert Morell <rmorell@nvidia.com>,
linaro-mm-sig@lists.linaro.org,
Sumit Semwal <sumit.semwal@linaro.org>,
dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] dma-buf: Use EXPORT_SYMBOL
Date: Thu, 11 Oct 2012 12:34:07 +0100 [thread overview]
Message-ID: <20121011123407.63b5ecbe@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <201210110857.15660.hverkuil@xs4all.nl>
> The whole purpose of this API is to let DRM and V4L drivers share buffers for
> zero-copy pipelines. Unfortunately it is a fact that several popular DRM drivers
> are closed source. So we have a choice between keeping the export symbols GPL
> and forcing those closed-source drivers to make their own incompatible API,
> thus defeating the whole point of DMABUF, or using EXPORT_SYMBOL and letting
> the closed source vendors worry about the legality. They are already using such
> functions (at least nvidia is), so they clearly accept that risk.
Then they can accept the risk of ignoring EXPORT_SYMBOL_GPL and
calling into it anyway can't they. Your argument makes no rational sense
of any kind.
Alan
WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
Rob Clark <rob@ti.com>, Sumit Semwal <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] dma-buf: Use EXPORT_SYMBOL
Date: Thu, 11 Oct 2012 12:34:07 +0100 [thread overview]
Message-ID: <20121011123407.63b5ecbe@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <201210110857.15660.hverkuil@xs4all.nl>
> The whole purpose of this API is to let DRM and V4L drivers share buffers for
> zero-copy pipelines. Unfortunately it is a fact that several popular DRM drivers
> are closed source. So we have a choice between keeping the export symbols GPL
> and forcing those closed-source drivers to make their own incompatible API,
> thus defeating the whole point of DMABUF, or using EXPORT_SYMBOL and letting
> the closed source vendors worry about the legality. They are already using such
> functions (at least nvidia is), so they clearly accept that risk.
Then they can accept the risk of ignoring EXPORT_SYMBOL_GPL and
calling into it anyway can't they. Your argument makes no rational sense
of any kind.
Alan
next prev parent reply other threads:[~2012-10-11 11:29 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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-11 20:08 ` [Linaro-mm-sig] " Dave Airlie
2012-10-12 16:32 ` Alan Cox
2012-10-25 21:30 ` Dave Airlie
2012-10-16 21:22 ` Robert Morell
2012-10-17 9:53 ` Alan Cox
2012-10-17 9:54 ` [Linaro-mm-sig] " Dave Airlie
2012-10-17 10:08 ` Dave Airlie
2012-10-17 10:19 ` Dave Airlie
2012-10-17 10:25 ` Alan Cox
2012-10-17 10:22 ` Dave Airlie
2012-10-17 10:38 ` Alan Cox
2012-10-17 10:40 ` Dave Airlie
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
-- strict thread matches above, loose matches on Subject: below --
2012-01-06 15:06 [git pull] dma-buf tree 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
2012-01-18 11:48 ` Alan Cox
2012-02-19 21:20 ` Rob Clark
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=20121011123407.63b5ecbe@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil@xs4all.nl \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=rmorell@nvidia.com \
--cc=rob@ti.com \
--cc=sumit.semwal@linaro.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.