From: "Aleksandr V. Piskunov" <aleksandr.v.piskunov@gmail.com>
To: linux-media@vger.kernel.org
Subject: xc2028 sound carrier detection
Date: Tue, 22 Sep 2009 01:37:51 +0300 [thread overview]
Message-ID: <20090921223751.GA1303@moon> (raw)
Is xc2028 tuner able to autodetect/handle different sound carrier standards
without being spoon-fed precise input system information using module param
or ioctl?
Got an ivtv board here (AverTV MCE 116) with xc2028 and cx25843.
When I specify a generic standard using 'v4l2-ctl -s pal', xc2028 loads
firmware specific to PAL-BG, so if there is an PAL-DK or PAL-I signal on RF
input... nice picture but no sound. Setting a more precise standard like
'v4l2-ctl -s pal-dk' fixes the issue, but other PAL-BG or PAL-I channels
loose sound.
Bttv board with a tin-can tuner sitting on the same RF source autodetects
PAL-BG, PAL-DK and PAL-I without any manual intervention.
So any voodoo tricks to get the autodetection running?
next reply other threads:[~2009-09-21 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 22:37 Aleksandr V. Piskunov [this message]
[not found] ` <20090921215238.2e189d60@pedra.chehab.org>
2009-09-23 19:28 ` xc2028 sound carrier detection Aleksandr V. Piskunov
2009-09-23 21:27 ` Devin Heitmueller
2009-09-25 21:03 ` Aleksandr V. Piskunov
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=20090921223751.GA1303@moon \
--to=aleksandr.v.piskunov@gmail.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