Re: 3c59x: Using bad IRQ 0

2000-11-24 Thread Jeff Garzik
Linus Torvalds wrote: > > On Tue, 21 Nov 2000, Jeff Garzik wrote: > > > > A caveat to this whole scheme is that usb-uhci -already- calls > > pci_enable_device before checking dev->irq, and yet cannot get around > > the "assign IRQ to USB: no" setting in BIOS. I hope that is an > > exception rath

Re: 3c59x: Using bad IRQ 0

2000-11-24 Thread Erik Mouw
On Tue, Nov 21, 2000 at 05:26:06PM -0800, Linus Torvalds wrote: > On Tue, 21 Nov 2000, Jeff Garzik wrote: > > > > A caveat to this whole scheme is that usb-uhci -already- calls > > pci_enable_device before checking dev->irq, and yet cannot get around > > the "assign IRQ to USB: no" setting in BIO

Re: 3c59x: Using bad IRQ 0

2000-11-23 Thread Jeff Garzik
Linus Torvalds wrote: > > On Thu, 23 Nov 2000, Tobias Ringstrom wrote: > > > > > > - enable DEBUG in arch/i386/kernel/pci-i386.h. This should make the code > > >print out what the pirq table entries are etc. > > > > Done. When adding the call to eisa_set_level_irq, the line > > > > IRQ for 0

Re: 3c59x: Using bad IRQ 0

2000-11-23 Thread Linus Torvalds
On Thu, 23 Nov 2000, Tobias Ringstrom wrote: > > > > - enable DEBUG in arch/i386/kernel/pci-i386.h. This should make the code > >print out what the pirq table entries are etc. > > Done. When adding the call to eisa_set_level_irq, the line > > IRQ for 00:0a.0(0) via 00:0a.0 -> PIRQ 03, ma

Re: 3c59x: Using bad IRQ 0

2000-11-23 Thread Tobias Ringstrom
On Thu, 23 Nov 2000, Linus Torvalds wrote: > > > Tobias, can you confirm that calling pci_enable_device before reading > > > dev->irq fixes the 3c59x.c problem for you? > > > > Nope. The interrupts do not seem to get through. Packets are transmitted, > > but that's it. I've copied the interesting

Re: 3c59x: Using bad IRQ 0

2000-11-23 Thread Linus Torvalds
On Tue, 21 Nov 2000, Tobias Ringstrom wrote: > > > > Tobias, can you confirm that calling pci_enable_device before reading > > dev->irq fixes the 3c59x.c problem for you? > > Nope. The interrupts do not seem to get through. Packets are transmitted, > but that's it. I've copied the interesting

Re: 3c59x: Using bad IRQ 0

2000-11-21 Thread Linus Torvalds
On Tue, 21 Nov 2000, Jeff Garzik wrote: > > A caveat to this whole scheme is that usb-uhci -already- calls > pci_enable_device before checking dev->irq, and yet cannot get around > the "assign IRQ to USB: no" setting in BIOS. I hope that is an > exception rather than the rule. Do we have a re

Re: 3c59x: Using bad IRQ 0

2000-11-21 Thread Tobias Ringstrom
On Tue, 21 Nov 2000, Jeff Garzik wrote: > Tobias Ringstrom wrote: > > When saying yes to "Plug-and-play OS" in the BIOS, my 3Com 905C adapter > > stops working, since the driver tries to use IRQ 0, since the BIOS does > > not assign an IRQ to it. The driver seems to read the IRQ from the card > >

Re: 3c59x: Using bad IRQ 0

2000-11-21 Thread Jeff Garzik
Tobias Ringstrom wrote: > When saying yes to "Plug-and-play OS" in the BIOS, my 3Com 905C adapter > stops working, since the driver tries to use IRQ 0, since the BIOS does > not assign an IRQ to it. The driver seems to read the IRQ from the card > before it calls pci_enable_device (and pci_set_mas