John wrote: > Attached is a patch for people to try.
Short version: it works, kind of. tvm :-) Long version: Tried ivtv-0.3.1z against 2.6.9-1.681, built cleanly with a few minor errors, good news is it didn't seg fault on load, didn't lock the machine up (hurrah!) and I was able to reboot cleanly when the driver was loaded. Trying to dd if=/dev/video0 of=/dev/video16 bs=64k gives _loads_ of ivtv: ENC IRQ OVERFLOW: #1925 Stealing a Buffer, 1024 currently allocated Messages *however* if I actually set the channel using ptune.pl first rather than leave it unset there are *no* error messages and the picture is perfect (tried it for about 15min with zero errors [hurrah again :-)]) Loaded ivtv-fb and the screen came up with a number of slightly multicoloured lines. (actually a better description might be a white screen with a nummber of thin black lines every 5 pixels with a spattering of random coloured pixels everywhere with a hint of diagonal lines across the screen, bit hard to describe though) X started and worked (using the ivtvdrv_dev.o from the utils dir) :-) Mythtv didn't work too well playing through the osd it looks like it's dropping frames and gives loads of ivtv: OSD: DMA xfer from 0xf6e01008 of 851968 bytes failed with (-512) offset = 0x00000000, total 851968 ivtv: OSD: DMA xfer from 0xf6e01008 of 851968 bytes failed with (-512) offset = 0x00000000, total 851968 ivtv: OSD: DMA xfer from 0xf6e01008 of 851968 bytes failed with (-512) offset = 0x00000000, total 851968 ivtv: OSD: DMA xfer from 0xf6e01008 of 851968 bytes failed with (-512) offset = 0x00000000, total 851968 ivtv: OSD: DMA xfer from 0xf6e01008 of 851968 bytes failed with (-512) offset = 0x00000000, total 851968 ivtv: OSD: DMA xfer from 0xf6e01008 of 851968 bytes failed with (-512) offset = 0x00000000, total 851968 ivtv: OSD: DMA xfer from 0xf6e01008 of 851968 bytes failed with (-512) offset = 0x00000000, total 851968 ivtv: OSD: DMA xfer from 0xf6e01008 of 851968 bytes failed with (-512) offset = 0x00000000, total 851968 Messages in dmesg, setting mythtv to play out through the pvr-350's out and the picture is fine though. Still getting loads of DMA xfer failed messages while X is running (even without mythtv) Then came the problem, I rebooted to runlevel 5, X failed to start with (the bottom) half of the screen with the funny lines across and the top half ok with the cursor in the centre but locked The screen I started X on stopped at (EE) IVTVDEV(0): FBIOPAN_DISPLAY: Invalid argument I rebooted with a little bit extra in my ivtv init.d script[0] and X starts (if I don't have this it doesn't everytime), the first time I do this when it did the modprobe ivtv-fb the same half X half funny lines came up, I presume this to be the card storing what was last displayed. I'm not sure what is due to ongoing issues due to the development status and what is extra issues but it certainly works better than before! Thanks David [0] The extra bit consisting of: /usr/lib/ivtv/ptune.pl -f pal-europe-west --channel 53 dd if=/dev/video0 of=/dev/video16 bs=64k & sleep 5 kill %1 inbetween the modprobe ivtv and the modprobe ivtv-fb ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ ivtv-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
