[mythtv] WinTV PVR-250 Install/Config
ron at haliplex.com.au
Wed Aug 20 09:55:16 EDT 2003
OK, so the interrupt count is not zero. It doesn't really tell us anything about the PVR-250 then - other devices are also sharing interrupt 11 - ethernet and usb... I assume they are working, so you will be getting interrupts from them...
There's probably nothing further to glean from the interrupt count, unless you can shuffle the interrupt usage to get the PVR-250 on its own. Even then, it would just confirm that the card is not functioning properly - which you already know...
What about the ioctl definitions? Initially, my test_ioctl was out of sync with the driver even though the source was pulled straight from CVS - just because they used different header files. Even when I sorted that out, it still wouldn't work under Myth because of Myth's own defintions for the ioctl values...
Anyone else care to comment?
From: Adam Leach [mailto:mythtv-dev at ask-adders.co.uk]
Sent: Wednesday, 20 August 2003 6:14 AM
To: Development of mythtv
Subject: RE: [mythtv] WinTV PVR-250 Install/Config
On Tue, 2003-08-19 at 00:25, Ron Kellam wrote:
> I had this sort of problem a few weeks back.
> First, check /proc/interrupts - look at the interrupt count for the
> ivtv related interrupt - from the sort of errors you're reporting (the
> "EOS interrupt not received" message), it's probably 0......
# cat /proc/interrupts
11: 17112 XT-PIC eth0, ohci1394, usb-uhci, usb-uhci,
ivtv: iTVC15/16 mpg2 encoder chip
when i do lcpci -v i get.
00:09.0 Multimedia video controller: Internext Compression Inc iTVC15
MPEG-2 Encoder (rev 01)
Subsystem: Hauppauge computer works Inc.: Unknown device 4001
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at e8000000 (32-bit, prefetchable) [size=64M]
Capabilities:  Power Management version 2
Would the Unknown device 4001 cause any problems.
More information about the mythtv-dev