Where are you getting IRQ5 from? You can't "hard-code" interrupts on
PCI.
kernel: ACPI: PCI interrupt :13:03.0[A] -> GSI 36 (level, low) ->
IRQ 217
^___ This is your IRQ
It should be in dev->irq AFTER it's enabled.
[SNIPPED...]
Cheers,
Dick Johnson
Penguin : Linux versio
On Wed, 2005-02-23 at 15:46 -0800, Roland Dreier wrote:
> Alan> pci_read_config_byte(dev, PCI_INTERRUPT_LINE,
> &softp->interrupt_line);
> Alan> request_irq(softp->interrupt_line, sseintr, SA_INTERRUPT,
> "sse", softp);
>
> Don't do that. The kernel may need you to use a differe
Alan> I ask the card which interrupt line it was given at
Alan> boot-time:
Alan> pci_read_config_byte(dev, PCI_INTERRUPT_LINE,
&softp->interrupt_line);
Alan> Then I request an IRQ:
Alan> request_irq(softp->interrupt_line, sseintr, SA_INTERRUPT,
"sse", softp);
D
Alan Kilian wrote:
Maybe that's it.
I ask the card which interrupt line it was given at boot-time:
pci_read_config_byte(dev, PCI_INTERRUPT_LINE,
&softp->interrupt_line);
Then I request an IRQ:
request_irq(softp->interrupt_line, sseintr,
Alan Kilian wrote:
kernel: SSE: Found a DeCypher card.
kernel: ACPI: PCI interrupt :13:03.0[A] -> GSI 36 (level, low) ->
IRQ 217
The first message is in my driver after pci_find_device()
The second is from when I do pci_enable_device(dev);
Can you decode the mys
> Alan> kernel: SSE: Found a DeCypher card. kernel: ACPI: PCI
> Alan> interrupt :13:03.0[A] -> GSI 36 (level, low) -> IRQ 217
>
> If ACPI has set this device up to use interrupt 217, why are you
> registering it on IRQ 5?
>
Peter,
Maybe that's it.
I ask the car
> "Alan" == Alan Kilian <[EMAIL PROTECTED]> writes:
Alan> kernel: SSE: Found a DeCypher card. kernel: ACPI: PCI
Alan> interrupt :13:03.0[A] -> GSI 36 (level, low) -> IRQ 217
If ACPI has set this device up to use interrupt 217, why are you
registering it on IRQ 5?
--
Dr Peter Chub
> On Wed, 23 Feb 2005, Dick Johnson wrote:
>
> callpci_enable_device(dev)
> ... before you use the IRQ in dev->irq.
>
> The reported IRQ is bogus until you make that
> call. It's a reported BUG, probably won't
> ever get fixed because it's considered a
> fe
On Wed, 23 Feb 2005, Alan Kilian wrote:
callpci_enable_device(dev)
... before you use the IRQ in dev->irq.
The reported IRQ is bogus until you make that
call. It's a reported BUG, probably won't
ever get fixed because it's considered a
feature.
Folks,
This group was instrumental in helping me get my first-ever
linux/PCI-bus device driver working last year, and I'm back for
some more help if you are willing.
I have a PCI card that generates an interrupt when it completes
a DMA transfer to the
10 matches
Mail list logo
