From: Hans de Goede <hdegoede@redhat.com>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH v2] tinyjpeg: Dynamic luminance quantization table for Pixart JPEG
Date: Sat, 28 Apr 2012 15:50:46 +0200 [thread overview]
Message-ID: <4F9BF5B6.9040203@redhat.com> (raw)
In-Reply-To: <20120425180949.2243472b@tele>
Hi,
On 04/25/2012 06:09 PM, Jean-Francois Moine wrote:
> Hi Hans,
<snip>
> BTW, I don't think the exposure and gain controls use the right
> registers as they are coded in the actual gspca pac7302 subdriver.
> The ms-windows driver uses the registers (3-80 / 3-03), (3-05 / 3-04),
3-03, 3-04 and 3-05 are already known and they all influence framerate /
exposure in some way. I've also ran some tests with 3-80, again it
influences framerate in some way (*). We already have a well tested and
working, fine-grained way to control exposure so I think it is best
to leave things as is exposure wise.
> (3-12)
3-12 is interesting, it is a new gain control. The pull request I've just
send (with you in the CC) contains a patch to improve gain control using
both 3-10 and 3-12 together.
> and (1-80)
1-80 is compression balance, since our decompression code for higher
compression settings (markers > 68) still is not perfect this is best
left untouched.
*) Note I've documented all registers I've ran tests with as part of
the patchset for which I've just send a pull request.
Regards,
Hans
prev parent reply other threads:[~2012-04-28 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 10:20 [PATCH v2] tinyjpeg: Dynamic luminance quantization table for Pixart JPEG Jean-Francois Moine
2012-04-23 21:34 ` Hans de Goede
2012-04-24 10:34 ` Jean-Francois Moine
2012-04-25 14:19 ` Hans de Goede
2012-04-25 16:09 ` Jean-Francois Moine
2012-04-27 13:08 ` Hans de Goede
2012-04-28 13:50 ` Hans de Goede [this message]
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=4F9BF5B6.9040203@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;
as well as URLs for NNTP newsgroup(s).