To: Jeff Garzik <jeff@garzik.org>
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
       Benjamin Herrenschmidt <benh@kernel.crashing.org>,
       David Miller <davem@davemloft.net>, torvalds@osdl.org,
       linux-kernel@vger.kernel.org, tiwai@suse.de
Subject: Re: [PATCH] ALSA: hda-intel - Disable MSI support by default
References: <455A938A.4060002@garzik.org>
	<20061114.201549.69019823.davem@davemloft.net>
	<455A9664.50404@garzik.org>
	<20061114.202814.70218466.davem@davemloft.net>
	<1163643937.5940.342.camel@localhost.localdomain>
	<455BDA1D.5090409@garzik.org>
	<1163650341.5940.361.camel@localhost.localdomain>
	<455C0176.5090107@garzik.org> <m3u00z4fnv.fsf@defiant.localdomain>
	<455C8350.3050309@garzik.org>
From: Roland Dreier <rdreier@cisco.com>
Date: Thu, 16 Nov 2006 09:24:59 -0800
In-Reply-To: <455C8350.3050309@garzik.org> (Jeff Garzik's message of "Thu, 16 Nov 2006 10:27:12 -0500")
Message-ID: <adau00ztic4.fsf@cisco.com>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 719
Lines: 16

 > Most interrupt-driven devices have an interrupt mask register of some
 > sort.  The nice thing about PCI_COMMAND_INTX_DISABLE is that it is
 > standardized.

You all got on me about quoting the spec about not generating INTx
interrupts after MSI is enabled.  What makes you think that setting
some bit in the command register, which wasn't even standardized until
PCI 2.3 and which most hardware designers probably forgot about, is
going to work on broken devices?

 - R.
-
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/