cx18: Need information on SECAM-D/K problem with PVR-2100

2010-01-03 Thread Andy Walls 
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 
# 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

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: cx18: Need information on SECAM-D/K problem with PVR-2100

2010-01-04 Thread Sergey Bolshakov 
> "Andy" == Andy Walls  writes:

 > 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.

It was some misunderstanding, i suppose, i do not have problems with
secam, i had improper detection of sound standard (and silence as
result) on pal channels. Later i've found, that fully-specified std
(pal-d instead of just pal) helps, so i can live with that.

Anyway, logs you requested (first STATUS CARD chunk for pal, second
for pal-d):

cx18:  Start initialization, version 1.2.0
cx18-0: Initializing card 0
cx18-0: Autodetected Leadtek WinFast PVR2100 card
cx18 :01:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
cx18-0: cx23418 revision 0101 (B)
cx18-0: Experimenters and photos needed for device to work well.
To help, mail the ivtv-devel list (www.ivtvdriver.org).
IRQ 17/cx18-0: IRQF_DISABLED is not guaranteed on shared IRQs
tuner 1-0061: Setting mode_mask to 0x0e
tuner 1-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
tuner 1-0061: tuner 0x61: Tuner type absent
tuner 1-0061: Calling set_type_addr for type=71, addr=0xff, mode=0x04, 
config=0x
tuner 1-0061: defining GPIO callback
xc2028: Xcv2028/3028 init called!
xc2028 1-0061: creating new instance
xc2028 1-0061: type set to XCeive xc2028/xc3028 tuner
tuner 1-0061: type set to Xceive XC3028
tuner 1-0061: cx18 i2c driver #0-1 tuner I2C addr 0xc2 with type 71 used for 
0x0e
xc2028 1-0061: xc2028_set_config called
cx18-0: Registered device video0 for encoder MPEG (64 x 32 kB)
cx18-0: Registered device video32 for encoder YUV (16 x 128 kB)
cx18-0: Registered device vbi0 for encoder VBI (20 x 51984 bytes)
cx18-0: Registered device video24 for encoder PCM audio (256 x 4 kB)
cx18-0: Registered device radio0 for encoder radio
cx18-0: Initialized card: Leadtek WinFast PVR2100
cx18:  End initialization
cx18 :01:07.0: firmware: requesting v4l-cx23418-cpu.fw
cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332 bytes)
cx18 :01:07.0: firmware: requesting v4l-cx23418-apu.fw
cx18-0: loaded v4l-cx23418-apu.fw firmware V0012 (141200 bytes)
cx18-0: FW version: 0.0.74.0 (Release 2007/03/12)
cx18 :01:07.0: firmware: requesting v4l-cx23418-cpu.fw
cx18 :01:07.0: firmware: requesting v4l-cx23418-apu.fw
cx18 :01:07.0: firmware: requesting v4l-cx23418-dig.fw
cx18-0 843: loaded v4l-cx23418-dig.fw firmware (16382 bytes)
cx18-0 843: verified load of v4l-cx23418-dig.fw firmware (16382 bytes)
tuner 1-0061: switching to v4l2
tuner 1-0061: tv freq set to 400.00
xc2028 1-0061: xc2028_set_analog_freq called
xc2028 1-0061: generic_set_freq called
xc2028 1-0061: should set frequency 40 kHz
xc2028 1-0061: check_firmware called
xc2028 1-0061: load_all_firmwares called
xc2028 1-0061: Reading firmware xc3028-v27.fw
cx18 :01:07.0: firmware: requesting xc3028-v27.fw
xc2028 1-0061: Loading 80 firmware images from xc3028-v27.fw, type: xc2028 
firmware, ver 2.7
xc2028 1-0061: Reading firmware type BASE F8MHZ (3), id 0, size=8718.
xc2028 1-0061: Reading firmware type BASE F8MHZ MTS (7), id 0, size=8712.
xc2028 1-0061: Reading firmware type BASE FM (401), id 0, size=8562.
xc2028 1-0061: Reading firmware type BASE FM INPUT1 (c01), id 0, size=8576.
xc2028 1-0061: Reading firmware type BASE (1), id 0, size=8706.
xc2028 1-0061: Reading firmware type BASE MTS (5), id 0, size=8682.
xc2028 1-0061: Reading firmware type (0), id 10007, size=161.
xc2028 1-0061: Reading firmware type MTS (4), id 10007, size=169.
xc2028 1-0061: Reading firmware type (0), id 20007, size=161.
xc2028 1-0061: Reading firmware type MTS (4), id 20007, size=169.
xc2028 1-0061: Reading firmware type (0), id 40007, size=161.
xc2028 1-0061: Reading firmware type MTS (4), id 40007, size=169.
xc2028 1-0061: Reading firmware type (0), id 80007, size=161.
xc2028 1-0061: Reading firmware type MTS (4), id 80007, size=169.
xc2028 1-0061: Reading firmware type (0), id 300e0, size=161.
xc2028 1-0061: Reading firmware type MTS (4), id 300e0, size=169.
xc2028 1-0061: Reading firmware type (0), id c00e0, size=161.
xc2028 1-0061: Reading firmware type MTS (4), id c00e0, size=169.
xc2028 1-0061: Reading firmware type (0), id 20, size=161.
xc2028 1-0061: Reading firmware type MTS (4), id 20, size=169.
xc2028 1-0061: Reading firmware type (0), id 400, size=161.
xc2028 1-0061: Reading firmware type MTS (4), id 400, size=169.
xc2028 1-0061: Reading firmware type D2633 DTV6 ATSC (10030), id 0, size=149.
xc2028 1-0061: Reading firmware type D2620 DTV6 QAM (68), id 0, size=149.
xc2028 1-0061: Reading firmware type D2633 DTV6 QAM (70), id 0, size=149.
xc2028 1-0061: Reading firmware type D2620 DTV7 (88), id 0, size=149.
xc2028 1-0061: Reading firmware type D2633 DTV7 (90), id 0, size=149.
xc2028 1-0061: Reading firmware type D2620 DTV78 (108), id 0, size=149.
xc2028 1-0061: Reading firmware type D2633 DTV78 (110), id 0, size=149.
xc2028 1-0061: R

Re: cx18: Need information on SECAM-D/K problem with PVR-2100

2010-01-05 Thread Aleksandr V. Piskunov 
On Mon, Jan 04, 2010 at 02:40:47PM +0300, Sergey Bolshakov wrote:
> > "Andy" == Andy Walls  writes:
> 
>  > 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.
> 
> It was some misunderstanding, i suppose, i do not have problems with
> secam, i had improper detection of sound standard (and silence as
> result) on pal channels. Later i've found, that fully-specified std
> (pal-d instead of just pal) helps, so i can live with that.
> 

Thats a general problem of any card with XC2028 silicon tuner, user
(tv app) has to specify a precise substandard (audio carrier frequency)
for sound to work.

PAL-BG users (western europe, etc) won't notice it, since in case of 
generic PAL standard set, xceive tuner defaults to BG substandard firmware.

In other cases, you either have to specify correct standard (DK, etc) or
try to specify PAL-I, which seems to work for BG, DK and I carriers.
At least it works for me :)

See http://osdir.com/ml/linux-media/2009-09/msg00997.html for more details.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html