From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753215AbZBJPbq (ORCPT ); Tue, 10 Feb 2009 10:31:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753268AbZBJPbg (ORCPT ); Tue, 10 Feb 2009 10:31:36 -0500 Received: from mx2.redhat.com ([66.187.237.31]:44930 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753103AbZBJPbg (ORCPT ); Tue, 10 Feb 2009 10:31:36 -0500 Message-ID: <49919E08.5050002@redhat.com> Date: Tue, 10 Feb 2009 16:32:24 +0100 From: Hans de Goede User-Agent: Thunderbird 2.0.0.18 (X11/20081119) MIME-Version: 1.0 To: Matthew Garrett CC: Jean Delvare , Len Brown , Luca Tettamanti , Thomas Renninger , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] ACPI: add "auto" to acpi_enforce_resources References: <20090125210520.GA12963@dreamland.darkstar.lan> <200901291130.35434.trenn@suse.de> <68676e00901290716g1aabd6c0p1e5202fbdbc659a4@mail.gmail.com> <20090204060513.GA28321@srcf.ucam.org> <498953DF.5050306@redhat.com> <20090204131708.GA2739@srcf.ucam.org> <20090204142606.1823661b@hyperion.delvare> <20090204142015.GB3923@srcf.ucam.org> <20090210145716.105ab58b@hyperion.delvare> <20090210140829.GA25397@srcf.ucam.org> In-Reply-To: <20090210140829.GA25397@srcf.ucam.org> 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 Matthew Garrett wrote: > On Tue, Feb 10, 2009 at 02:57:16PM +0100, Jean Delvare wrote: > year (I think the info is available, right?) We could >> default to strict for systems with year >= 2009. This may still prevent >> users from getting the best out of their system, but at least won't >> cause a regression for users of older systems where the native driver >> has been used so far. I know it's not an ideal solution, but ACPI >> implementations aren't ideal either. > > The problem with this approach is that we still end up with a large > number of malfunctioning machines. Really, I don't think there's any way > to handle this other than defaulting to strict, letting the default be > changed at run and boot time and printing a message when a driver is > refused permission to bind. Distributions that want to obtain the > previous behaviour can change the default back. > For the record we have changed the default to strict in Fedora's development branch, for 2 weeks or so now, including in the recently released Fedora 11 release and we've had 0 complaints so far. Regards, Hans