[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1180474611.17711.26.camel@dhcp-10-12-136-115.broadcom.com>
Date: Tue, 29 May 2007 14:36:51 -0700
From: "Gary Zambrano" <zambrano@...adcom.com>
To: "Jeff Garzik" <jgarzik@...ox.com>
cc: "Michael Buesch" <mb@...sch.de>,
"Maximilian Engelhardt" <maxi@...monizer.de>,
"linux-kernel" <linux-kernel@...r.kernel.org>,
"linux-wireless" <linux-wireless@...r.kernel.org>,
"Stephen Hemminger" <shemminger@...ux-foundation.org>,
"Arnaldo Carvalho de Melo" <acme@...stprotocols.net>,
netdev@...r.kernel.org, "Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: b44: regression in 2.6.22 (resend)
On Tue, 2007-05-29 at 18:39 -0400, Jeff Garzik wrote:
> We check for 0xffffffff because that is often how a fault is indicated,
> when the memory location is read during or immediately after hotplug (or
> if the PCI bus is truly faulty). So for most hardware, you see
>
> tmp = read(irq status)
> if (!tmp)
> return irq-none /* no irq events raised */
> if (tmp == 0xffffffff)
> return irq-none /* hot unplug or h/w fault */
>
> and the method that determines no interrupt handling is needed.
>
I guess you are right, but then shouldn't the driver be checking for
faults in other parts of the code too? What if a fault/hotplug occurs
immediately after an interrupt, but before a tx?
Thanks,
Gary
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists