Mailing List Archive

Devin Heitmueller wrote:

> On Fri, Jan 22, 2010 at 5:20 PM, Andy Walls <awalls@radix.net> wrote:
>> No. I'm implying that without being able to visualize the signal
>> defect (due to no storage o-scope), I have a low probably of finding
>> the right settings even with VHS tape in hand.
>
> Has Tony tried the that tape with the Hauppauge card under Windows?

Yes I have, Devin, with the same results within the Microsoft environment
with any of the three Hauppage cards.


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

I wrote:

> In order to get the "v4l2-dbg" functionality, new troubles exist when
> installing the most recent drivers after a "make apps" etc. as
> outlined in
> http://ivtvdriver.org/pipermail/ivtv-users/2009-December/009710.html

Problem solved by removing the ivtv rpm packages, which apparently were
conflicting with the source install.


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

On Fri, 2010-01-22 at 15:56 -0800, Tony Ross wrote:
> I wrote:
> ...
> > May I ask please how one "looks" at, or sets the register settings?
>
> In order to get the "v4l2-dbg" functionality, new troubles exist when
> installing the most recent drivers after a "make apps" etc. as outlined in
> http://ivtvdriver.org/pipermail/ivtv-users/2009-December/009710.html :
>
> ...
> [root@centos54 v4l-dvb-e4429a1b736c]# make install
> make -C /home/me/src/v4l-dvb-e4429a1b736c/v4l install
> make[1]: Entering directory `/home/me/src/v4l-dvb-e4429a1b736c/v4l'
>
> Removing obsolete files from
> /lib/modules/2.6.18-164.9.1.el5/kernel/drivers/media/video:
> Removing obsolete files from
> /lib/modules/2.6.18-164.9.1.el5/kernel/drivers/media/dvb/cinergyT2:
> Removing obsolete files from
> /lib/modules/2.6.18-164.9.1.el5/kernel/drivers/media/common:
> Removing obsolete files from
> /lib/modules/2.6.18-164.9.1.el5/kernel/drivers/media/dvb/frontends:
>
> Installing kernel modules under
> /lib/modules/2.6.18-164.9.1.el5/kernel/drivers/media/:
^^^^^^^^^^^^^^^^^^^^
Remeber that path and see below....

> video/gspca/m5602/: gspca_m5602.ko
[...]
> video/ivtv/: ivtvfb.ko ivtv.ko
^^^^^^^^^^
Also remeber that additional portion of the path and see below....

[...]
> video/au0828/: au0828.ko
> /sbin/depmod -a 2.6.18-164.9.1.el5
> make -C firmware install
> make[2]: Entering directory `/home/me/src/v4l-dvb-e4429a1b736c/v4l/firmware'
> Installing firmwares at /lib/firmware: vicam/firmware.fw dabusb/firmware.fw
> dabusb/bitstream.bin ttusb-budget/dspbootcode.bin cpia2/stv0672_vp4.bin
> av7110/bootcode.bin
> make[2]: Leaving directory `/home/me/src/v4l-dvb-e4429a1b736c/v4l/firmware'
> make[1]: Leaving directory `/home/me/src/v4l-dvb-e4429a1b736c/v4l'
>
> [root@centos54 v4l-dvb-e4429a1b736c]# make unload
> make -C /home/me/src/v4l-dvb-e4429a1b736c/v4l unload
> make[1]: Entering directory `/home/me/src/v4l-dvb-e4429a1b736c/v4l'
> scripts/rmmod.pl unload
> found 271 modules
> /sbin/rmmod cx2341x
> /sbin/rmmod v4l2_common
> /sbin/rmmod videodev
> /sbin/rmmod v4l1_compat
> /sbin/rmmod tveeprom
> make[1]: Leaving directory `/home/me/src/v4l-dvb-e4429a1b736c/v4l'
> [root@centos54 v4l-dvb-e4429a1b736c]# make unload
> make -C /home/me/src/v4l-dvb-e4429a1b736c/v4l unload
> make[1]: Entering directory `/home/me/src/v4l-dvb-e4429a1b736c/v4l'
> scripts/rmmod.pl unload
> found 271 modules
> make[1]: Leaving directory `/home/me/src/v4l-dvb-e4429a1b736c/v4l'


> [root@centos54 v4l-dvb-e4429a1b736c]# modprobe ivtv
> FATAL: Error inserting ivtv (/lib/modules/2.6.18-164.9.1.el5/extra/ivtv.ko):
^^^^^
Wrong path -----------------------------------------------------|


That's an old ivtv module. Move it out of the way or get rid of it.

You may have to as root run:

# /sbin/depmod -a 2.6.18-164.9.1.el5

again after removing it.

You may also want to look for any other duplicate module names
under /lib/modules/2.6.18-164.9.1.el5/ and move the older ones out of
the way or remove them.

Regards,
Andy

> Unknown symbol in module, or unknown parameter (see dmesg)
>
> [root@centos54 v4l-dvb-e4429a1b736c]# dmesg
> ...
> ivtv: disagrees about version of symbol cx2341x_ext_ctrls
> ivtv: Unknown symbol cx2341x_ext_ctrls
> ivtv: disagrees about version of symbol v4l_compat_translate_ioctl



_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

On Fri, 2010-01-22 at 14:02 -0800, Tony Ross wrote:

> May I ask please how one "looks" at, or sets the register settings? I see
> that "v4l2-ctl --set-ctrl=<ctrl>=<val>[,<ctrl>=<val>...]" allows one to
> alter the value of various controls returned by the "-l" (ell) option, but I
> don't see any obvious way to list or set the values of the various registers
> on the chip.

v4l-dbg, with debugging compiled into the ivtv, cx25840, cx18, and
videodev modules is the easiest way. You have to be root to use it.

Just so you know, an HVR-1600 will show this:

# v4l2-dbg -d /dev/video0 -S
host0: cx23418 revision 0x01010000
host1: cx23418_843 revision 0x00008430
i2c 0x4c: cs5345 revision 0x00000000

# v4l2-dbg -d /dev/video0 -c host1 --list-registers=min=0x100,max=0x11f
ioctl: VIDIOC_DBG_G_REGISTER

00 04 08 0C 10 14 18 1C
00000100: 76028430 07005d00 160e040f 002be2fe 005227ad 00078c00 00000002 00000000
^^^^
(This indicates you're accessing the CX23418 integrated digitizer)


And a PVR-150 will show this:

# v4l2-dbg -d /dev/video1 -S
host0: cx23416 revision 0x00000000
i2c 0x1b: wm8775 revision 0x00000000
i2c 0x44: cx25843 revision 0x00008433

# v4l2-dbg -d /dev/video1 -c 0x44 --list-registers=min=0x100,max=0x10f
ioctl: VIDIOC_DBG_G_REGISTER

00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00000100: 33 84 02 76 80 dd 04 07 0f 04 0a 10 fe e2 2b 00
^^^^^
(This indicates you're accessing the CX25843)



But honestly, I'd recommend using my "technician controls" for the
HVR-1600 first. They are in this oldish repository here:

http://linuxtv.org/hg/~awalls/v4l-dvb-ctls/

And an email on what they mean:
http://ivtvdriver.org/pipermail/ivtv-users/2009-August/009513.html

It saves much of the bit counting on a number of registers I recommended
you might twiddle.


> Of course I'd like to be able to somehow return to the current settings if
> something gets mucked up. <g>

Well, the CX25843 has a *cough* helpful *cough* autoconfig. If you muck
with some registers, it reconfigures some others by itself. The cx25840
driver leaves autoconfig on and cleans up after it when it happens.
(You will find that frustrating but can clean it up with a switch to
another input and then back IIRC). The cx18 driver turns autoconfig off
(plus the chip appears to ignore it) and no auto register config
happens.

I have attached my notes on CX25843 register autoconfig. It is all from
the datasheet, but just in one place.

Again, if you can test with the HVR-1600 and the "technician controls"
patches, I'd do that.

Regards,
Andy

Andy Walls wrote:

> Just so you know, an HVR-1600 will show this:
>
> # v4l2-dbg -d /dev/video0 -S
> host0: cx23418 revision 0x01010000
> host1: cx23418_843 revision 0x00008430
> i2c 0x4c: cs5345 revision 0x00000000

Here I have:

# pwd
/home/me/src/v4l-dvb-ctls-c9f13db7a53e/v4l2-apps/util

# ./v4l2-dbg -S
host0: cx23418 revision 0x01010000
host1: cx23418_843 revision 0x00008430
i2c 0x4c: cs5345 revision 0x00000000

My apologies for the following line-wraps:

> # v4l2-dbg -d /dev/video0 -c host1
> --list-registers=min=0x100,max=0x11f
> ioctl: VIDIOC_DBG_G_REGISTER
>
> 00 04 08 0C 10 14
> 18 1C 00000100: 76028430 07005d00 160e040f 002be2fe 005227ad
> 00078c00 00000002 00000000 ^^^^
> (This indicates you're accessing the CX23418 integrated digitizer)

Some diferences here, not sure if they're important in any way:

# ./v4l2-dbg -c host1 --list-registers=min=0x100,max=0x11f
ioctl: VIDIOC_DBG_G_REGISTER

00 04 08 0C 10 14 18
1C
00000100: d0008430 07005c00 210e040f 002be2fe 005227ad 00078c00 00000002
00000000

...
> But honestly, I'd recommend using my "technician controls" for the
> HVR-1600 first. They are in this oldish repository here:
>
> http://linuxtv.org/hg/~awalls/v4l-dvb-ctls/
>
> And an email on what they mean:
> http://ivtvdriver.org/pipermail/ivtv-users/2009-August/009513.html
>
> It saves much of the bit counting on a number of registers I
> recommended you might twiddle.
...
> Again, if you can test with the HVR-1600 and the "technician controls"
> patches, I'd do that.

Thank you, the HVR-1600 is installed, the v4l-dvb-ctls-c9f13db7a53e.tar.bz2
has been installed, /dev/video0 is functional (although the audio has some
annoying static; can that be modified?) and the dmesg output is:

cx18: Start initialization, version 1.2.0
cx18-0: Initializing card 0
cx18-0: Autodetected Hauppauge card
PCI: Enabling device 0000:03:05.0 (0010 -> 0012)
ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 18 (level, low) -> IRQ 217
cx18-0: cx23418 revision 01010000 (B)
tveeprom 0-0050: Hauppauge model 74591, rev C1A4, serial# 1685589
tveeprom 0-0050: MAC address is 00-0D-FE-19-B8-55
tveeprom 0-0050: tuner model is TCL MNM05-4 (idx 104, type 43)
tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 0-0050: audio processor is CX23418 (idx 38)
tveeprom 0-0050: decoder processor is CX23418 (idx 31)
tveeprom 0-0050: has no radio
cx18-0: Autodetected Hauppauge HVR-1600
cx18-0: Simultaneous Digital and Analog TV capture supported
tuner 1-0043: chip found @ 0x86 (cx18 i2c driver #0-1)
tda9887 1-0043: creating new instance
tda9887 1-0043: tda988[5/6/7] found
tuner 1-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
cs5345 0-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
tuner-simple 1-0061: creating new instance
tuner-simple 1-0061: type set to 43 (Philips NTSC MK3 (FM1236MK3 or
FM1236/F))
cx18-0: Registered device video0 for encoder MPEG (64 x 32 kB)
DVB: registering new adapter (cx18)
MXL5005S: Attached at address 0x63
DVB: registering adapter 0 frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)...
cx18-0: DVB Frontend registered
cx18-0: Registered DVB adapter0 for TS (32 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: Initialized card: Hauppauge HVR-1600
cx18: End initialization
cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332 bytes)
cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 (141200 bytes)
cx18-0: FW version: 0.0.74.0 (Release 2007/03/12)
cx18-0 843: loaded v4l-cx23418-dig.fw firmware (16382 bytes)
cx18-0 843: verified load of v4l-cx23418-dig.fw firmware (16382 bytes)

A look at some of the registers you previously mentioned yields:

# (for i in 0x402 0x40e 0x104 0x106; do ./v4l2-dbg --get-register=$i; done;
./v4l2-dbg --list-registers=min=0x488,max=0x49a) | grep -v VIDIOC
Register 0x00000402 = e587h (58759d 11100101 10000111b)
Register 0x0000040e = 1001e597h (268559767d 00010000 00000001 11100101
10010111b)
Register 0x00000104 = e7900104h (3884974340d 11100111 10010000 00000001
00000100b)
Register 0x00000106 = 6081e790h (1619126160d 01100000 10000001 11100111
10010000b)

00 04 08 0C 10 14 18
1C
00000480: e59f38a8 e5976060 e3a01000 e59f58a0 e59f88a0

I'll confess some confusion about the use of the "technician controls" you
mentioned in this version, as the v4l2-dbg output appears the same as the
other code.

I also understand that the aforementioned registers were on the cx2584x
chip. I'm not sure what registers to address on the cx18, as there's no
datasheet for it at http://dl.ivtvdriver.org/datasheets/video

Your (and Devin's, and anyone else's) help and guidance is much appreciated
and needed.

I may be able to find someone with knowledge of how to use their storage
oscilloscope. May I ask if it would somehow be helpful to grab the data
associated with one of the problem areas on the tape? What sort of request
should I make of the technician? I'm not familiar with such an instrument,
but if it's possible to email some kind of file with the "sillyscope"
output, then what would work best for you, if indeed you're willing and have
the time to deal with such a task?


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Andy Walls wrote:

> 2. It's been a long time (too long) since I worked anywhere with an
> oscilliscope available to me. :( So I would be fumbling in the dark
> as well.
>
> (Coincidentially, I just happen to be updating my resume right now.
> It looks like about 1998 when I last used an oscilliscope at work.)

Things have certainly changed considerably since then, such as:
http://www.elandigitalsystems.com/measurement/usbscope50.php

which (on the above page) has downloadable software for both Linux and that
other OS. It's stated that the freely-available software operates in demo
mode if no device is detected, so that might work well for evaluation
purposes. It would be better if they plainly stated the real-time sampling
rate though, instead of the equivalent-time.

Your experience with the historical intrumentation places you in a superior
position to those who only know the modern stuff (IMHO), but I've found that
it helps to spell résumé correctly. <g>

Skydiver compliments are always back-handed. These ancient VHS tapes I'm
working with, for instance, have one instructor who looks the same now as he
did 25+ years ago. When I announced that fact at the dropzone, I waited a
second or so and then added "... he's *always* looked old!"


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users