Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750871AbWCGN6j (ORCPT ); Tue, 7 Mar 2006 08:58:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751200AbWCGN6j (ORCPT ); Tue, 7 Mar 2006 08:58:39 -0500 Received: from shawidc-mo1.cg.shawcable.net ([24.71.223.10]:14659 "EHLO pd3mo3so.prod.shaw.ca") by vger.kernel.org with ESMTP id S1750871AbWCGN6j (ORCPT ); Tue, 7 Mar 2006 08:58:39 -0500 Date: Tue, 07 Mar 2006 07:58:37 -0600 From: Robert Hancock Subject: Re: de2104x: interrupts before interrupt handler is registered In-reply-to: To: "linux-os (Dick Johnson)" Cc: linux-kernel Message-id: <440D918D.2000502@shaw.ca> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <5N5Ql-30C-11@gated-at.bofh.it> <5NnDE-44v-11@gated-at.bofh.it> <440CCD9A.3070907@shaw.ca> User-Agent: Thunderbird 1.5 (Windows/20051201) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 928 Lines: 22 linux-os (Dick Johnson) wrote: > No. It would be good if that was true. Unfortunately, the IRQ > returned before the pci_enable_device() is not correct. It > gets re-written by pci_enable_device(). That wasn't what I meant, yes, that is true in the current kernel. However, any device which would start generating interrupts just because its BARs got enabled by pci_enable_device seems broken. The driver needs to request the interrupt after the device is enabled, and only after that can it enable the device to generate interrupts. -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from hancockr@nospamshaw.ca Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/