On 06/03/17 09:43, wm4 wrote: > On Mon, 6 Mar 2017 10:38:53 +0100 > Luca Barbato <lu_z...@gentoo.org> wrote: > >> On 06/03/2017 09:33, Diego Biurrun wrote: >>> On Sat, Mar 04, 2017 at 11:57:47PM +0000, Mark Thompson wrote: >>>> --- a/configure >>>> +++ b/configure >>>> @@ -1272,6 +1273,7 @@ HWACCEL_LIBRARY_LIST=" >>>> mmal >>>> nvenc >>>> omx >>>> + opencl >>>> vaapi >>>> vda >>>> vdpau >>> >>> Does opencl have a compatible license? Which one? >>> >> >> MIT. >> >> /******************************************************************************* >> * Copyright (c) 2008-2015 The Khronos Group Inc. >> * >> * Permission is hereby granted, free of charge, to any person obtaining a >> * copy of this software and/or associated documentation files (the >> * "Materials"), to deal in the Materials without restriction, including >> * without limitation the rights to use, copy, modify, merge, publish, >> * distribute, sublicense, and/or sell copies of the Materials, and to >> * permit persons to whom the Materials are furnished to do so, subject to >> * the following conditions: >> * >> * The above copyright notice and this permission notice shall be included >> * in all copies or substantial portions of the Materials. >> * >> * MODIFICATIONS TO THIS FILE MAY MEAN IT NO LONGER ACCURATELY REFLECTS >> * KHRONOS STANDARDS. THE UNMODIFIED, NORMATIVE VERSIONS OF KHRONOS >> * SPECIFICATIONS AND HEADER INFORMATION ARE LOCATED AT >> * https://www.khronos.org/registry/ >> * >> * THE MATERIALS ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, >> * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF >> * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. >> * IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY >> * CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, >> * TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE >> * MATERIALS OR THE USE OR OTHER DEALINGS IN THE MATERIALS. >> >> ******************************************************************************/ > > The license of the header is of course important. > > Isn't OpenCL technically provided by the driver, which makes the > licensing questionable, but is usually not an issue because it's > considered a system-provided thing?
The linked binary is the ICD loader: <https://github.com/KhronosGroup/OpenCL-ICD-Loader>. The driver files are dynamically loaded by it at runtime, so there are no issues with proprietary drivers from hostile hardware companies. The ICD loader is also MIT, but with some tricky additional clauses to block people from making incompatible binaries and forking the standard. I believe that these do not apply because we are neither modifying the ICD loader code nor are we making an OpenCL implementation. _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
