On Mon, 2008-09-29 at 21:13 -0600, engage wrote: > On Monday 29 September 2008 19:05:25 engage wrote: > > On Saturday 13 September 2008 21:09:21 Andy Walls wrote: > > > On Sat, 2008-09-13 at 22:58 -0400, Andy Walls wrote: > > > > On Sat, 2008-09-13 at 19:21 -0600, engage wrote: > > > > > [drm] Initialized drm 1.1.0 20060810 > > > > > warning: `proftpd' uses 32-bit capabilities (legacy support in use) > > > > > ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes) > > > > > ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> > > > > > [drm] Initialized via 2.11.1 20070202 on minor 0 > > > > > ivtv0: Encoder revision: 0x02060039 > > > > > firmware: requesting v4l-cx25840.fw > > > > > agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0. > > > > > agpgart: X tried to set rate=x12. Setting to AGP3 x8 mode. > > > > > agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode > > > > > agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode > > > > > > > > > > > > > > > irq 16: nobody cared (try booting with the "irqpoll" option) > > > > > > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > Remember this --- > > > > > > One correction/clarification here. It looks like the actions of the > > > agpgart module are stimulating the IRQ 16 firing from the VIA on-board > > > graphics controller. Then the ivtv driver and via and drm modules tell > > > the kernel the IRQ 16 that just fired wasn't for them. > > > > > > Regards, > > > Andy > > > > Well, adding acpi=force irqpoll to lilo's append line didn't work out so > > well. It's been awhile since I've played with interrupts so wish me luck. > > Maybe I can reassign IRQ 6 to ivtv0? > > > > > Changing PCI slots did the trick.
Well that's one way to get different PCI IRQ routing, don't change the route, just change the endpoint you care about. :) Glad you found an acceptable solution. Regards, Andy _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
