On Thu, 2009-12-31 at 14:26 -0500, Andy Walls wrote:
> On Thu, 2009-12-31 at 18:15 +0100, Martin Dauskardt wrote:
Some corrections to errors:
> My preferences in summary, is that not matter what the digitizer chip:
My preferences are, in summary, that no matter what the digitizer chip:
> a. I'd like to keep the audio clocks always up to avoid tinny audio.
>
> b. I'd also like to inhibit the video clock and add the delay after
^^^
refine
> re-enabling the digitizer to avoid the *potential* for a hung machine.
A value smaller than 300 ms should work, but a value smaller than 40 ms
may not work, if my hypothesis is correct.
>
> c. I do not care to much about the delay after disbaling the video
> clock, only that it is empirically "long enough".
>
> Thanks for taking the time to test and comment.
>
> Regards,
> Andy
Regards,
Andy
> > Greets and Happy New Year
> >
> > Martin
> >
> > PS:
> > Readers on the ivtv-devel ML list will miss previous postings (the list was
> > down a few days). Please have a look in
> > http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/14151
> > and
> > http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/14155
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
