Hi All,
This patch adds support to libv4l for the compressed bayer format emitted by pac207 based cams.
Signed-off-by: Hans de Goede j.w.r.degoede@hhs.nl
Regards,
Hans
Hans de Goede a écrit :
Hi All,
This patch adds support to libv4l for the compressed bayer format emitted by pac207 based cams.
Signed-off-by: Hans de Goede j.w.r.degoede@hhs.nl
Regards,
Hans
Applied on http://www.linuxtv.org/hg/~tmerle/v4l2-library Is it necessary to add the emails about license authorizations in the sources? Only a public agreement on the ML, and the GNU LGPL should be sufficient.
Regards, Thierry
Thierry Merle wrote:
Hans de Goede a écrit :
Hi All,
This patch adds support to libv4l for the compressed bayer format emitted by pac207 based cams.
Signed-off-by: Hans de Goede j.w.r.degoede@hhs.nl
Regards,
Hans
Applied on http://www.linuxtv.org/hg/~tmerle/v4l2-library Is it necessary to add the emails about license authorizations in the sources?
I dunno IANAL, but within Fedora (where I'm a packager) the guy responsible for the legal stuff, in case of license changes always wants a "written" (email is ok) permission notice bundled with the sources, so I followed this example, we could put the permission notices in some other file, but I think its good practice to keep them around bundled with the sources. I deliberately put them at the end so that with normal editing they don't get in the way.
Actually I'm about to submit a patch to add a permission notice for the sn9c10x decompression algorithm as I didn't write that myself.
Regards,
Hans
p.s.
Sorry about the semi missing subject last mail.
Hans de Goede a écrit :
Thierry Merle wrote:
Hans de Goede a écrit :
Hi All,
This patch adds support to libv4l for the compressed bayer format emitted by pac207 based cams.
Signed-off-by: Hans de Goede j.w.r.degoede@hhs.nl
Regards,
Hans
Applied on http://www.linuxtv.org/hg/~tmerle/v4l2-library Is it necessary to add the emails about license authorizations in the sources?
I dunno IANAL, but within Fedora (where I'm a packager) the guy responsible for the legal stuff, in case of license changes always wants a "written" (email is ok) permission notice bundled with the sources, so I followed this example, we could put the permission notices in some other file, but I think its good practice to keep them around bundled with the sources. I deliberately put them at the end so that with normal editing they don't get in the way.
OK if it is mandatory, continue to put it at the closest place from the concerned source code.
Actually I'm about to submit a patch to add a permission notice for the sn9c10x decompression algorithm as I didn't write that myself.
OK
Regards,
Hans
p.s.
Sorry about the semi missing subject last mail.
I corrected it by myself :)
Thierry
-
Hans de Goede -
Thierry Merle