From: Hans de Goede <hdegoede@redhat.com>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] v4l-utils: Add the JPEG Lite decoding function
Date: Mon, 14 Feb 2011 20:20:32 +0100 [thread overview]
Message-ID: <4D598080.2070100@redhat.com> (raw)
In-Reply-To: <20110214133643.3c9d1454@tele>
Hi,
On 02/14/2011 01:36 PM, Jean-Francois Moine wrote:
> Hi Hans,
>
> JPEG Lite images are created by the DivIO nw80x chips.
>
> The gspca subdriver nw80x will be ready soon.
>
> Decoding to RGB24 and BGR24 are ok. Decoding to YUV420 and YVU420 are
> not tested.
>
You're working on nw80x support? Cool! I've a cam with one of
those chipsets lying around, it is a Dynalink 06be:d001. I'll definitely
give the driver a try when it hits your git tree, or send it
my way if you wanted it tested with this cam earlier.
Now about the libv4l patch, unfortunately it cannot go in as is.
The problem is that the code you derived it from seems to be GPL
not LGPL (judging from the copyright header you put on top of it),
and libv4l is LGPL, and has to be to to allow it to be used with
for example skype and flash. The thing to do here is to try
and contact the original author and get permission to relicense
under the LGPL (version 2 or later). In the mean time the code
can still go in but as an external helper, see for example the
ov511 and ov518 decompression code. There is a generic external
helper framework in libv4l, so the needed code changes should
be minimal.
Thanks & Regards,
Hans
next prev parent reply other threads:[~2011-02-14 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 12:36 [PATCH] v4l-utils: Add the JPEG Lite decoding function Jean-Francois Moine
2011-02-14 19:20 ` Hans de Goede [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-15 9:26 Jean-Francois Moine
2011-02-15 19:30 ` Hans de Goede
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=4D598080.2070100@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=moinejf@free.fr \
/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