From: James <bjlockie@lockie.ca>
To: linux-wireless Mailing List <linux-wireless@vger.kernel.org>
Subject: Re: why would IRQ change?
Date: Sun, 20 Mar 2011 21:00:01 -0400 [thread overview]
Message-ID: <4D86A311.2070404@lockie.ca> (raw)
In-Reply-To: <AANLkTim_YELaSk4X4uRf_nsyAThK7SiMAq3rDD_MZVmb@mail.gmail.com>
On 03/20/11 19:42, Julian Calaby wrote:
> On Mon, Mar 21, 2011 at 07:44, James <bjlockie@lockie.ca> wrote:
>> Is there a tool to list what devices are assigned what IRQ?
>>
>> This from an old kernel:
>> ieee80211 phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81
>> mem=0xffffc900017a0000, irq=18
>>
>> This is from today:
>> ath9k 0000:02:09.0: PCI INT A -> Link[LNKB] -> GSI 17 (level, low) -> IRQ 17
>> ieee80211 phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81
>> mem=0xffffc90001ba0000, irq=17
> AFAIK, PCI interrupts numbers are just sequential numbers assigned by
> Linux - there is no significance to them, they are just a number for
> tracking which interrupt is assigned to which device - there is no
> "IRQ17" or "IRQ18" anywhere in any actual hardware.
>
> Thanks,
>
I'm thinking maybe the IRQ sharing doesn't work right with this card.
next prev parent reply other threads:[~2011-03-21 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 20:44 why would IRQ change? James
2011-03-20 23:42 ` Julian Calaby
2011-03-21 1:00 ` James [this message]
2011-03-21 1:14 ` Julian Calaby
2011-03-21 2:00 ` James
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=4D86A311.2070404@lockie.ca \
--to=bjlockie@lockie.ca \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.