From: Robert Jarzmik <robert.jarzmik@free.fr>
To: fpantaleao@mobisensesystems.com
Cc: video4linux-list@redhat.com
Subject: Re: About CITOR register value for pxa_camera
Date: Fri, 31 Oct 2008 19:45:38 +0100 [thread overview]
Message-ID: <87vdv8mwml.fsf@free.fr> (raw)
In-Reply-To: <20081031160520.2cc7whghs0gs8osk@webmail.hebergement.com> (fpantaleao@mobisensesystems.com's message of "Fri\, 31 Oct 2008 16\:05\:20 +0100")
fpantaleao@mobisensesystems.com writes:
> Hi all,
>
> While testing, I think I have found one reason why overruns occur with
> pxa_camera.
> I propose to set CITOR to a non-null value.
Yes, seconded.
> I would appreciate any comment about this.
Well, at first sight I would advice to test some corner case to see if DMA
trailing bytes are handled well. I know this can be a pain, but you seem to be
testing thouroughly ..
So, if your configuration/sensor is able to, try some funny resolution like
"1619 x 1", and then "67 x 1", and see what happens. If you don't have any
capture issue, you're done, and post a patch (only CITOR or CITOR + trailling
bytes handling).
Have fun.
--
Robert
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-10-31 18:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 15:05 About CITOR register value for pxa_camera fpantaleao
2008-10-31 18:45 ` Robert Jarzmik [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-05 14:14 fpantaleao
2008-11-05 19:31 ` Guennadi Liakhovetski
2008-11-06 5:26 fpantaleao
2008-11-06 23:57 ` Guennadi Liakhovetski
2008-11-07 6:22 fpantaleao
2008-11-07 7:58 ` Guennadi Liakhovetski
2008-11-07 12:01 fpantaleao
2008-11-29 1:42 ` Guennadi Liakhovetski
2008-11-30 22:42 ` Robert Jarzmik
2008-11-30 23:59 ` Guennadi Liakhovetski
2008-12-01 15:14 ` Guennadi Liakhovetski
2008-12-01 21:13 ` Robert Jarzmik
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=87vdv8mwml.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=fpantaleao@mobisensesystems.com \
--cc=video4linux-list@redhat.com \
/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