From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 16 Apr 2014 21:04:04 +0200 From: Borislav Petkov To: Bjorn Helgaas , "Rafael J. Wysocki" Cc: "Zhang, Rui" , "Lu, Aaron" , lkml , "x86@kernel.org" , Linux PCI , ACPI Devel Maling List , Yinghai Lu , "H. Peter Anvin" , Stephane Eranian , "Yan, Zheng Z" Subject: Re: Info: mapping multiple BARs. Your kernel is fine. Message-ID: <20140416190404.GA7070@pd.tnic> References: <20140224162400.GE16457@pd.tnic> <744357E9AAD1214791ACBA4B0B9092630121F201@SHSMSX101.ccr.corp.intel.com> <1558044.S1G2VU7srO@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-ID: On Thu, Mar 20, 2014 at 02:48:30PM -0600, Bjorn Helgaas wrote: > Right. Even if we had this long-term solution, we'd still have > Stephane's current problem, because the PNP0C02 _CRS is still wrong. > > We do have a drivers/pnp/quirks.c where we could conceivably adjust > the PNP resource if we found the matching PCI device and MCHBAR. That > should solve Stephane's problem even with the current > drivers/pnp/system.c. Guys, this still triggers in -rc1. Do we have a fix or something testable at least? Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. --