* why would IRQ change?
@ 2011-03-20 20:44 James
2011-03-20 23:42 ` Julian Calaby
0 siblings, 1 reply; 5+ messages in thread
From: James @ 2011-03-20 20:44 UTC (permalink / raw)
To: linux-wireless Mailing List
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: why would IRQ change?
2011-03-20 20:44 why would IRQ change? James
@ 2011-03-20 23:42 ` Julian Calaby
2011-03-21 1:00 ` James
0 siblings, 1 reply; 5+ messages in thread
From: Julian Calaby @ 2011-03-20 23:42 UTC (permalink / raw)
To: James; +Cc: linux-wireless Mailing List
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,
--
Julian Calaby
Email: julian.calaby@gmail.com
Profile: http://www.google.com/profiles/julian.calaby/
.Plan: http://sites.google.com/site/juliancalaby/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: why would IRQ change?
2011-03-20 23:42 ` Julian Calaby
@ 2011-03-21 1:00 ` James
2011-03-21 1:14 ` Julian Calaby
0 siblings, 1 reply; 5+ messages in thread
From: James @ 2011-03-21 1:00 UTC (permalink / raw)
To: linux-wireless Mailing List
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: why would IRQ change?
2011-03-21 1:00 ` James
@ 2011-03-21 1:14 ` Julian Calaby
2011-03-21 2:00 ` James
0 siblings, 1 reply; 5+ messages in thread
From: Julian Calaby @ 2011-03-21 1:14 UTC (permalink / raw)
To: James; +Cc: linux-wireless Mailing List
On Mon, Mar 21, 2011 at 12:00, James <bjlockie@lockie.ca> wrote:
> 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.
It's a PCI card. See: http://en.wikipedia.org/wiki/Conventional_PCI#Interrupts
Thanks,
--
Julian Calaby
Email: julian.calaby@gmail.com
Profile: http://www.google.com/profiles/julian.calaby/
.Plan: http://sites.google.com/site/juliancalaby/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: why would IRQ change?
2011-03-21 1:14 ` Julian Calaby
@ 2011-03-21 2:00 ` James
0 siblings, 0 replies; 5+ messages in thread
From: James @ 2011-03-21 2:00 UTC (permalink / raw)
Cc: linux-wireless Mailing List
On 03/20/11 21:14, Julian Calaby wrote:
> On Mon, Mar 21, 2011 at 12:00, James <bjlockie@lockie.ca> wrote:
>> 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.
> It's a PCI card. See: http://en.wikipedia.org/wiki/Conventional_PCI#Interrupts
>
> Thanks,
>
Interesting, thanks.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-03-21 2:00 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-20 20:44 why would IRQ change? James
2011-03-20 23:42 ` Julian Calaby
2011-03-21 1:00 ` James
2011-03-21 1:14 ` Julian Calaby
2011-03-21 2:00 ` James
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).