Hallo,

My system:  2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 
GNU/Linux

Hauppauge computer works Inc. WinTV PVR 500

and lspci shows several VIA things.

I tried ivtv-0.10.3, after approx one minute of reading from
/dev/video1 or /dev/video2 (I have a webcam at /dev/video0) the system 
reboots, without a trail in the logfiles. I had the same problem with 0.10.2

After reading the article about pci latencies, 
http://www.mythtv.org/wiki/index.php/PCI_Latency I tried to set the 
latency of the hauppauge to zero, using setpci. This resulted in  a 
stable system. Therefore I modified ivtv-driver.c (diff is at the end of 
my story) and experienced no instability whatsoever any more. I don't 
think that this is THE solution, but I read on the www that many people 
seem to have trouble with VIA motherboards in combination with ivtv, so 
I decided to post this. (this also works for the 0.10.2 driver)

Willem

Here is the diff:

-> diff ivtv-driver.c ivtv-driver.c.orig
773,774d772
< /* wv: set latency always zero, this prevents crashes of my system */
< /*
781,786d778
< */
<        IVTV_INFO("wwvv: Setting latency timer "
<                  "to 0 (was %d)\n", pci_latency);
<        pci_write_config_byte(dev, PCI_LATENCY_TIMER, 0);
<        pci_read_config_byte(dev, PCI_LATENCY_TIMER, &pci_latency);
<


Michel Verbraak wrote:
> Hans Verkuil schreef:
>> Hi all,
>>
>> I would appreciate it if people could start testing the latest ivtv on 
>> the 0.10 branch, available here:
>>
>> http://ivtvdriver.org/viewcvs/ivtv/branches/0.10.tar.gz?view=tar
>>
>> The current driver has a problem with copying data from the MPEG card to 
>> memory that are done using PIO instead of DMA (for good reasons). 
>> Unfortunately PIO accesses are slow, so too much time is spent inside 
>> the interrupt handler. This can lead to missing clock ticks and 
>> problems with remotes (key hits that are missed).
>>
>> The patch I've committed moves these PIO copies to a separate handler 
>> outside the interrupt handler, so this should solve these problems.
>>
>> However, I did not have much time to test it thoroughly, so I'd very 
>> much appreciate it if people could start testing this and report 
>> whether or not any new problems were introduced.
>>
>> This patch is also queued for the 2.6.22 kernel, by the way.
>>
>> If this change solves the problems that I've mentioned above, then I'll 
>> make a new 0.10.3 release in two weeks time.
>>
>> Thanks,
>>
>>      Hans
>>
>> _______________________________________________
>> ivtv-devel mailing list
>> [email protected]
>> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>>   
> Hans,
> 
> Working on 32-bit OS, Vanilla kernel 2.6.21.1 (FC6 base installation), 
> with PVR-150 and PVR-350 and Freecom DVB-T USB, an Asus P4C800 
> motherboard, xdriver for PVR-350 out and MythTV (an older svn version) 
> it looks all stable.
> 
> Tested it with recording directly from DVB-T, PVR-350 and watching 
> livetv from the PVR-150 out of the PVR-350 all at the same time. 
> Pictures looking allright.
> 
> I'm still tuning my IR in combination with MythTV. Will do some more 
> testing. This was allready an older poblem in my setup. Also need to get 
> my DVB-S configured into the system and will do some testing with just 
> reading from the devices at the same time.
> 
> I will let you know.
> 
> Regards
> 
> Michel
> 
> 
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel

_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to