From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jose Alberto Reguero <jareguero@telefonica.net>
Cc: Jean-Francois Moine <moinejf@free.fr>,
Hans de Goede <hdegoede@redhat.com>,
linux-media@vger.kernel.org
Subject: Re: Problem with gspca and zc3xx
Date: Thu, 06 May 2010 15:09:33 -0300 [thread overview]
Message-ID: <4BE305DD.5020106@redhat.com> (raw)
In-Reply-To: <201001141726.52062.jareguero@telefonica.net>
Jose Alberto Reguero wrote:
> El Miércoles, 13 de Enero de 2010, Jose Alberto Reguero escribió:
>> El Martes, 12 de Enero de 2010, Jose Alberto Reguero escribió:
>>> El Martes, 12 de Enero de 2010, Jean-Francois Moine escribió:
>>>> On Mon, 11 Jan 2010 15:49:55 +0100
>>>>
>>>> Jose Alberto Reguero <jareguero@telefonica.net> wrote:
>>>>> I take another image with 640x480 and the bad bottom lines are 8. The
>>>>> right side look right this time. The good sizes are:
>>>>> 320x240->320x232
>>>>> 640x480->640x472
>>>> Hi Jose Alberto and Hans,
>>>>
>>>> Hans, I modified a bit your patch to handle the 2 resolutions (also,
>>>> the problem with pas202b does not exist anymore). May you sign or ack
>>>> it?
>>>>
>>>> Jose Alberto, the attached patch is to be applied to the last version
>>>> of the gspca in my test repository at LinuxTv.org
>>>> http://linuxtv.org/hg/~jfrancois/gspca
>>>> May you try it?
>>>>
>>>> Regards.
>>> The patch works well.
>>> There is another problem. When autogain is on(default), the image is bad.
>>> It is possible to put autogain off by default?
>>>
>>> Thanks.
>>> Jose Alberto
>> Autogain works well again. I can't reproduce the problem. Perhaps the debug
>> messages. (Now I have debug off).
>>
>> Thanks.
>> Jose Alberto
>
> I found the problem. Autogain don't work well if brightness is de default
> value(128). if brightness is less(64) autogain work well. There is a problem
> when setting the brightness. It is safe to remove the brightness control?
> Patch attached.
>
> Jose Alberto
This patch doesn't apply anymore. I'm not sure if the issue were fixed upstream. If
not, please re-base your patch against my git tree and send it again.
patching file drivers/media/video/gspca/zc3xx.c
Hunk #1 succeeded at 6086 with fuzz 1 (offset 45 lines).
Hunk #2 FAILED at 6882.
1 out of 2 hunks FAILED -- saving rejects to file drivers/media/video/gspca/zc3xx.c.rej
>>> Patch patches/lmml_72895_problem_with_gspca_and_zc3xx.patch doesn't apply
--
Cheers,
Mauro
next prev parent reply other threads:[~2010-05-06 18:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 23:15 Problem with gspca and zc3xx Jose Alberto Reguero
2010-01-10 8:37 ` Jean-Francois Moine
2010-01-10 10:31 ` Jose Alberto Reguero
2010-01-11 8:37 ` Hans de Goede
2010-01-11 9:55 ` Jean-Francois Moine
2010-01-11 14:49 ` Jose Alberto Reguero
2010-01-12 8:36 ` Jean-Francois Moine
2010-01-12 11:54 ` Hans de Goede
2010-01-12 14:57 ` Jose Alberto Reguero
2010-01-13 13:50 ` Jose Alberto Reguero
2010-01-14 16:26 ` Jose Alberto Reguero
2010-05-06 18:09 ` Mauro Carvalho Chehab [this message]
2010-05-06 18:32 ` Jean-Francois Moine
2010-01-11 22:03 ` Hans de Goede
-- strict thread matches above, loose matches on Subject: below --
2010-01-28 13:35 Fabio Rossi
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=4BE305DD.5020106@redhat.com \
--to=mchehab@redhat.com \
--cc=hdegoede@redhat.com \
--cc=jareguero@telefonica.net \
--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