Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760650AbXIOFzQ (ORCPT ); Sat, 15 Sep 2007 01:55:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751912AbXIOFzE (ORCPT ); Sat, 15 Sep 2007 01:55:04 -0400 Received: from wa-out-1112.google.com ([209.85.146.181]:4921 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752505AbXIOFzC (ORCPT ); Sat, 15 Sep 2007 01:55:02 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Gov1bn2fghrnmqfKJmKa2AaWOrAw1fJrLdG1aaZBcHcQg6VvG1jAU2kS7VzI1TgBTkC5V0/fBXQQKQP3q/8RYxCGzYoHUGaS4P0fIygbN1CBXAhvTAmsPQuWbr2LU+eDPfVRCe6pbidT5spbel3bTI32cpu6hor1Jkzxsx0xA64= Message-ID: <86802c440709142255p68768f7chf7d1f073c8a8937b@mail.gmail.com> Date: Fri, 14 Sep 2007 22:55:00 -0700 From: "Yinghai Lu" To: "Robert Hancock" Subject: Re: [PATCH]PCI:disable resource decode in PCI BAR detection Cc: "Ivan Kokshaysky" , "Greg KH" , "Matthew Wilcox" , "Shaohua Li" , lkml , linux-pci , "Andrew Morton" , "Jesse Barnes" In-Reply-To: <46EB1F16.8060209@shaw.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46EA00DA.6010704@shaw.ca> <20070914151401.A5586@jurassic.park.msu.ru> <46EA9B23.7030709@shaw.ca> <20070914192913.A6668@jurassic.park.msu.ru> <46EB1F16.8060209@shaw.ca> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 822 Lines: 18 On 9/14/07, Robert Hancock 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/