[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440709142255p68768f7chf7d1f073c8a8937b@mail.gmail.com>
Date: Fri, 14 Sep 2007 22:55:00 -0700
From: "Yinghai Lu" <yhlu.kernel@...il.com>
To: "Robert Hancock" <hancockr@...w.ca>
Cc: "Ivan Kokshaysky" <ink@...assic.park.msu.ru>,
"Greg KH" <gregkh@...e.de>, "Matthew Wilcox" <matthew@....cx>,
"Shaohua Li" <shaohua.li@...el.com>,
lkml <linux-kernel@...r.kernel.org>,
linux-pci <linux-pci@...ey.karlin.mff.cuni.cz>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Jesse Barnes" <jbarnes@...tuousgeek.org>
Subject: Re: [PATCH]PCI:disable resource decode in PCI BAR detection
On 9/14/07, Robert Hancock <hancockr@...w.ca> wrote:
> It's not impossible at all. In fact I'm quite sure (Jesse can confirm)
> that in the case of the board he was using, it was an add-in graphics
> card where he saw this problem.
>
> The fact is that in the case of MMCONFIG overlap with PCI BARs, which
> one takes priority is completely undefined. In the case of this Intel
> chipset, clearly the PCI Express device connected to the northbridge had
> higher decode priority than the MMCONFIG aperture.
can you relocate the MMCONFIG above RAM range? for example 512G...
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