On Fri, Nov 21, 2008 at 9:56 PM, Andy Walls <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-11-21 at 14:21 -0500, Al McIntosh wrote: > > > > > > > In the meantime, if you're feeling adventurous, you may wish > > to try > > removing "IRQF_SHARED |" from line 730 in > > cx18-driver.c:cx18_probe(): > > > > > > /* Register IRQ */ > > retval = request_irq(cx->dev->irq, cx18_irq_handler, > > IRQF_SHARED | IRQF_DISABLED, > > cx->name, (void *)cx); > > ^^^^^^^^^^^^^ > > Try removing this ---+ > > > > recompile and reinstall the driver and see what happens. > > Hopefully the > > cx18 driver will then get it's own interrupt line and things > > will be > > better for you. > > > > > > > > I will definitely test this for you, likely won't be until next week, > > off to Montreal for the weekend. :) > > Don't bother with the test. The more I research this the more my head > hurts. My above suggestion will only cause the nvidia or cx18 driver > not to load. > > The "easy" options appear to be: > > 1. Move the cx18 to a different PCI slot so it no longer shares an IRQ > line with the nvidia hardware. > I was actually thinking the same thing. I am about to do this actually. I moved the card into an amd64 dual core system but I need the ir blaster working in that machine otherwise it's useless. I am going to have to move it back the single cpu machine and ensure the cx18 has it's own irq. Thanks for thinking about this, I really appreciate it. > > or > > 2. Configure your IRQs for your PCI slots in the BIOS setup. This may > also have to be coupled with a kernel command line option: pci=noacpi so > that hopefully the kernel preserves what the BIOS sets up. > > any other method looks like it involves a lot of time and pain. > > Regards, > Andy > > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users >
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
