http://bugzilla.kernel.org/show_bug.cgi?id=7304
--- Comment #52 from Thomas Nemeth <[email protected]> 2010-03-13 08:29:02 --- > --- Comment #51 from Dominik Brodowski <[email protected]> 2010-03-06 14:07:42 > --- > Hm, it looks to me that the PCI IRQ pins are routed to IRQ #11. So what about > trying out (at first) some workaround: Could you replace the line in > drivers/pcmcia/yenta_socket.c - function yenta_probe() which states: > socket->cb_irq = dev->irq; > with: > socket->cb_irq = 11; > ? It seems that forcing the irq number does not change anything :( I tested that oneliner on the 2.6.25.6 (since it's the one I already had under my hand at that time) and there are still the same messages. > Also, some quite new patches (see: > http://www.mail-archive.com/[email protected]/msg02903.html > http://www.mail-archive.com/[email protected]/msg02904.html > http://www.mail-archive.com/[email protected]/msg02906.html > ) which currently are only for some TI bridge might be generalized to work > also > in other cases where the PCI IRQ is 0. I'll dig into that later. Should I use a more recent kernel or can I continue going on with 2.6.25.6 ? Using a recent kernel may take me some time since there's no network on that machine (the network only comes through pcmcia :( ). Anyway, thank you very much ! I was desperating that someone might have a look at my problem... Thomas. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
