[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47EAB54A.1060306@intel.com>
Date: Wed, 26 Mar 2008 13:42:50 -0700
From: "Kok, Auke" <auke-jan.h.kok@...el.com>
To: Jeff Garzik <jeff@...zik.org>
CC: e1000-devel@...ts.sourceforge.net, netdev@...r.kernel.org,
Jesse Brandeburg <jesse.brandeburg@...el.com>
Subject: Re: [E1000-devel] [PATCH] e1000e: test MSI interrupts
Jeff Garzik wrote:
> Auke Kok wrote:
>> From: Jesse Brandeburg <jesse.brandeburg@...el.com>
>>
>> Test the MSI interrupt physically once before assuming that it
>> actually works. Several platforms have already come across that
>> have non-functional MSI interrupts and this code will attempt
>> to detect those safely. Once the test succeeds MSI interrupts
>> will be enabled.
>>
>> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@...el.com>
>> Signed-off-by: Auke Kok <auke-jan.h.kok@...el.com>
>> ---
>>
>> drivers/net/e1000e/defines.h | 1
>> drivers/net/e1000e/e1000.h | 1
>> drivers/net/e1000e/netdev.c | 161 ++++++++++++++++++++++++++++++++++++++++--
>> 3 files changed, 155 insertions(+), 8 deletions(-)
>
> Ah, the perennial add-same-test-to-every-driver conundrum.
>
> I think we are far enough along with MSI to _not_ do this anymore in
> drivers.
>
> The platforms with MSI problems should be discovered, made public, and
> worked around.
>
> Otherwise you hide the same problem, just for someone else to discover
> with another component of the machine.
ok, that's reasonable as I have not recently seen any "new" reports against the
current trees.
We have to keep this patch in our out-of-tree version around though, since a lot
of distros still ship kernels without all the new MSI quirks. But that's not for
this forum.
Thanks,
Auke
--
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