Return-path: Received: from mail-iw0-f174.google.com ([209.85.214.174]:44143 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752364Ab1CUBOo (ORCPT ); Sun, 20 Mar 2011 21:14:44 -0400 Received: by iwn34 with SMTP id 34so5925523iwn.19 for ; Sun, 20 Mar 2011 18:14:44 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4D86A311.2070404@lockie.ca> References: <4D866714.80503@lockie.ca> <4D86A311.2070404@lockie.ca> From: Julian Calaby Date: Mon, 21 Mar 2011 12:14:24 +1100 Message-ID: Subject: Re: why would IRQ change? To: James Cc: linux-wireless Mailing List Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, Mar 21, 2011 at 12:00, James wrote: > On 03/20/11 19:42, Julian Calaby wrote: >> On Mon, Mar 21, 2011 at 07:44, James 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/