On Sunday 28 August 2005 16:37, Harry Orenstein wrote:
> I have a question that has been bothering me for quite awhile. I thought
> that at some point it might be addressed in one of the many driver
> versions, but it looks like it may be a problem that only I care about.
>
> The problem is that, for all driver versions after 0.2.0-rc3g (in both the
> 0.2 and 0.3 branches), I get interrupt errors as well as ivtv interrupts in
> /proc/interrupts even if I do not try to capture from my PVR-250. This
> does not seem to affect my ability to capture properly, and the captured
> mpeg seems fine. It just bugs me that a) I am getting constant interrupt
> errors and b) apparently the driver is throwing interrupts even if it is
> not "active".
>
> Now, you may say, why is this a problem? "Just use 0.2.0-rc3g is you don't
> want to see these interrupts and leave us alone". I would, but there was a
> patch (0.2.0-rc3k - patch from Anduin Withers, fixes i2c changes in kernel)
> that keeps the driver compatible with kernels beyond 2.6.10. I tried
> backporting this patch but was not entirely successful. Applying this
> patch to rc3g stops the interrupt problems but forces me to specify a tuner
> type because it breaks tuner type auto detection. I would try to find out
> exactly what caused this problem, but I believe it was introduced in rc3i
> and the diff from rc3h to rc3i is basically the entire driver.
>
> So, what am I asking? Do other people see this problem? Is anyone else
> bothered by it? Can someone who knows more than I do (basically, most
> anyone out there) take a look and see if there is an easy fix for this? I
> know from reading the list that there is now a roadmap to kernel inclusion
> for the driver. I think this is not a huge problem, but I believe it
> should be resolved prior to a version of the driver becoming part of a
> kernel release.
>
> Feedback is welcome. Please let me know if more info is required.
0) Upgrade to 0.3.7k, make sure you use the correct firmware (if not then
ivtv tells you in the dmesg output) and show the dmesg output between the
IVTV lines.
1) Do you share interrupts with another driver?
2) Do you see any messages in the kernel log?
3) What do you see if you enable the IRQ debug messages?
(ivtvctl -D 64)
4) Mail the output of /proc/interrupts
Well, enough homework. And for the record, no, I don't see interrupt errors.
Hans
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
