Hi Russell,
> Can you provide the kernel messages without the hack applied please?
The kernel messages don't differ if the hack is applied or not. The hack
simply configures the PCI1410 to use a particular pin for INTA output.
Without the hack, the counter for IRQ9 in /proc/interrupt simply stays at 0.
Aug 3 14:51:02 rt1-sp kernel: Linux Kernel Card Services 3.1.22
Aug 3 14:51:02 rt1-sp kernel: options: [pci] [cardbus] [pm]
Aug 3 14:51:02 rt1-sp kernel: PCI: Enabling device 02:0a.0 (0000 -> 0002)
Aug 3 14:51:02 rt1-sp kernel: PCI: Found IRQ 9 for device 02:0a.0
Aug 3 14:51:02 rt1-sp kernel: Yenta IRQ list 0000, PCI irq9
Aug 3 14:51:02 rt1-sp kernel: Socket status: 30000010
Aug 3 14:51:03 rt1-sp kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Aug 3 14:51:03 rt1-sp kernel: cs: IO port probe 0x0800-0x08ff: clean.
Aug 3 14:51:03 rt1-sp kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x377 0x3b8-0x3df 0x4d0-0x4d7
Aug 3 14:51:03 rt1-sp kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Aug 3 14:51:03 rt1-sp kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
--jochen
-
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/
This archive was generated by hypermail 2b29 : Thu Aug 07 2003 - 22:00:22 EST