mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Robert Hancock" <hancockr@shaw.ca>
Cc: "Ivan Kokshaysky" <ink@jurassic.park.msu.ru>,
	"Greg KH" <gregkh@suse.de>, "Matthew Wilcox" <matthew@wil.cx>,
	"Shaohua Li" <shaohua.li@intel.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-pci <linux-pci@atrey.karlin.mff.cuni.cz>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Jesse Barnes" <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH]PCI:disable resource decode in PCI BAR detection
Date: Fri, 14 Sep 2007 22:55:00 -0700	[thread overview]
Message-ID: <86802c440709142255p68768f7chf7d1f073c8a8937b@mail.gmail.com> (raw)
In-Reply-To: <46EB1F16.8060209@shaw.ca>

On 9/14/07, Robert Hancock <hancockr@shaw.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

  reply	other threads:[~2007-09-15  5:55 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.ggBqx6W3i6hfs6jdfg64oXKSxW8@ifi.uio.no>
     [not found] ` <fa.o5cJ0O7pLVWRzUiVPDEZL6nKqA8@ifi.uio.no>
     [not found]   ` <fa.tyYt4GOpTOmJTUbzsxpiCAObJPQ@ifi.uio.no>
     [not found]     ` <fa.13eJumylqINOxOaoEj9cthw0d0M@ifi.uio.no>
     [not found]       ` <fa.tAIuIM02CoL+ixB11n9Fmcqyz9M@ifi.uio.no>
     [not found]         ` <fa.pxFYhTaUz2NVN7Vux7b5xVRrKTw@ifi.uio.no>
2007-09-14  3:32           ` Robert Hancock
2007-09-14 11:14             ` Ivan Kokshaysky
2007-09-14 11:33               ` Ivan Kokshaysky
2007-09-14 14:30               ` Robert Hancock
2007-09-14 15:29                 ` Ivan Kokshaysky
2007-09-14 23:53                   ` Robert Hancock
2007-09-15  5:55                     ` Yinghai Lu [this message]
2007-09-16 11:13                     ` Ivan Kokshaysky
2007-09-16 17:34                       ` Robert Hancock
2007-09-17  9:20                         ` Ivan Kokshaysky
2007-09-16 19:52                       ` Matthew Wilcox
2007-09-17  9:31                         ` Ivan Kokshaysky
2007-09-17 14:30                           ` Robert Hancock
2007-09-17  1:21                       ` Shaohua Li
2007-09-18  9:53                         ` Ivan Kokshaysky
2007-09-19 21:34                           ` Jesse Barnes
2007-09-16 20:06             ` Benjamin Herrenschmidt
2007-09-16 23:37               ` Robert Hancock
2007-09-17  0:21                 ` Benjamin Herrenschmidt
     [not found]           ` <fa.0Edi0qLTdvqVnuoDAebaTVz1jEM@ifi.uio.no>
     [not found]             ` <fa.sq+NimBnzGB2syLmvcIGOvDkixI@ifi.uio.no>
     [not found]               ` <fa.G9DPndNUxuPi5LrUTOL4uPFshnc@ifi.uio.no>
2007-09-26 23:01                 ` Robert Hancock
2007-09-27  0:40                   ` Benjamin Herrenschmidt
2007-09-27  2:14                     ` Matthew Wilcox
     [not found] <fa.+WRenB38novq157RnGPLoU4q2XI@ifi.uio.no>
     [not found] ` <fa.mM7Va6Nlsaduo/AF4MkeurSBTbs@ifi.uio.no>
     [not found]   ` <fa.Ff0IMhMYWp7NYEdjO0AftHzVOh4@ifi.uio.no>
     [not found]     ` <fa.d9zBdhHd9gKcJbtwrYguusbECo4@ifi.uio.no>
     [not found]       ` <fa.TLO57rS9iV7zhomQxJbV9gjbxx8@ifi.uio.no>
     [not found]         ` <fa.lPg6OSzX+f6jdXK1ZF0rlIhZok4@ifi.uio.no>
2007-09-15 20:24           ` Robert Hancock
2007-09-13  6:21 Shaohua Li
2007-09-13  7:31 ` Matthew Wilcox
2007-09-13  7:24   ` Shaohua Li
2007-09-13  7:55     ` Matthew Wilcox
2007-09-13  9:53       ` Greg KH
2007-09-13 11:16         ` Ivan Kokshaysky
2007-09-13 12:00           ` Greg KH
2007-09-16 20:01           ` Benjamin Herrenschmidt
2007-09-17 10:22             ` Ivan Kokshaysky
2007-09-17 20:30               ` Benjamin Herrenschmidt
2007-09-18  9:54                 ` Ivan Kokshaysky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86802c440709142255p68768f7chf7d1f073c8a8937b@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=hancockr@shaw.ca \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=matthew@wil.cx \
    --cc=shaohua.li@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome