
awalls at radix
May 21, 2008, 8:24 AM
Post #4 of 10
(4716 views)
Permalink
|
On Tue, 2008-05-20 at 15:10 -0400, zedoriah [at] gmail wrote: > The cx18 driver seems to be working wonderfully, other than I get no audio. > > $ cat /dev/video0 > test.mpg > $ mplayer test.mpg > [snip] > Audio: no sound > [snip] > > So it's looking like it's not finding any audio at all, it's not low or anything. There is a known bug related to firmware loading after the modporbe of cx18, the first analog capture may not have audio. Do you get audio with the second capture? > I read it only supports mono so far, so let's check that: > > ~$ v4l2-ctl -IT > ~$ v4l2-ctl -D > ~$ v4l2-ctl -l | grep -i audio These commands may not tell you the whole truth when it comes to audio. Some are reporting from the CX23418's encoder settings and some are reporting from the CX25843 core in the CX23418. For tuner audio, the CX28543 core is currently being bypassed even though it's still being configured (improperly) for tuner SIF audio processing. So it may report stereo even though it's not the encoder's current baseband audio source. Fixing tuner audio to get stereo is on my pet peeve list of things to do. But right now I only have data to fix most of the problem (i.e. the cx25843 setup), but not all of the problem (i.e. how to tell the encoder what to use for audio input). > The only strange thing showing up in dmesg is: > [158086.417606] cx18-0: i2c ID 0x00000000 (gpio) not found for cmd 0xc0185650! > > repeatedly. 1. The function that emits this message in your case is: cx18-i2c.c:cx18_i2c_id() is currently only called for handling debug ioctls. Your attempts at troubleshooting may have stimulated them. If you: # modprobe -r cx18 # modprobe cx18 debug=83 To turn on i2c, ioctl, warn, and info debugging, you may be able to better see what user actions you are taking to stimulate the message. 2. cmd 0xc01855650 decodes to dir = IOWR, size = 0x18 (24 decimal), type = 0x56 'V', number = 0x50 (80 decimal). This appears to be VIDIOC_DBG_G_REGISTER defined in linux/include/videodev2.h. Whatever command line utility you are using for debug is making this ioctl() call on cx18 with a bad argument. There is no real device with an I2C id of 0. The cx18 driver internally assigns 0 to the GPIO and the CX23418 as "dummy" i2c devices. In the name lookup, it finds gpio first, so that's why that's in the message. > This is on Ubuntu 8.04, 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux > > Any help would be greatly appreciated. If you have compiled v4l2-dbg you may want to try the following commands to check the state of the cs5345 registers, and see if they are close to mine: # v4l2-dbg -d /dev/video1 -C host 0x0: cx23418 revision 0x00000000 i2c 0x4c: cs5345 revision 0x00000000 # v4l2-dbg -d /dev/video1 -R type=i2cdrv,chip=cs5345 ioctl: VIDIOC_DBG_G_REGISTER 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000000: e2 00 08 01 10 40 00 00 01 00 00 c0 00 00 00 00000010: 00 (/dev/video1 is my HVR-1600, yours may be at /dev/video0.) The cs5345 is responsible for digitizing, amplifying, muting, and multiplexing baseband audio sources. If it isn't set up right, then no baseband audio would be a symptom. Regards, Andy _______________________________________________ ivtv-devel mailing list ivtv-devel [at] ivtvdriver http://ivtvdriver.org/mailman/listinfo/ivtv-devel
|