![]() | ||||||||||
Messages in this thread |
Alan Cox <alan@lxorguk.ukuu.org.uk> writes: > On Mon, 2002-12-09 at 17:00, Linus Torvalds wrote: > > On 9 Dec 2002, Alan Cox wrote: > > > I wonder if this is why we have all these problems with VIA chipset > > > interrupt handling. According to VIA docs they _do_ use > > > PCI_INTERRUPT_LINE on integrated devices to select the IRQ routing > > > between APIC and PCI/ISA etc, as well as 0 meaning "IRQ disabled" > > > > Whee.. That sounds like a load of crock in the first place, since the > > PCI_INTERRUPT_LINE thing should be just a scratch register as far as I > > know. However, it doesn't really matter - we definitely should never write > > to it anyway, so the VIA behaviour while strange should still be > > acceptable. > > Tested and verified. If I leave it alone non apic mode works. To use > APIC mode I have to write the new IRQ value into that register. I've > shoved that into the driver for now, since its a demented chip specific > horror. Think you can put in a reboot notifier/device shutdown method to restore it to it's old value, so kexec has a chance of working correctly with this hardware. Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-03-22 11:31 [W:0.393 / U:0.230 seconds] ©2003-2008 Jasper Spaans | ||||||||||