From: Andy Walls <awalls@radix.net>
To: linux-media@vger.kernel.org, Sergey Bolshakov <sbolshakov@altlinux.ru>
Cc: ivtv-devel@ivtvdriver.org, hverkuil@xs4all.nl
Subject: cx18: Need information on SECAM-D/K problem with PVR-2100
Date: Sun, 03 Jan 2010 22:10:35 -0500 [thread overview]
Message-ID: <1262574635.5963.40.camel@localhost> (raw)
Sergey,
On IRC you mentioned a problem of improper detection of SECAM-D/K with
the Leadtek PVR2100 (XC2028 and CX23418) from an RF source.
To investigate this problem on my own, I added SECAM support to the
saa7127 driver so a PVR-350 could generate a baseband SECAM signal for
me. The good news for me is that a PVR-350 (SAA7115 video decoder) and
HVR-1600 (CX23418 integrated video decoder) card both properly
recognized the output of the PVR-350 as SECAM. The bad news is I could
not reproduce your problem with this setup.
Could you please do the following and send me the output from the logs?
1. Unload the cx18 module, tuner-xc2028 module, and the other tuner
modules.
2. In /etc/modprobe.conf set the following
options tuner-xc2028 debug=1
options tuner debug=1
3. Then
# modprobe cx18 debug=0x33 <---- info, warn, ioctl, file
# v4l2-ctl -d /dev/video0 -i 0 <---- Tuner input
# v4l2-ctl -d /dev/video0 -s 18 <---- SECAM-D/K
# v4l2-ctl -d /dev/video0 -f <freq of good channel>
# v4l2-ctl -d /dev/video0 --log-status
And send the relevant output from dmesg and /var/log/messages,
preferably to the mailing list. I do not need the lines that begin
"cx18-0 encoder MPEG: VIDIOC_QUERYCTRL " if that makes the output
smaller.
Thanks,
Andy
next reply other threads:[~2010-01-04 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 3:10 Andy Walls [this message]
2010-01-04 11:40 ` cx18: Need information on SECAM-D/K problem with PVR-2100 Sergey Bolshakov
2010-01-05 12:41 ` 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=1262574635.5963.40.camel@localhost \
--to=awalls@radix.net \
--cc=hverkuil@xs4all.nl \
--cc=ivtv-devel@ivtvdriver.org \
--cc=linux-media@vger.kernel.org \
--cc=sbolshakov@altlinux.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.