Messages in this thread | | | Date | Wed, 25 Feb 2004 01:55:09 -0500 (EST) | From | Pavel Roskin <> | Subject | Re: [PATCH] yenta: irq-routing for TI bridges - take 2 |
| |
On Wed, 25 Feb 2004, Daniel Ritz wrote:
> hi > > the last patch was bad...chaning stuff it shouldn't on TI125x, 145x... > > another try...comments? > couldn't find datasheets for 1210, 1220, 1250 so i'm not quite sure about them....
http://www.mit.edu/afs/sipb/contrib/doc/specs/ic/bridge/
> compile tested (my TI works, so no difference there)
Works for me. yenta_socket is compiled into the kernel. Two cards: TI 1221 with 2 slots (no fixup needed) and TI 1410 that needs it.
Yenta: CardBus bridge found at 0000:00:08.0 [133f:1233] Yenta: Enabling burst memory read transactions Yenta: Using CSCINT to route CSC interrupts to PCI Yenta: Routing CardBus interrupts to PCI Yenta TI: mfunc 0cc07d92, devctl 60 Yenta: ISA IRQ mask 0x0000, PCI irq 5 Socket status: 30000006 Yenta: CardBus bridge found at 0000:00:08.1 [133f:1233] Yenta: Using CSCINT to route CSC interrupts to PCI Yenta: Routing CardBus interrupts to PCI Yenta TI: mfunc 0cc07d92, devctl 60 Yenta: ISA IRQ mask 0x0000, PCI irq 5 Socket status: 30000006 Yenta: CardBus bridge found at 0000:00:0a.0 [0000:0000] Yenta: Enabling burst memory read transactions Yenta: Using CSCINT to route CSC interrupts to PCI Yenta: Routing CardBus interrupts to PCI Yenta TI: mfunc 00000000, devctl 66 Yenta TI: changing mfunc to 00001000 Yenta TI: falling back to PCI interrupts Yenta TI: changing mfunc to 00001002 Yenta: ISA IRQ mask 0x0000, PCI irq 12
$ cat /proc/interrupts CPU0 0: 664717 XT-PIC timer 1: 1530 XT-PIC i8042 2: 0 XT-PIC cascade 5: 3 XT-PIC yenta, yenta, orinoco_cs 7: 0 XT-PIC acpi 8: 4 XT-PIC rtc 10: 1502 XT-PIC uhci_hcd, uhci_hcd 11: 46 XT-PIC eth0 12: 3 XT-PIC yenta, VIA686A, orinoco_cs 14: 36354 XT-PIC ide0 15: 21 XT-PIC ide1 NMI: 0 ERR: 0
-- Regards, Pavel Roskin - 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/
| |