Re: [ivtv-devel] PVR-150 and dvd compliant audio
it's been awhile, but i'm pretty sure it's all mpeg-2.. no mp3 audio. you might need to capture at a different bitrate (44.1 khz vs 48?) -tmk --- Steven Ellis [EMAIL PROTECTED] wrote: Am I correct in assuming that the PVR-150 produces an MP3 audio stream as part of the MPEG produced on /dev/video0? Is this true of all of the PVR cards, and is there no way to get MP2 audio from the card. At the moment as part of my post capture edit with avidemux2 I have to convert the audio to AC3 or MP2, but preserve the video stream. Steve ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] svn updated: hopefully this fixes SECAM audio
Le 9 oct. 05, à 23:02, Mark Weaver a écrit : Julien Pervillé wrote: PS: on a totaly different subject, what's up with the lirc driver turning unresponsive after a few minutes with the PVR 150 remote? It starts working just fine, then it silently stops working. I think this may be an issue with the i2c implementation on their IR chip, I produced a patch by reverse engineering changes that hauppauge made in the windows driver, apparently to address similar issues. See trac ticket #29 or http://www.blushingpenguin.com/mark/blog/?p=23 for the full details. If you do try it out, i'd be very interested in any results. Dear Mark, I will test it out tonight, but it looks promising. Thank you very much for the help! Cheers, Julienn ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] PVR-150 and dvd compliant audio
kevin thayer wrote: it's been awhile, but i'm pretty sure it's all mpeg-2.. no mp3 audio. you might need to capture at a different bitrate (44.1 khz vs 48?) I can use dvdauthor to produce a dvd based on the mpeg files generated from the PVR-150 but the audio won't work in any of my DVD players. I have other MP2 matertial, usually a DVB source, that does work fine. The stream is reported as 384K MPEG Audio 48K. Hence I assumed MP3 rather than MP2 audio. Steve ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] Hangs with ivtv 0.4.0 and MythTV 0.18.1
Hi! I'm just in the middle of upgrading a ivtv(ivtv-0.2.0-rc2r) / MythTV(0.16.0) setup that's about a year old. And I decided to try Ivtv 0.4.0 and MythTV 0.18.1. I'm using a PVR-350 and ivtv-fb to run Myth on, and do TV out. The host is running with root (and all filesystems) NFS mounted I've gotten everything compiled and installed, and seemingly in good shape UNTIL (you knew there had to be a catch! :), I start watching recorded shows, or live TV for more then a minute or two. If I'm using the recomended firmware pvr_1.18.21.22254_inf.zip the box will hang solid, with no records in the logs of why. Running with my previous firmware pvr_1.18.21.22168_inf.zip the playback crashes out, and oopses the kernel. (All details pasted in below!) Any ideas on where to go from here? Thanks in advance for any help! *** IVTV info and oops from older firmware *** Oct 10 01:13:23 boobtoob kernel: ivtv: START INIT IVTV Oct 10 01:13:23 boobtoob kernel: ivtv: version 0.4.0 (tagged release) loading Oct 10 01:13:23 boobtoob kernel: ivtv: Linux version: 2.6.13.3epia1 preempt VIAC3-2 gcc-4.0 Oct 10 01:13:23 boobtoob kernel: ivtv: In case of problems please include the debug info Oct 10 01:13:23 boobtoob kernel: ivtv: between the START INIT IVTV and END INIT IVTV lines when Oct 10 01:13:23 boobtoob kernel: ivtv: mailing the ivtv-devel mailinglist. Oct 10 01:13:23 boobtoob kernel: ivtv0: Autodetected WinTV PVR 350 card (iTVC15 based) Oct 10 01:13:23 boobtoob kernel: ivtv0: Unreasonably low latency timer, setting to 64 (was 32) Oct 10 01:13:23 boobtoob kernel: tveeprom: ivtv version Oct 10 01:13:23 boobtoob kernel: tveeprom: Hauppauge: model = 48132, rev = K168, serial# = 7519674 Oct 10 01:13:23 boobtoob kernel: tveeprom: tuner = LG TAPE H001F MK3 (idx = 68, type = 47) Oct 10 01:13:23 boobtoob kernel: tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x1000) Oct 10 01:13:23 boobtoob kernel: tveeprom: audio processor = MSP4448 (type = 1b) Oct 10 01:13:23 boobtoob kernel: tveeprom: decoder processor = SAA7115 (type = 13) Oct 10 01:13:23 boobtoob kernel: ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] Oct 10 01:13:23 boobtoob kernel: tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 Oct 10 01:13:23 boobtoob kernel: ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] Oct 10 01:13:23 boobtoob kernel: saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) Oct 10 01:13:23 boobtoob kernel: ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21] Oct 10 01:13:23 boobtoob kernel: saa7127 1-0044: saa7127 found @ 0x88 (ivtv i2c driver #0) Oct 10 01:13:23 boobtoob kernel: ivtv0: i2c attach to card #0 ok [client=saa7127, addr=44] Oct 10 01:13:23 boobtoob kernel: msp34xx: ivtv version Oct 10 01:13:23 boobtoob kernel: msp34xx: init: chip=MSP3448W-A2, has NICAM support, simple (D) mode, simpler (G) no-thread mode Oct 10 01:13:23 boobtoob kernel: msp34xx: $Id$ compiled on: Oct 9 2005 16:28:28 Oct 10 01:13:23 boobtoob kernel: ivtv0: i2c attach to card #0 ok [client=MSP3448W-A2, addr=40] Oct 10 01:13:23 boobtoob kernel: tda9885/6/7: (ivtv) chip found @ 0x86 Oct 10 01:13:23 boobtoob kernel: ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43] Oct 10 01:13:23 boobtoob kernel: PCI: Setting latency timer of device :00:11.5 to 64 Oct 10 01:13:23 boobtoob kernel: ivtv0: loading /lib/modules/ivtv-fw-enc.bin Oct 10 01:13:23 boobtoob kernel: ivtv0: loading /lib/modules/ivtv-fw-dec.bin Oct 10 01:13:23 boobtoob kernel: ivtv0: Encoder revision: 0x02040024 Oct 10 01:13:23 boobtoob kernel: ivtv0 warning: Encoder Firmware can be buggy, use version 0x02040011 or 0x02050032. Oct 10 01:13:23 boobtoob kernel: ivtv0: Decoder revision: 0x02020023 Oct 10 01:13:23 boobtoob kernel: ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) Oct 10 01:13:23 boobtoob kernel: ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) Oct 10 01:13:23 boobtoob kernel: ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) Oct 10 01:13:23 boobtoob kernel: ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) Oct 10 01:13:23 boobtoob kernel: ivtv0: Create encoder radio stream Oct 10 01:13:23 boobtoob kernel: ivtv0: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024KB total) Oct 10 01:13:23 boobtoob kernel: ivtv0: Allocate DMA decoder VBI stream: 512 x 2048 buffers (1024KB total) Oct 10 01:13:23 boobtoob kernel: ivtv0: Create decoder VOUT stream Oct 10 01:13:23 boobtoob kernel: ivtv0: Allocate DMA decoder YUV stream: 24 x 43200 buffers (1024KB total) Oct 10 01:13:23 boobtoob kernel: ivtv0: loading /lib/modules/ivtv_init_mpeg.bin Oct 10 01:13:23 boobtoob kernel: tuner: type set to 47 (LG NTSC (TAPE series)) by ivtv i2c driver #0 Oct 10 01:13:23 boobtoob kernel: spurious 8259A interrupt: IRQ7. Oct 10 01:13:23 boobtoob kernel: ivtv0: Initialized WinTV PVR 350, card #0 Oct
Re: [ivtv-devel] /dev/video0 doesn't return anything in radio mode
On Fri, Oct 07, 2005, Hans Verkuil wrote: I have retried with the latest SVN, and the behaviour has changed. When I switch to radio mode, every time I cat /dev/video0 /tmp/toto, it creates a /tmp/toto file of exactly 12224 bytes. It contains a pack header, a system header and the first I frame. It stops after that. Do you have any idea which changeset might have changed this behaviour ? This may be a hint as to where I must look. Thanks, Possible candidates: 2745, 2721. If it is the latter, then I'd advise testing encoder firmware 0x02040011 and 0x02050032 to see if there's any difference between them. Bingo ! I upgraded to firmware 0x02050032 and the problem disappears. Probably the information I have gathered on HcwMakoA.ROM and HcwFalcn.rom should be placed in the wiki when it is back up. Using the latest versions really makes problems disappear. Thanks a lot, -- Christophe Massiot Freebox S.A. ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] /dev/video0 doesn't return anything in radio mode
On 10/10/05, Christophe Massiot [EMAIL PROTECTED] wrote: On Fri, Oct 07, 2005, Hans Verkuil wrote: I have retried with the latest SVN, and the behaviour has changed. When I switch to radio mode, every time I cat /dev/video0 /tmp/toto, it creates a /tmp/toto file of exactly 12224 bytes. It contains a pack header, a system header and the first I frame. It stops after that. Do you have any idea which changeset might have changed this behaviour ? This may be a hint as to where I must look. Thanks, Possible candidates: 2745, 2721. If it is the latter, then I'd advise testing encoder firmware 0x02040011 and 0x02050032 to see if there's any difference between them. Bingo ! I upgraded to firmware 0x02050032 and the problem disappears. Probably the information I have gathered on HcwMakoA.ROM and HcwFalcn.rom should be placed in the wiki when it is back up. Using the latest versions really makes problems disappear. The wiki is back up, and that information is already on the wiki. Ross ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] 0.5 and backwards compatibility
Based on recent developments on v4l I think we should go with the initial idea: build v4l, then ivtv. In the meantime we keep 0.4 up to date with bug fixes and new features, at least for the duration of the 0.5 development series. Hans Hi Hans How can I help with 0.5 development? Best Regards Trev ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
RE: [ivtv-devel] Cannot install new 0.4.0 ivtv drivers
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Philip Rowlands Sent: Sunday, October 09, 2005 8:28 PM To: Discussion list for development of the IVTV driver Subject: Re: [ivtv-devel] Cannot install new 0.4.0 ivtv drivers Hi Phil... There is, somewhere on the disk, the older .ko module. Find out where by first rmmod'ing ivtv (however may be required; lsmod must show it absent), then run modprobe -v ivtv. This will print out the path of ivtv, and all dependant modules, as they load. I finally got 0.4.0 installed... First, I found that I had to rmmod lirc_i2c which then enabled rmmod ivtv to unload the old driver. Next, I ran find /lib/modules/`uname -r` -iname \*ivtv\* -ls (which is slightly different than the 'find' example on the HOWTO page), and found the 0.2.0 drivers hiding-- '/lib/modules/2.6.11-1.27_FC3/updates/drivers/media/video' contained: msp3400-ivtv.ko ivtv-fb.ko tuner-ivtv.ko ivtv.ko tveeprom-ivtv.ko ...slightly different naming convention than expected. ;) I renamed all of these by appending a '.HIDE', ran depmod -a and then modprobe -v ivtv and the 0.4.0 drivers were in place! After testing, I shut the MythTV box down completely and let it rest a few minutes, then booted it up. Curiously, kudzu popped up during the boot process, saying it had found new hardware and giving me the option to either configure it, (temporarily) ignore it, or permanently forget about it. Hmm... as I had just installed drivers for it, I chose to temporarily ignore it (meaning that kudzu will pop up again, next time I boot the machine) and see if it works with Myth. I'm happy to report that all appears to be working fine. Interesting, though... I don't remember kudzu popping up in the past, having discovered a video capture device - Brian ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Cannot install new 0.4.0 ivtv drivers
Hmmm. I was following Jarod's guide which uses apt to install precompiled binaries. I don't recall seeing anything like this, but I'll go back a look.On 10/9/05, Adam Forsyth [EMAIL PROTECTED] wrote: If you followed the mythtv on fedora guide preivously, you need toremove the ivtv rpms, depmod -a, and remake your initrd. You probablyforgot to do this last part.On 10/9/05, Philip Rowlands [EMAIL PROTECTED] wrote: On Sun, 9 Oct 2005, Brian wrote: I followed, faithfully, the directions given on the ivtvdriver.org HOWTO page.Despite 7.5 hours of constantly doing/redoing it, I'm still running 0.2.0 (rc3j), according to `modinfo ivtv`. (`ivtvctl -a` returns 'not an ivtv driver device'). [snip build info] running /sbin/modprobe ivtv as indicated on the HOWTO page, despite not being able to (even forcefully!) rmmod ivtv... produced no errors, warnings, or output of any kind. It's possible that the newer drivers, now having the necessary lines, have caused depmod to modify modules.pcimap and consequently may try to load ivtv and related modules on bootup. If this is happening, you will need to rmmod or reboot, which you report having done (albeit unsucessfully). modinfo ivtv version:0.2.0-68_rc3j.rhfc3.at There is, somewhere on the disk, the older .ko module. Find out where by first rmmod'ing ivtv (however may be required; lsmod must show it absent), then run modprobe -v ivtv. This will print out the path of ivtv, and all dependant modules, as they load. Cheers, Phil ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel___ivtv-devel mailing list ivtv-devel@ivtvdriver.orghttp://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [SOLVED!] Re: [ivtv-devel] Tried to install 0.4.0, now nothing will install... (ivtv make file???)
I apologize in advance if this isn't what you were talking about, or if this is too off topic or newbie-ish for this list. Mark Knecht wrote: What would your suggestion be for pair of rm and ln commands? Under /usr/src/ you should have one directory called something like 2.6.13-gentoo-r3 and another called 2.6.13-gentoo-r3-ht. You would then create a symlink to 'linux' from whichever one is currently running. To change it do 'rm linux' and 'ln -s 2.6.13-gentoo-r3 linux' (as appropriate.) For example, my /usr/src looks like this: [EMAIL PROTECTED]:/usr/src 2ls -l total 12 lrwxr-xr-x 1 root root 23 Aug 15 19:59 linux - linux-2.6.11-gentoo-r9/ drwxr-xr-x 19 root root 4096 Sep 10 13:00 linux-2.6.11-gentoo-r9 drwxr-xr-x 18 root root 4096 Sep 7 18:41 linux-2.6.12-gentoo-r10 drwxr-xr-x 18 root root 4096 Oct 6 10:14 linux-2.6.13-gentoo-r3 I have 3 different source trees installed, but the one I'm currently running (2.6.11-gentoo-r9) is the one that is linked to 'linux'. That way anything that looks in /usr/src/linux for the running kernel sources will find it. If I want to switch to 2.6.13-gentoo-r3 I would do this: [EMAIL PROTECTED]:/usr/src 1rm linux [EMAIL PROTECTED]:/usr/src 2ln -s linux-2.6.13-gentoo-r3/ linux Now the directory looks like this: [EMAIL PROTECTED]:/usr/src 3ls -l total 12 lrwxrwxrwx 1 root root 23 Oct 10 11:10 linux - linux-2.6.13-gentoo-r3/ drwxr-xr-x 19 root root 4096 Sep 10 13:00 linux-2.6.11-gentoo-r9 drwxr-xr-x 18 root root 4096 Sep 7 18:41 linux-2.6.12-gentoo-r10 drwxr-xr-x 18 root root 4096 Oct 6 10:14 linux-2.6.13-gentoo-r3 Daniel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] Problem with PVR-250 and PVR-500
Hi, I have two different hauppauge cards, and i have problems with both of them. I live in Sweden and uses Europe-pal. using .0.4.0 First of is a PVR-250. With this one i get a nice clear picture, but no sound (except for one channel. it has a label with PAL-B/G-I-D/K-SECAM 32059. Output from dmesg can be found below. The second card is a PVR-500 where i have sound, but quite bad reception (some channels are better than the others). Same thing on both tuners. This one has the following under the sticker on one of the tuner: FQ1216AME/R H-4 The output from dmesg can be found below. Any help would be appreciated allot! BR / Johan ivtv: START INIT IVTV ivtv: version 0.4.0 (tagged release) loading ivtv: Linux version: 2.6.10-5-686-smp SMP preempt 686 gcc-3.3 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. ivtv0: Autodetected WinTV PVR 250 card (iTVC16 based) ACPI: PCI interrupt :02:0a.0[A] - GSI 22 (level, low) - IRQ 22 tveeprom: ivtv version tveeprom: Hauppauge: model = 32059, rev = B143, serial# = 7263640 tveeprom: tuner = Temic 4046FM5 (idx = 43, type = 22) tveeprom: tuner fmt = PAL(B/G) PAL(I) SECAM(L/L') PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio processor = MSP4418 (type = 19) tveeprom: decoder processor = SAA7115 (type = 13) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21] msp34xx: ivtv version msp34xx: init: chip=MSP3418W-A2, has NICAM support, simple (D) mode, simpler (G) no-thread mode msp34xx: $Id$ compiled on: Oct 10 2005 17:44:36 ieee1394: Host added: ID:BUS[0-00:1023] GUID[00e0188d7503] ivtv0: i2c attach to card #0 ok [client=MSP3418W-A2, addr=40] ivtv0: loading /lib/modules/ivtv-fw-enc.bin ivtv0: Encoder revision: 0x02040011 ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv0: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total) ivtv0: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total) ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) tuner: type set to 22 (Temic PAL/SECAM multi (4046 FM5)) by ivtv i2c driver #0 ivtv0: Initialized WinTV PVR 250, card #0 ivtv: == NEXT CARD == ivtv1: Autodetected WinTV PVR 150 card (iTVC16 based) ACPI: PCI interrupt :03:08.0[A] - GSI 21 (level, low) - IRQ 21 tveeprom: Second (radio) tuner idx 101 tveeprom: ivtv version tveeprom: Hauppauge: model = 23559, rev = D591, serial# = 2989473 tveeprom: tuner = Philips FQ1216AME MK4 (idx = 91, type = 56) tveeprom: tuner fmt = PAL(B/G) PAL(I) SECAM(L/L') PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio processor = CX25843 (type = 25) tveeprom: decoder processor = CX25843 (type = 1e) ivtv1: i2c attach to card #1 ok [client=tveeprom, addr=50] tuner (ivtv): chip found at addr 0xc0 i2c-bus ivtv i2c driver #1 TEA5767 detected. ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=60] tuner: type set to 62 (Philips TEA5767HN FM Radio) by autodetect type set to 62 (Philips TEA5767HN FM Radio) tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #1 ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=61] tda9885/6/7: (ivtv) chip found @ 0x86 ivtv1: i2c attach to card #1 ok [client=tda9887, addr=43] ivtv1: This is the first unit of a PVR500 cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1) cx25840 2-0044: loaded /lib/modules/HcwMakoA.ROM firmware (14264 bytes) ivtv1: i2c attach to card #1 ok [client=cx25840, addr=44] wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1) ivtv1: i2c attach to card #1 ok [client=wm8775, addr=1b] ivtv1: Detected a TEA5767 radio tuner. Enabling radio support. ivtv1: loading /lib/modules/ivtv-fw-enc.bin ivtv1: Encoder revision: 0x02040011 ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv1: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total) ivtv1: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total) ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) ivtv1: Create encoder radio stream tuner: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4)) by ivtv i2c driver #1 ivtv1: Initialized WinTV PVR 500 (unit #1), card #1 ivtv: == NEXT CARD == ivtv2: Autodetected WinTV PVR 150 card (iTVC16 based) ACPI: PCI interrupt :03:09.0[A] - GSI 22 (level, low) - IRQ 22 tveeprom: Second (radio) tuner idx 101 tveeprom: ivtv version tveeprom: Hauppauge: model = 23559, rev = D591, serial# = 2989473 tveeprom: tuner = Philips FQ1216AME MK4 (idx = 91, type = 56)
Re: [ivtv-devel] ivtv 0.5.0 development
On Monday 10 October 2005 16:44, Mauro Carvalho Chehab wrote: Hans, Em Dom, 2005-10-09 às 17:44 +0200, Hans Verkuil escreveu: On Sunday 09 October 2005 17:27, Adam Forsyth wrote: It says right at the top of the the cvs info page that it often only works on the current -rc, and a patch is needed to make it work on the latest stable kernel. Is ther eany good reason compatibility isn't maintained? I get the feeling that backwards compatibility isn't a high priority. If you are talking about V4L, we have a period of two months without maintainer. During that period, we lost compatibility with 2.4. Also, some contributions were not tested with older versions. We did an effort to test backwards compat until 2.6.8. DVB is another history. They don't provide backward compatibility. In fact, their CVS is meant to compile on the latest -mm or -rc kernel version. We had to remove some DVB code from V4L three because of code conflicts caused by this. Also, DVB code on V4L is backward compatible with 2.6.12 and 2.6.13. With the merging scripts, we also provide compatibility with DVB development tree. We may provide backward compat with other DVB versions providing that somebody interested on it provide us patches for it. Sorry Mauro, I quickly realized I was mistaken and that I formed the wrong impression. My apologies for judging too quickly. It isn't helped by the crosslinks between the v4l and dvb repositories. And they've just restructured their repository, so that may also contribute. Anyway, I'm now looking at a way to keep a minimum subset with ivtv, preferably with just the unchanged v4l sources so that all I have to do is to copy them from v4l to ivtv. You may do it, if you wish. But it would be nice to keep duplicated codes read-only on ivtv. If you guys find a bug or want to send an improvement, please send to V4L mailing list for us to apply. Then, you may copy the newer version. This way, we will avoid having duplicated code, with different patchsets on it. As you may have read my earlier posting I've reconsidered. All supporting drivers are moved to v4l and during the transition period (at least until these drivers turn up in distributions like Fedora Core) we keep maintaining the stable 0.4 branch which still contains the copies of these drivers. Hans ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] Experience report v.0.4.0
Hi, I just upgraded to v.0.4.0 from v.0.2.0-r1. First I tried to compile under Debian sid, kernel-2.4.31 with gcc-4.0.1. It ended with this: gcc -D__KERNEL__ -D__KERNEL_SYSCALLS__ -DMODULE -DMODVERSIONS -DEXPORT_SYMTAB -I/lib/modules/2.4.31-ct-1/build/include -O2 -fomit-frame-pointer -march=i586 -mcpu=i586 -fno-strict-aliasing -Wno-unused -include /lib/modules/2.4.31-ct-1/build/include/linux/modversions.h-c -o msp3400.o msp3400.c `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead. In file included from /lib/modules/2.4.31-ct-1/build/include/linux/prefetch.h:13, from /lib/modules/2.4.31-ct-1/build/include/linux/list.h:6, from /lib/modules/2.4.31-ct-1/build/include/linux/module.h:13, from msp3400.c:38: /lib/modules/2.4.31-ct-1/build/include/asm/processor.h:75: error: array type has incomplete element type In file included from msp3400.c:45: /lib/modules/2.4.31-ct-1/build/include/linux/i2c.h:73: error: array type has incomplete element type /lib/modules/2.4.31-ct-1/build/include/linux/i2c.h:205: error: array type has incomplete element type msp3400.c: In function âmsp3400c_resetâ: msp3400.c:173: warning: pointer targets in initialization differ in signedness msp3400.c:174: warning: pointer targets in initialization differ in signedness msp3400.c:177: warning: pointer targets in initialization differ in signedness msp3400.c:178: warning: pointer targets in initialization differ in signedness msp3400.c:182: error: type of formal parameter 2 is incomplete msp3400.c:183: error: type of formal parameter 2 is incomplete msp3400.c:184: error: type of formal parameter 2 is incomplete msp3400.c: In function âmsp3400c_readâ: msp3400.c:206: error: type of formal parameter 2 is incomplete msp3400.c: In function âmsp3400c_writeâ: msp3400.c:241: warning: pointer targets in passing argument 2 of âi2c_master_sendâ differ in signedness msp3400.c: In function âmsp_commandâ: msp3400.c:2060: warning: pointer targets in passing argument 2 of âmsp34xxg_get_v4l2_stereoâ differ in signedness msp3400.c:2060: warning: pointer targets in passing argument 3 of âmsp34xxg_get_v4l2_stereoâ differ in signedness make[1]: *** [msp3400.o] Fehler 1 make[1]: Verlasse Verzeichnis »/root/ivtv-0.4.0/driver« make: *** [all] Fehler 2 Using gcc-3.4 in the Makefile made the source compile. After the firmware upgrade and the cold reboot I'm now using v.0.4.0 for 5 minutes in myth 0.18.1 without noticeable problems. Cheers, Steffen Dipl.-Wirtsch.-Inform. Steffen Becker, DFG Junior Research Group Palladio, Fk 2, Department of Computing Science, Software Engineering Group CvO Universität Oldenburg / OFFIS, Escherweg 2, D-26121 Oldenburg Email: [EMAIL PROTECTED] URL: http://se.informatik.uni-oldenburg.de Voice: +49 441 9722-582 (-501, secr.) Fax: +49 441 9722-502 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.13/126 - Release Date: 09.10.2005 ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] [ANNOUNCE] Improvements on V4L
Tyler Trafford wrote: Tyler Trafford wrote: Hans Verkuil wrote: On Monday 10 October 2005 01:38, Tyler Trafford wrote: Mauro Carvalho Chehab wrote: Latest V4L CVS version can be obtained at linuxtv.org: Hmm, tveeprom here doesn't work with my PVR150 tuner=50, but the one in 2.6.12 does, even loading ivtv with tuner=50 doesn't seem to work. Also, tda9887 is loading for some unknown reason. I'll have to figure out how to work with cvs to see what it could be. What is the ivtv 0.4.0 tveeprom output and what is the v4l tveeprom output? AFAIK the two should be identical as far as tuner detection is concerned. I synced them recently. I haven't used the ivtv one in about 8 months now... but the V4L one is saying it can't find any haupauge eeprom. I'll try with debugging turned on and post those results. Well, not much to post apparently, since tveeprom never outputs anything. It loads fine but never attaches to ivtv (and no, eeprom isn't loaded). I've installed 2.6.14-rc3 with v4l cvs, and now everything is working. It's possible this was operator error, so I'll see if I can get it to happen again. -- Tyler Trafford ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] What's the current state of /dev/video32 and /dev/video48?
Hi, Tommy Persson wrote: The size could be fixed by choosing another size in nvtv but I still think the aspect ratio is not entirelt correct but this can be my graphics card or its configuration. It seems that the image from mplayer is to high. PAL resolution of 720:576 == 5:4. So to display it correctly, it will have to be slightly rescaled. Since for me neither -aspect 4:3 nor -monitoraspect 4:3 worked (both made the window a bit wider but not the content), I used -x N/ -y M parameters for mplayer (with N/M either 720/540 or 768/576 - or anything else which is == 4/3). Or can it be a mplayer problem. Is the following expected output: [...] pretty much what I get too. As for the sound problem with /dev/video24: Since aplay -f dat /dev/video24 works perfectly, I can only assume that it has something to do with the -rawaudio parameters of mplayer. Cheers Martin ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] What's the current state of /dev/video32 and /dev/video48?
mt wrote: Hi, Tommy Persson wrote: The size could be fixed by choosing another size in nvtv but I still think the aspect ratio is not entirelt correct but this can be my graphics card or its configuration. It seems that the image from mplayer is to high. If you're using mplayer, you can always force the aspect ratio: mplayer -rawvideo on:w=574:h=488:hm12 -aspect 4:3 /dev/video32 Paul ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
Tim, I don't see that anywhere in Jarod's guide. Appreciate further info.On 10/10/05, Timothy McFadden [EMAIL PROTECTED] wrote:Also check to see if you used Jarod's mkinit-rd patch to include the ivtv drivers.You need to re-make the initial ramdisk with the newdrivers installed.-Tim___ivtv-devel mailing list ivtv-devel@ivtvdriver.orghttp://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
I now have the right version of the ivtv driver loading. To do this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the driver properly. I was using 2.6-10.x and there appears to be no prepackaged ivtv 0.3.x driver for this kernel. Now, having gotten the ivtv driver corrected, I seem to have introduced another problem with a number of unknown symbols, as shown below in dmesg output. Can anyone shed any light on this? I also read that the ivtv version of tuner, tveeprom, and msp3400 must be used. I played around with renaming the kernel version of the drivers, in an attempt to force the system to laod the ivtv version. But I put everything back to the way it was at the start, and below is the modinfo output. I am concerned that perhaps I am not loading the correct version of these modules? Many thanks from a frustrated PVR-500 owner. snip ivtv: START INIT IVTV ivtv: version 0.3.8 (tagged release) loading ivtv: Linux version: 2.6.12-1.1378_FC3 686 REGPARM 4KSTACKS 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) ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 3 PCI: setting IRQ 3 as level-triggered ACPI: PCI Interrupt :02:08.0[A] - Link [LNK3] - GSI 3 (level, low) - IRQ 3 ivtv: Unreasonably low latency timer, setting to 64 (was 32) tveeprom: Hauppauge: model = 23552, rev = D592, serial# = 8221024 tveeprom: tuner = Philips FQ1236A MK4 (idx = 92, type = 57) tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x1000) tveeprom: audio processor = CX25843 (type = 25) tveeprom: decoder processor = CX25843 (type = 1e) ivtv: i2c attach to card #0 ok [client=tveeprom[50], addr=50] ivtv: This is the first unit of a PVR500 tuner: chip found at addr 0xc0 i2c-bus ivtv i2c driver #0 TEA5767 detected. ivtv: i2c attach to card #0 ok [client=(tuner unset), addr=60] tuner: type set to 62 (Philips TEA5767HN FM Radio) by autodetect type set to 62 (Philips TEA5767HN FM Radio) 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] tda9885/6/7: chip found @ 0x86 ivtv: i2c attach to card #0 ok [client=tda9887, addr=43] ivtv: Detected a TEA5767 radio tuner. Enabling radio support. ivtv: loading /lib/modules/ivtv-fw-enc.bin ivtv: Encoder revision: 0x02040024 ivtv warning: Encoder Firmware can be buggy, use version 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) ivtv: Create encoder radio stream tuner: type set to 57 (Philips FQ1236A MK4) by ivtv i2c driver #0 ivtv: Initialized WinTV PVR 500 (unit #1), card #0 ivtv: == NEXT CARD == ivtv: Autodetected WinTV PVR 150 card (iTVC16 based) ACPI: PCI Interrupt Link [LNK4] enabled at IRQ 5 PCI: setting IRQ 5 as level-triggered ACPI: PCI Interrupt :02:09.0[A] - Link [LNK4] - GSI 5 (level, low) - IRQ 5 ivtv: Unreasonably low latency timer, setting to 64 (was 32) tveeprom: Hauppauge: model = 23552, rev = D592, serial# = 8221024 tveeprom: tuner = Philips FQ1236A MK4 (idx = 92, type = 57) tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x1000) tveeprom: audio processor = CX25843 (type = 25) tveeprom: decoder processor = CX25843 (type = 1e) ivtv: i2c attach to card #1 ok [client=tveeprom[50], addr=50] tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #1 ivtv: i2c attach to card #1 ok [client=(tuner unset), addr=61] cx25840: loading /lib/modules/HcwMakoA.ROM ivtv: i2c attach to card #1 ok [client=cx25840[50], addr=44] ivtv: i2c attach to card #1 ok [client=wm8775[50], addr=1b] tda9885/6/7: chip found @ 0x86 ivtv: i2c attach to card #1 ok [client=tda9887, addr=43] ivtv: This is the second unit of a PVR500 ivtv: Correcting tveeprom data: no radio present on second unit ivtv: loading /lib/modules/ivtv-fw-enc.bin ivtv: Encoder revision: 0x02040024 ivtv warning: Encoder Firmware can be buggy, use version 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 57 (Philips FQ1236A MK4) by ivtv i2c driver #1 ivtv: Initialized WinTV PVR 500 (unit #2), card #1 ivtv: END INIT IVTV lirc_dev: IR
Re: [ivtv-devel] Tried to install 0.4.0, now nothing will install...
dragonfly ivtv-0.4.0 # /lib/modules/`uname -r`/ivtv/ -bash: /lib/modules/2.6.13-gentoo-r3/ivtv/: No such file or directory dragonfly ivtv-0.4.0 # As I said, ivtv doesn't get installed! try making the /lib/modules/2.6.13-gentoo-r3/ivtv directory before hand? try running make KVER=2.6.13-gentoo-r3 make install KVER=2.6.13-gentoo-r3 instead of just make make install ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
One additional thing I fergot to mention. If I take out the 3 alias commands from modprobe.conf: alias tveeprom tveeprom-ivtv alias tuner tuner-ivtv alias msp3400 msp3400-ivtv The unknown module messages go away in the dmesg output. Then, the modprobe info looks the same as above. Any advice appreciated. On 10/9/05, Philip Rowlands [EMAIL PROTECTED] wrote: On Sun, 9 Oct 2005, Larry K wrote:Is something wrong here? Does 0.2.0 in this context mean that I'm notloading the 0.3.8 driver?Yes; see the very recent archives for the Cannot install new 0.4.0 ivtvdrivers thread.Cheers,Phil___ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
On Monday 10 October 2005 22:13, Larry K wrote: I now have the right version of the ivtv driver loading. To do this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the driver properly. I was using 2.6-10.x and there appears to be no prepackaged ivtv 0.3.x driver for this kernel. Now, having gotten the ivtv driver corrected, I seem to have introduced another problem with a number of unknown symbols, as shown below in dmesg output. Can anyone shed any light on this? I also read that the ivtv version of tuner, tveeprom, and msp3400 must be used. I played around with renaming the kernel version of the drivers, in an attempt to force the system to laod the ivtv version. But I put everything back to the way it was at the start, and below is the modinfo output. I am concerned that perhaps I am not loading the correct version of these modules? Many thanks from a frustrated PVR-500 owner. bttv: disagrees about version of symbol tveeprom_hauppauge_analog bttv: Unknown symbol tveeprom_hauppauge_analog cx88xx: disagrees about version of symbol tveeprom_hauppauge_analog cx88xx: Unknown symbol tveeprom_hauppauge_analog Well, I do know what is wrong, but I don't know why you are bitten by it. The tveeprom_hauppauge_analog() function in tveeprom.c has an extra client argument in the upcoming 2.6.14 kernel. However, it looks like your kernel has that extra argument already. Can you check tveeprom.c from your kernel tree (it should be in drivers/media/video) and report if the function looks like this: void tveeprom_hauppauge_analog(struct i2c_client *c, struct tveeprom *tvee, unsigned char *eeprom_data) or this: void tveeprom_hauppauge_analog(struct tveeprom *tvee, unsigned char *eeprom_data) Note the extra i2c_client pointer in the first. One option is not to use the ivtv tveeprom but the one from the kernel. This should work. Alternatively you can edit tveeprom.c in ivtv to add the 'struct i2c_client *c' argument. Hans ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
On Oct 10, 2005, at 3:13 PM, Larry K wrote: I now have the right version of the ivtv driver loading. To do this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the driver properly. I was using 2.6-10.x and there appears to be no prepackaged ivtv 0.3.x driver for this kernel. Now, having gotten the ivtv driver corrected, I seem to have introduced another problem with a number of unknown symbols, as shown below in dmesg output. Can anyone shed any light on this? I also read that the ivtv version of tuner, tveeprom, and msp3400 must be used. I played around with renaming the kernel version of the drivers, in an attempt to force the system to laod the ivtv version. But I put everything back to the way it was at the start, and below is the modinfo output. I am concerned that perhaps I am not loading the correct version of these modules? well, we do recommend that you use the ivtv versions. But you have some problems below. Many thanks from a frustrated PVR-500 owner. snip bttv: disagrees about version of symbol tveeprom_hauppauge_analog bttv: Unknown symbol tveeprom_hauppauge_analog cx88xx: disagrees about version of symbol tveeprom_hauppauge_analog Why is cx88xx loading? You have another capture card in there somewhere? And if you do, this is a conflict where the kernel cx88xx module will not use the ivtv tveeprom. So you'll have to use the kernel version of tveeprom. Here is my modprobe.conf: snip #ivtv PVR500 alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 ivtv alias tveeprom tveeprom-ivtv alias tuner tuner-ivtv alias msp3400 msp3400-ivtv These aliases are from the atrpms version of the modules. if you look in /lib/modules/2.6.12-1.1378_FC3/ivtv, you'll probably see that there is a tveeprom-ivtv.ko in there instead of the normal tveeprom.ko. [EMAIL PROTECTED] ~]# modinfo tveeprom filename: /lib/modules/2.6.12-1.1378_FC3/kernel/drivers/media/ video/tveeprom.ko As a result, this means nothing. Yes, this is the modinfo for tveeprom, but you're actually loading tveeprom-ivtv. So, this really boils down to a couple of things: 1. You're loading cx88xx for some reason or another and it doesn't like the ivtv version of tveeprom. If you need cx88xx for something, then you'll need the kernel version of tveeprom to get it working. 2. The naming scheme of atrpms' ivtv modules is confusing you and/or your kernel. Just saw your newest email. You can use the kernel versions of tveeprom and tuner, but you must use the ivtv version of msp3400. Keith C ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
On 10/10/05, Keith C [EMAIL PROTECTED] wrote: On Oct 10, 2005, at 3:13 PM, Larry K wrote: I now have the right version of the ivtv driver loading.To do this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the driver properly.I was using 2.6-10.x and there appears to be no prepackaged ivtv 0.3.x driver for this kernel. Now, having gotten the ivtv driver corrected, I seem to have introduced another problem with a number of unknown symbols, as shown below in dmesg output.Can anyone shed any light on this? I also read that the ivtv version of tuner, tveeprom, and msp3400 must be used.I played around with renaming the kernel version of the drivers, in an attempt to force the system to laod the ivtv version.But I put everything back to the way it was at the start, and below is the modinfo output.I am concerned that perhaps I am not loading the correct version of these modules?well, we do recommend that you use the ivtv versions.But you havesome problems below. Many thanks from a frustrated PVR-500 owner. snip bttv: disagrees about version of symbol tveeprom_hauppauge_analog bttv: Unknown symbol tveeprom_hauppauge_analog cx88xx: disagrees about version of symbol tveeprom_hauppauge_analog Why is cx88xx loading?You have another capture card in theresomewhere?And if you do, this is a conflict where the kernel cx88xxmodule will not use the ivtv tveeprom.So you'll have to use the kernel version of tveeprom. I don't have anything installed except the PVR-500MCE. I have no idea why cx88xx is loading. The machine has the pvr-500 and an nvidia video card. That's it. Here is my modprobe.conf: snip #ivtv PVR500 alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 ivtv alias tveeprom tveeprom-ivtv alias tuner tuner-ivtv alias msp3400 msp3400-ivtvThese aliases are from the atrpms version of the modules.if you look in/lib/modules/2.6.12-1.1378_FC3/ivtv, you'll probably seethat there is a tveeprom-ivtv.ko in there instead of the normaltveeprom.ko. [EMAIL PROTECTED] ~]# modinfo tveeprom filename: /lib/modules/2.6.12- 1.1378_FC3/kernel/drivers/media/ video/tveeprom.koAs a result, this means nothing.Yes, this is the modinfo fortveeprom, but you're actually loading tveeprom-ivtv.So, this really boils down to a couple of things: 1.You're loading cx88xx for some reason or another and it doesn'tlike the ivtv version of tveeprom.If you need cx88xx for something,then you'll need the kernel version of tveeprom to get it working.2.The naming scheme of atrpms' ivtv modules is confusing you and/or your kernel.Just saw your newest email.You can use the kernel versions oftveeprom and tuner, but you must use the ivtv version of msp3400. I'm not sure whether or not I need to include the alias stuff in modprobe. If I do, I get the errors. If I don't, the errors go away, but I'm not sure if I am loading the right modules Keith C___ivtv-devel mailing list ivtv-devel@ivtvdriver.orghttp://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Re: ivtv 0.5.0 development
2.6.13-1.1526_FC4 So, what I've done in this: checkout the v4l-kernel and dvb-kernel sources. Then make merge-trees -- works fine make --- has errors relating to a single header file. If I edit Make.config to remove the few lines Michael suggested, I get that file only included in two places: cx88.h and saa7134.h. The include is set to be for any 2.6 kernel -- but it won't work for me on 2.6.13. So, I change the version to be 2.6.14 and above. That doesn't cause any errors in cx88.h, but it leaves NOTIFY_WAIT and a few other things still as problems in saa7134-core.c. On 10/10/05, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: Adam, What's your kernel version? This code is meant for 2.6 kernels (but, in fact, we know for sure that it works from 2.6.8 and above). For 2.4, there is another code. ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
I don't have the tveeprom.c anywhere on my system ( I searched for it like so: find / -name tveeprom.c). I suspect I am using the kernel version of tveeprom now. However, I still have the original issue that is the source of my angst: I get good audio and video on /video1, but nothing but static (no sound) on /video0. Axel Thimm, Jarod Wilson, et. al., maintains the atrpm stuff at http://atrpms.net/ I can try to contact them. Do you know those guys?On 10/10/05, Hans Verkuil [EMAIL PROTECTED] wrote: On Monday 10 October 2005 22:50, Larry K wrote: Hans, I'm not working from source. I pulled the compiled kernel from atrpms like so: apt-get install kernel=2.6.12-1.1378_FC3 Do you have any other ideas as to how I can pursue this?In that case just use the kernel tveeprom (or edit ivtv tveeprom.c as per myprevious email). Can someone else check just which tveeprom.c is included inthat kernel?Hans___ivtv-devel mailing listivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
Keith C wrote: On Oct 10, 2005, at 3:13 PM, Larry K wrote: I now have the right version of the ivtv driver loading. To do this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the driver properly. I was using 2.6-10.x and there appears to be no prepackaged ivtv 0.3.x driver for this kernel. Now, having gotten the ivtv driver corrected, I seem to have introduced another problem with a number of unknown symbols, as shown below in dmesg output. Can anyone shed any light on this? I also read that the ivtv version of tuner, tveeprom, and msp3400 must be used. I played around with renaming the kernel version of the drivers, in an attempt to force the system to laod the ivtv version. But I put everything back to the way it was at the start, and below is the modinfo output. I am concerned that perhaps I am not loading the correct version of these modules? well, we do recommend that you use the ivtv versions. But you have some problems below. Personally, I only recommend ivtv versions of tveeprom and tuner if the kernel ones already contain the right definitions. Go with the kernel ones if you can. msp3400 is a different story. -- Tyler Trafford ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Problem with PVR-250 and PVR-500
1. Do you have any module options specified? 2. Make sure you are using the newest firmware versions: http://ivtvdriver.org/index.php/Firmware On 10/10/05, Johan Asterholm [EMAIL PROTECTED] wrote: Hi, I have two different hauppauge cards, and i have problems with both of them. I live in Sweden and uses Europe-pal. using .0.4.0 First of is a PVR-250. With this one i get a nice clear picture, but no sound (except for one channel. it has a label with PAL-B/G-I-D/K-SECAM 32059. Output from dmesg can be found below. The second card is a PVR-500 where i have sound, but quite bad reception (some channels are better than the others). Same thing on both tuners. This one has the following under the sticker on one of the tuner: FQ1216AME/R H-4 The output from dmesg can be found below. Any help would be appreciated allot! BR / Johan ivtv: START INIT IVTV ivtv: version 0.4.0 (tagged release) loading ivtv: Linux version: 2.6.10-5-686-smp SMP preempt 686 gcc-3.3 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. ivtv0: Autodetected WinTV PVR 250 card (iTVC16 based) ACPI: PCI interrupt :02:0a.0[A] - GSI 22 (level, low) - IRQ 22 tveeprom: ivtv version tveeprom: Hauppauge: model = 32059, rev = B143, serial# = 7263640 tveeprom: tuner = Temic 4046FM5 (idx = 43, type = 22) tveeprom: tuner fmt = PAL(B/G) PAL(I) SECAM(L/L') PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio processor = MSP4418 (type = 19) tveeprom: decoder processor = SAA7115 (type = 13) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21] msp34xx: ivtv version msp34xx: init: chip=MSP3418W-A2, has NICAM support, simple (D) mode, simpler (G) no-thread mode msp34xx: $Id$ compiled on: Oct 10 2005 17:44:36 ieee1394: Host added: ID:BUS[0-00:1023] GUID[00e0188d7503] ivtv0: i2c attach to card #0 ok [client=MSP3418W-A2, addr=40] ivtv0: loading /lib/modules/ivtv-fw-enc.bin ivtv0: Encoder revision: 0x02040011 ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv0: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total) ivtv0: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total) ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) tuner: type set to 22 (Temic PAL/SECAM multi (4046 FM5)) by ivtv i2c driver #0 ivtv0: Initialized WinTV PVR 250, card #0 ivtv: == NEXT CARD == ivtv1: Autodetected WinTV PVR 150 card (iTVC16 based) ACPI: PCI interrupt :03:08.0[A] - GSI 21 (level, low) - IRQ 21 tveeprom: Second (radio) tuner idx 101 tveeprom: ivtv version tveeprom: Hauppauge: model = 23559, rev = D591, serial# = 2989473 tveeprom: tuner = Philips FQ1216AME MK4 (idx = 91, type = 56) tveeprom: tuner fmt = PAL(B/G) PAL(I) SECAM(L/L') PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio processor = CX25843 (type = 25) tveeprom: decoder processor = CX25843 (type = 1e) ivtv1: i2c attach to card #1 ok [client=tveeprom, addr=50] tuner (ivtv): chip found at addr 0xc0 i2c-bus ivtv i2c driver #1 TEA5767 detected. ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=60] tuner: type set to 62 (Philips TEA5767HN FM Radio) by autodetect type set to 62 (Philips TEA5767HN FM Radio) tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #1 ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=61] tda9885/6/7: (ivtv) chip found @ 0x86 ivtv1: i2c attach to card #1 ok [client=tda9887, addr=43] ivtv1: This is the first unit of a PVR500 cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1) cx25840 2-0044: loaded /lib/modules/HcwMakoA.ROM firmware (14264 bytes) ivtv1: i2c attach to card #1 ok [client=cx25840, addr=44] wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1) ivtv1: i2c attach to card #1 ok [client=wm8775, addr=1b] ivtv1: Detected a TEA5767 radio tuner. Enabling radio support. ivtv1: loading /lib/modules/ivtv-fw-enc.bin ivtv1: Encoder revision: 0x02040011 ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv1: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total) ivtv1: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total) ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) ivtv1: Create encoder radio stream tuner: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4)) by ivtv i2c driver #1 ivtv1: Initialized WinTV PVR 500 (unit #1), card #1 ivtv: == NEXT CARD == ivtv2: Autodetected WinTV
Re: [ivtv-devel] Noob question about ivtv driver version
I can certainly install the card on my win2k machine as a test. What I'm doing now to test the card is to cat from /dev/video0 and /dev/video1, like so: # /usr/bin/ivtvctl -u 0x3000 -d /dev/video0 # /usr/bin/ivtvctl -p 6 -d /dev/video0 # /usr/bin/ivtvctl -f width=720,height=480 -d /dev/video0 # cat /dev/video0 /tmp/test_capture0.mpg (ctrl-c to stop capture) # mplayer -vo xv /tmp/test_capture0.mpg # /usr/bin/ivtvctl -u 0x3000 -d /dev/video1 # /usr/bin/ivtvctl -p 6 -d /dev/video1 # /usr/bin/ivtvctl -f width=720,height=480 -d /dev/video1 # cat /dev/video1 /tmp/test_capture1.mpg (ctrl-c to stop capture) # mplayer -vo xv /tmp/test_capture1.mpg Under this scenario, only /dev/video1 produces a playable file. /dev/video0 produces lots of static, and no audio.On 10/10/05, Hans Verkuil [EMAIL PROTECTED] wrote:On Monday 10 October 2005 23:08, Larry K wrote: I don't have the tveeprom.c anywhere on my system ( I searched for it like so: find / -name tveeprom.c). I suspect I am using the kernel version of tveeprom now. However, I still have the original issue that is the source of my angst: I get good audio and video on /video1, but nothing but static (no sound) on /video0.Can you test under Windows? It sounds like a hardware problem to me. I doassume that you tuned both tuners to the same channel? I also assume that you have no other TV cards in your system and are not mixing up /dev/videoXdevices :-)Hans___ivtv-devel mailing list ivtv-devel@ivtvdriver.orghttp://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
This problem has come up on the list several times before. lirc_i2c sometimes pulls in the cx88xx module for some reason (doesn't happen to me any more, but did until fairly recently) and that conflicts with the ivtv version of tveeprom. For me, editing tveeprom.c did NOT fix the problem, I still got the same error. The solution is to use the tveeprom.ko that came with your kernel. I definately had this problem with 2.6.12-*_FC3. ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] rewritten ivtvfbctl using getopt
I've rewritten ivtvfbctl using getopt. http://ivtvdriver.org/trac/attachment/ticket/38/ivtvfbctl.c?format=raw It seemed to be too big to send to the list. Please test it, as I can't because I don't have a tv right now. Note that I have cleaned up a few typos and the patch is attached (just so you don't correct things I've already fixed) ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
Why is cx88xx loading? You have another capture card in there somewhere? And if you do, this is a conflict where the kernel cx88xx module will not use the ivtv tveeprom. So you'll have to use the kernel version of tveeprom. I don't have anything installed except the PVR-500MCE. I have no idea why cx88xx is loading. The machine has the pvr-500 and an nvidia video card. That's it. Then you should probably look into why bttv/cx88xx is loading. Thats not a good thing. Look through dmesg for more bttv and cx88xx and see what else is going on there. Here is my modprobe.conf: snip #ivtv PVR500 alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 ivtv alias tveeprom tveeprom-ivtv alias tuner tuner-ivtv alias msp3400 msp3400-ivtv I'm not sure whether or not I need to include the alias stuff in modprobe. If I do, I get the errors. If I don't, the errors go away, but I'm not sure if I am loading the right modules Let me clarify this a little. If you use the kmdls from atrpms, and don't rename anything at all, and you want to use the ivtv versions of everything, then you MUST have the alias lines in modprobe.conf. Because thats what the ivtv modules are named in atrpms. Its a failsafe device added by Axel to ensure that linux newbies don't get the wrong modules loaded. But, the kernel version of bttv and cx88xx are not compatible with the ivtv version of tveeprom. So you'll get those unknown symbol errors when those modules are loaded. But if you really don't need those modules, no harm done. A lot of people can use the kernel versions of tuner and tveeprom. I don't think you're going to be one of them, because your kernel is too old to have the sync stuff that Hans has been committing to the v4l repository. So you'll need the ivtv versions, and you'll have those unknown symbols errors. If you want to try the kernel version of tveeprom and/or tuner, only remove those alias lines. Leave the msp3400 line there to force it to use the ivtv version. I just saw Adam's response that its lirc_i2c that is trying to load bttv and cx88xx. You could try blacklisting those modules from loading, but that might cause lirc_i2c to fail as well. Keith C ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [SOLVED!] Re: [ivtv-devel] Tried to install 0.4.0, now nothing will install... (ivtv make file???)
Hi, from my experience: - I don't have /usr/src/linux at all since my last update about 2 weeks ago (for me, /usr/src always was a link to /var/src anyways and this I removed). It is not needed for ivtv or lirc (the 2 modules I recompile after a kernel update). I think this /usr/src/linux stuff is deprecated (although some software indeed may rely on it) - When the modules are installed, links are put into /lib/modules/kernelversion, pointing to the src and build directory (which, in my case, are identical) - If I understand it correctly, ivtv uses this information as well as information about the currently running kernel (the uname -a) to find stuff needed for compilation. To me it seems that it is doing everything correctly So to me it appears that it is a Bad Thing to build different kernels within the same source tree, because then the links I mentioned above point to the same directory, but only for one kernel it actually contains the correct files. It will probably work, if you use different build directories (I never did that). Please correct me if I'm wrong, since I'm not exactly a Kernel Hacker. Martin Mark Knecht wrote: On 10/10/05, Daniel Segel [EMAIL PROTECTED] wrote: I apologize in advance if this isn't what you were talking about, or if this is too off topic or newbie-ish for this list. Mark Knecht wrote: What would your suggestion be for pair of rm and ln commands? Under /usr/src/ you should have one directory called something like 2.6.13-gentoo-r3 and another called 2.6.13-gentoo-r3-ht. You would then create a symlink to 'linux' from whichever one is currently running. To change it do 'rm linux' and 'ln -s 2.6.13-gentoo-r3 linux' (as appropriate.) This suggestion I understand and is what I would normally do. However, in this case I only had /usr/src/linux-2.6.13-gentoo-r3 and a link that pointed to it. What I did in this case was build the kernel with no extra post-pend to the name. The kernel came out as 2.6.13-gentoo-r3. That installed and ran. I wanted to try SMP/Hyper-threading so I entered the same source code tree, enabled SMP, added a post-pend name of -ht in the kernel config. The kernel compiled and installed as 2.6.13-gentoo-r3-ht. I now have both /lib/modules/2.6.13-gentoo-r3 /lib/modules/2.6.13-gentoo-r3-ht with the config file sitting in the -ht state. For various reasons I'm still mainly running the non-SMP kernel, but the kernel config is sitting in the SMP state. I go to build ivtv. It builds and tells me it's installing the drivers into 2-6-13-gentoo-r3, but it actually installed them in 2.6.13-gentoo-r3-ht. While I consider this weak, and I don't like that it works that way, at least I understand that it's under my control. I now have two copies of the same kernel source, the second renamed to -ht. The only difference between the two is that the config files have been changed. Now everything works. I have not tried ivtv under the -ht kernel yet. Possibly tomorrow. Thanks, Mark ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] svn 0.5 repository: should be OK tomorrow
I'm busy reorganizing ivtv-0.5. I had hoped to finish it today but I don't have enough time (well, not if I want to stay awake tomorrow :-). However I expect to complete it tomorrow. BTW, Mauro has already merged msp3400 into v4l, so that saves a lot of time. Thanks, Mauro! Hans ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
I don't have anything installed except the PVR-500MCE. I have no idea why cx88xx is loading. The machine has the pvr-500 and an nvidia video card. That's it. Then you should probably look into why bttv/cx88xx is loading. Thats not a good thing. Look through dmesg for more bttv and cx88xx and see what else is going on there. lirc is pulling in cx88xx, and doesn't seem to work without it on 2.6.12*FC3 kernels for me with a pvr350. Using the kernel tveeprom allows this to happen without issue. bttv used to get pulled in for me at some point too, but it doesn't cause any problems. Let me clarify this a little. If you use the kmdls from atrpms, and don't rename anything at all, and you want to use the ivtv versions of everything, then you MUST have the alias lines in modprobe.conf. Because thats what the ivtv modules are named in atrpms. Its a failsafe device added by Axel to ensure that linux newbies don't get the wrong modules loaded. I'm pretty sure that's only true for the 0.2 versions NOT the 0.3.8 / now 0.4 versions (the default) from atrpms, thus him getting the errors. But, the kernel version of bttv and cx88xx are not compatible with the ivtv version of tveeprom. So you'll get those unknown symbol errors when those modules are loaded. But if you really don't need those modules, no harm done. It will cause lirc not to work on 0.3.* / 2.6.12*FC3 with a pvr350 at least for me. A lot of people can use the kernel versions of tuner and tveeprom. I don't think you're going to be one of them, because your kernel is too old to have the sync stuff that Hans has been committing to the v4l repository. So you'll need the ivtv versions, and you'll have those unknown symbols errors. This is not correct for tveeprom I think. It should work anyways. If you want to try the kernel version of tveeprom and/or tuner, only remove those alias lines. Leave the msp3400 line there to force it to use the ivtv version. Again, I don't think that's correct since he's using 0.4 not 0.2. I just saw Adam's response that its lirc_i2c that is trying to load bttv and cx88xx. You could try blacklisting those modules from loading, but that might cause lirc_i2c to fail as well. He's better off using the kernel tveeprom which should work fine. Keith C ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [SOLVED!] Re: [ivtv-devel] Tried to install 0.4.0, now nothing will install... (ivtv make file???)
mt wrote: So to me it appears that it is a Bad Thing to build different kernels within the same source tree, because then the links I mentioned above point to the same directory, but only for one kernel it actually contains the correct files. It will probably work, if you use different build directories (I never did that). Please correct me if I'm wrong, since I'm not exactly a Kernel Hacker. This is exactly right. If you need multiple kernels from a tree, copy it with 'cp -al' to a new location. -- Tyler Trafford ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] PVR150 Firmware load error?
On 10/10/05, Kieron Wilkinson [EMAIL PROTECTED] wrote: I managed to find out what was causing my problem. I had a duplicate version of the ivtv modules installed in /lib/modules/'uname -r'/extra (which were prefixed by 'ivtv-'). Once I had got rid of the module loaded fine! Yay! Did you previously install from a package, or from source? Old versions of ivtv put the modules in a different location, so they don't get overwritten by the new version. (not specific to suse). I'm going to update the wiki with this info shortly. Side note: should the makefile include this sort of check, like what it does for v4l tveeprom, tuner, etc, modules? Cheers, Ross ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] Re: Noob question about ivtv driver version
On Mon, Oct 10, 2005 at 05:13:45PM -0500, Keith C wrote: Here is my modprobe.conf: snip #ivtv PVR500 alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 ivtv alias tveeprom tveeprom-ivtv alias tuner tuner-ivtv alias msp3400 msp3400-ivtv I'm not sure whether or not I need to include the alias stuff in modprobe. If I do, I get the errors. If I don't, the errors go away, but I'm not sure if I am loading the right modules Let me clarify this a little. If you use the kmdls from atrpms, and don't rename anything at all, and you want to use the ivtv versions of everything, then you MUST have the alias lines in modprobe.conf. Because thats what the ivtv modules are named in atrpms. Its a failsafe device added by Axel to ensure that linux newbies don't get the wrong modules loaded. Keith is correct. This mechanism allows to deploy ivtv's versions and have the user choose between the kernel's version (no aliases) and ivtv's version (with the aliases). This was introduced a year or so ago, when a first attempt was made to get msp3400 merged back to v4l/kernel, and a fast method of comparing them was needed. My recommendation (for now and future) is: Try w/o any aliases and if something doesn't work add them one by one. E.g. bad detection, then try ivtv's tveeprom and tuner modules, bad sound, then try ivtv's msp3400. And please report successes and failures as feedback for the ongoing merge efforts! -- Axel.Thimm at ATrpms.net pgplpJAvRt2vh.pgp Description: PGP signature ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] ivtv 0.2 vs. 0.4 deathmatch
I had *thought* that I had perceived a quality difference betwee the 0.2rc driver and the 3.9 driver. Over the weekend, I finally got to try it out. I fired up SVN and grabbed 0.2 (final) and 4.1 (snapshot) drivers, and recorded the closest thing I could find to identical programming, a few minutes of the Weather Channel. Using 720x480 resolution and 4500Mbps in MythTV, I noticed no real different in video or sound quality with my PVR-250. So much for that perception. :) Incidentally, while I was able to get the 2.0 driver to compile with kernel 2.6.13.1, I was not able to get the tuner to work in MythTV (I would get reception, but couldn't change channels). I had to test with a 2.6.12 kernel. Fortunately, since I didn't see a quality difference, that isn't really important. ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
On 10/10/05, Larry K [EMAIL PROTECTED] wrote: Actually, I'm using 0.3.8. Not 0.4.x. Ok. Well, I looked back at the thread and there were so many messages that I'm a bit confused. Do locate tveeprom.ko, then move any it finds to tveeprom.ko.HIDE. Repeat for tuner and tda9887. Then reboot. Since the modules you want to use have been renamed to tveeprom-ivtv.ko etc, this is safe. Also, don't use any ivtvctl commands at all either on bootup or when capturing. What frequency map have you been selecting with ptune-ui? Make sure you're using the right one. What now happens with /dev/video0 and /dev/video1? ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
