Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757422AbXLWXO5 (ORCPT ); Sun, 23 Dec 2007 18:14:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752565AbXLWXOt (ORCPT ); Sun, 23 Dec 2007 18:14:49 -0500 Received: from terminus.zytor.com ([198.137.202.10]:35213 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752576AbXLWXOs (ORCPT ); Sun, 23 Dec 2007 18:14:48 -0500 Message-ID: <476EEB6F.7080909@kernel.org> Date: Sun, 23 Dec 2007 15:12:47 -0800 From: "H. Peter Anvin" Organization: Linux Kernel Organization, Inc. User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: "Rafael J. Wysocki" CC: Linus Torvalds , Carlos Corbacho , linux-kernel@vger.kernel.org, Greg KH , Ingo Molnar , Thomas Gleixner , Len Brown , Andrew Morton Subject: Re: x86: Increase PCIBIOS_MIN_IO to 0x1500 to fix nForce 4 suspend-to-RAM References: <200712231419.40207.carlos@strangeworlds.co.uk> <200712231730.34935.rjw@sisk.pl> <200712232320.21182.rjw@sisk.pl> In-Reply-To: <200712232320.21182.rjw@sisk.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1289 Lines: 32 Rafael J. Wysocki wrote: > On Sunday, 23 of December 2007, Linus Torvalds wrote: >> On Sun, 23 Dec 2007, Rafael J. Wysocki wrote: >>> The patch is fine by me, so if anyone has objections, please speak up. >> There is absolutely *no* way I will apply this in an -rc6 release. >> >> The number of machines this will break is totally unknown. It might be >> zero. It might be hundreds. We just don't know. We might hit another >> unlucky allocation that we just happened to avoid before. > > I was rather thinking of putting it into -mm for some time and target for > 2.6.25 if possible. > > If it breaks systems, we can always revert before 2.6.25 final. > This is totally the wrong way to go about it. Instead, it should detect this particular chipset and reserve relevant ports. Even better would be if we can find out what reserves these ports and mark it as a quirk. That being said, I have seen other chipsets allocate ports in the low 0x1XXX range using non-BAR methods. They *should* reserve them in ACPI, of course. -hpa -- 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/