From mboxrd@z Thu Jan 1 00:00:00 1970 From: Len Brown Subject: Re: [git pull] Input updates for 2.6.34-rc6 Date: Thu, 20 May 2010 00:53:39 -0400 (EDT) Message-ID: References: <20100513160117.GB22238@core.coreip.homeip.net> <20100513171639.GA23708@core.coreip.homeip.net> <20100513181002.GB23708@core.coreip.homeip.net> <20100514153842.GA6398@srcf.ucam.org> <20100514154905.GA6681@srcf.ucam.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from vms173011pub.verizon.net ([206.46.173.11]:58070 "EHLO vms173011pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753510Ab0ETEy2 (ORCPT ); Thu, 20 May 2010 00:54:28 -0400 In-reply-to: <20100514154905.GA6681@srcf.ucam.org> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Matthew Garrett Cc: Linus Torvalds , "Eric W. Biederman" , Dmitry Torokhov , Andrew Morton , Linux Kernel Mailing List , linux-input@vger.kernel.org, Bastien Nocera > Also, even with Windows, I do wonder if they have things like cut-off > dates for trusting ACPI. We certainly do. Upstream Linux's main ACPI cutoff, CONFIG_ACPI_BLACKLIST_YEAR has been disabled by default since Linux-2.6.9. So if a platform claims to support ACPI, upstream Linux has run in ACPI mode on it for many years. The idea was that we'd harvest and debug ACPI failures using the upstream kernels, while the distros could play it safe and set the cutoff to 1999 or even later. But a funny thing happened a few years ago. The distros stopped setting this cutoff, and nobody complained. Of course, it could simply be that few people are using machines that old anymore... In any case, I expect that versions of Windows around 1999 or 2000 had to check, but that like Linux, they don't really need to anymore. cheers, Len Brown, Intel Open Source Technology Center