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
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
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 BIOS. I
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 rather than the
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
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,
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
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
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 parts
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 parts from
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 00:0a.0(0) via
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
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
> >
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
Linux-2.4.0-test11:
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_master).
Linux-2.4.0-test11:
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_master).
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
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
before
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 recent
19 matches
Mail list logo
