public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Help enabling PCI interrupts on Dell/SMP and Sun/SMP systems.
Date: Wed, 23 Feb 2005 17:52:25 -0600	[thread overview]
Message-ID: <421D1739.9090500@shaw.ca> (raw)
In-Reply-To: <3Be7p-1pY-43@gated-at.bofh.it>

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, 
>                     SA_INTERRUPT, "sse", softp);

Yeah, that's wrong. Should be request_irq(dev->irq, ... )

PCI_INTERRUPT_LINE is assigned by the BIOS and has nothing to do with 
the routing used in APIC mode. That's why it works with noapic mode 
since then the routing is the same as the BIOS assumed.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/



  parent reply	other threads:[~2005-02-24  0:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3Bbj7-7lG-17@gated-at.bofh.it>
     [not found] ` <3BbMe-7FP-39@gated-at.bofh.it>
     [not found]   ` <3BdkS-GS-21@gated-at.bofh.it>
2005-02-23 23:25     ` Help enabling PCI interrupts on Dell/SMP and Sun/SMP systems Robert Hancock
     [not found]     ` <3BdNW-1bH-29@gated-at.bofh.it>
     [not found]       ` <3Be7p-1pY-43@gated-at.bofh.it>
2005-02-23 23:52         ` Robert Hancock [this message]
2005-02-23 20:24 Alan Kilian
2005-02-23 20:46 ` linux-os
2005-02-23 22:17   ` Alan Kilian
2005-02-23 22:58     ` Peter Chubb
2005-02-23 23:24       ` Alan Kilian
2005-02-23 23:46         ` Roland Dreier
2005-02-24  1:23           ` Alan Kilian
2005-02-24 12:37     ` linux-os

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=421D1739.9090500@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox