I have been using a PVR350 for the past 3 months or so and everything
worked great. I had to give it back so I ran out yesterday and bought a
PVR150 (since I use a video card for output to TV anyway).
Everything appears to start properly.
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.3.8 (tagged release) loading
ivtv: Linux version: 2.6.13-vivid1 preempt K7 gcc-3.4
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv: Autodetected WinTV PVR 150 card (iTVC16 based)
PCI: Found IRQ 12 for device 0000:00:09.0
ivtv: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom: Hauppauge: model = 26032, rev = C199, serial# = 8208980
tveeprom: tuner = TCL 2002N 5H (idx = 99, type = 50)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio processor = CX25841 (type = 23)
tveeprom: decoder processor = CX25841 (type = 1c)
ivtv: i2c attach to card #0 ok [client=tveeprom[50], addr=50]
tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv: i2c attach to card #0 ok [client=(tuner unset), addr=61]
cx25840: loading /lib/modules/HcwMakoA.ROM
ivtv: i2c attach to card #0 ok [client=cx25840[50], addr=44]
ivtv: i2c attach to card #0 ok [client=wm8775[50], addr=1b]
ivtv: loading /lib/modules/ivtv-fw-enc.bin
ivtv: Encoder revision: 0x02040011
ivtv: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #0
ivtv: Initialized WinTV PVR 150, card #0
ivtv: ==================== END INIT IVTV ====================
Watching TV on Myth everything looks ok (although seems slighly less
quality then the pvr350) and the audio works. However the remote now does
not work. lsinput no longer shows that it is 'detected'. Here is the output
from i2cdetect.
linuxbox driver # i2cdetect -a 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/1.
I will probe address range 0x00-0x7f.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX UU XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX XX UU XX XX XX XX XX XX XX XX XX XX XX
50: UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: 70 71 72 73 XX XX XX XX XX XX XX XX XX XX XX XX
Now I realize I could use a normal kernel and just compile lirc-i2c (which
ANNOYING doesn't compile under newer -mm patches, which -vivid uses) but it
seems odd this doesn't work. Is it simply not supported/implemented? Do I
have one of the more budget 150s?
Andrew.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
