From: Franklin Meng <fmeng2002@yahoo.com>
To: Andy Walls <awalls@radix.net>,
Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Any saa711x users out there?
Date: Fri, 5 Feb 2010 08:21:21 -0800 (PST) [thread overview]
Message-ID: <762758.71843.qm@web32707.mail.mud.yahoo.com> (raw)
In-Reply-To: <829197381002042034g486b6162rf065388a225a60be@mail.gmail.com>
I also have a device that has the SAA7113 chip in it. Kworld 315U.
I suggested a patch to add a an s_power function to the code but it looks like the patch didn't work. I have to do some cleanup to it and resubmit it.
Franklin Meng
--- On Thu, 2/4/10, Devin Heitmueller <dheitmueller@kernellabs.com> wrote:
> From: Devin Heitmueller <dheitmueller@kernellabs.com>
> Subject: Re: Any saa711x users out there?
> To: "Andy Walls" <awalls@radix.net>
> Cc: "Linux Media Mailing List" <linux-media@vger.kernel.org>
> Date: Thursday, February 4, 2010, 8:34 PM
> Hey Andy,
>
> On Thu, Feb 4, 2010 at 11:15 PM, Andy Walls <awalls@radix.net>
> wrote:
> > Hmmm. The AGC (or static gain level?) of the
> amplifier in the SAA7113
> > before the anti-alias filter may be set too high
> causing the clipping
> > (intermods) there. It may be worth looking at the
> gain setting for that
> > amp.
>
> It's possible. One thing I did as a test though was I
> did a capture
> of the i2c traffic under Windows (using the same reference
> video
> source), and then compared the register programming (via
> some scripts
> I whipped up). There were some other registers that
> were different,
> but the only one that made *any* visible difference in the
> output was
> the AA flag.
>
> > The visible effects of the anti-alais filter could
> possibly be:
> >
> > 1. Less range of color, if high freqs of the color get
> attenuated.
> > (Most people likely will not perceive this as most
> people are not that
> > sensitive to small color variations.)
> >
> > 2. Loss of rapid variations in Luma - softer edges
> between light and
> > dark areas on a scan line - if higher freqs of the
> Luma get attenuated.
> >
> > but given that the anti-alais filter is essentially
> flat out to about
> > 5.6 MHz and has a slow rolloff (only 3 dB down at
> about 6.9 MHz), I
> > doubt anyone would ever notice it is on with NTSC.
>
> To give you a better idea of what I'm talking about, look
> at this image:
>
> http://imagebin.org/83458
>
> The above image was taken with the generator via the
> s-video input
> (ruling out the possibility that it's any sort of product
> of
> intermodulation).
>
> For the sake of comparison, here's the exact same signal
> source
> against an a similar em28xx design but with the tvp5150.
>
> http://imagebin.org/83459
>
> > Since you have a signal generator, you should run
> experiments with PAL-D
> > and SECAM-D with a grid containing vertical lines
> since those both have
> > a 6.0 MHz video bandwidth. SECAM also has FM color,
> so you might see
> > the greatest affect of an antialias filter on color on
> the Cyan color
> > bar in SECAM-D.
>
> Believe it or not, I'm actually having trouble with the
> generator
> right now with anything but NTSC. I'm going back and
> forth with
> Promax on repair options. So I cannot do any PAL or
> SECAM testing
> right now.
>
> On a separate note, I really should look at extending the
> v4l2
> capture-example to a version that let's me do a direct
> capture of the
> YUYV frame and convert the output into a zero-loss RGB
> format. It's
> too easy to be mislead by things the applications are doing
> like
> deinterlacing, rescaling, blending, and compression of the
> screenshot
> when saving to a file.
>
> Devin
>
> --
> Devin J. Heitmueller - Kernel Labs
> http://www.kernellabs.com
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-02-05 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 22:51 Any saa711x users out there? Devin Heitmueller
2010-02-03 0:29 ` Mauro Carvalho Chehab
2010-02-03 15:57 ` Devin Heitmueller
2010-02-03 16:41 ` Mauro Carvalho Chehab
2010-02-04 1:51 ` Andy Walls
2010-02-04 15:24 ` Devin Heitmueller
2010-02-05 4:15 ` Andy Walls
2010-02-05 4:34 ` Devin Heitmueller
2010-02-05 16:21 ` Franklin Meng [this message]
2010-02-06 16:37 ` Andy Walls
-- strict thread matches above, loose matches on Subject: below --
2010-02-08 0:10 Andy Walls
2010-02-08 15:36 ` Devin Heitmueller
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=762758.71843.qm@web32707.mail.mud.yahoo.com \
--to=fmeng2002@yahoo.com \
--cc=awalls@radix.net \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@vger.kernel.org \
/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