[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440902210031j698403cev2147e72a61e17194@mail.gmail.com>
Date: Sat, 21 Feb 2009 00:31:43 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Robert Hancock <hancockrwd@...il.com>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Andrew Morton <akpm@...ux-foundation.org>, david@...g.hm,
Matthew Wilcox <matthew@....cx>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-scsi@...r.kernel.org, DL-MPTFusionLinux@....com,
linux-pci@...r.kernel.org
Subject: Re: [PATCH] pci: enable MSI on 8132
On Fri, Feb 20, 2009 at 11:50 PM, Eric W. Biederman
<ebiederm@...ssion.com> wrote:
> Robert Hancock <hancockrwd@...il.com> writes:
>>
>> Is there a reason why we can't just enable the HT MSI mapping for any bridge
>> device that has that PCI capability and is underneath an HT bridge?
>
> The code should be under CONFIG_X86 because the rules for enabling HT MSI mappings
> are different for other architectures. But otherwise I can't think of a reason.
move to arch/x86/pci/fixup.c?
it seems some other arch do support HT ... powerpc, mips?
>
>> Essentially
>> the code for nv_msi_ht_cap_quirk could potentially be applied to all bridges as
>> it is currently for NVIDIA and ALi bridges..
>
> Sounds like it would save a fair amount of grief.
it seems there is some difference.
8132 is some kind of HT tunnel, and the bridge is acctually pci-x bridge.
mcp55 and ck804: is HT end device with several pcie bridges.
also 8131 has problem with HT MSI?
YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists