From owner-freebsd-acpi@FreeBSD.ORG Mon Feb 1 20:45:39 2010 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 48AFD106566B; Mon, 1 Feb 2010 20:45:37 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: "Moore, Robert" Date: Mon, 1 Feb 2010 15:45:15 -0500 User-Agent: KMail/1.6.2 References: <875CBAC3-245A-4199-94DC-BBB047318681@freebsd.org> <201002011451.09084.jkim@FreeBSD.org> <4911F71203A09E4D9981D27F9D83085855AF8381@orsmsx503.amr.corp.intel.com> In-Reply-To: <4911F71203A09E4D9981D27F9D83085855AF8381@orsmsx503.amr.corp.intel.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201002011545.25010.jkim@FreeBSD.org> Cc: "Brown, Len" , "freebsd-acpi@freebsd.org" , Rui Paulo , "Lin, Ming M" Subject: Re: ACPICA 20100121 regression X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2010 20:45:39 -0000 On Monday 01 February 2010 03:24 pm, Moore, Robert wrote: > The worst part of all is that if ACPICA returns TRUE for "Linux", > the ASL code executes down paths that often have never been tested. Luckiily there are only handful of BIOSes out there match "FreeBSD" AFAIK. :-) > The goal of ACPICA is to be 100% compatible with the Windows ACPI > implementation. As such, it returns TRUE for all Windows query > strings. Yes, of course. > Note, _OSI was never intended to be a test for "which operating > system is executing". It is meant to query the "set of ACPI-related > interfaces, behaviors, or features that the operating system > supports" (from ACPI specification.) Thus, it is entirely > appropriate for ACPICA to return TRUE for windows strings. Like it or not, Microsoft is advertising it as "how to identify Windows version" method to BIOS writers, unfortunately: http://www.microsoft.com/whdc/system/pnppwr/powermgmt/WinACPI_OSI.mspx Jung-uk Kim > I guess the next question would be: why is the machine disabling > things specifically for Windows 7? > > Bob > > >-----Original Message----- > >From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- > >acpi@freebsd.org] On Behalf Of Jung-uk Kim > >Sent: Monday, February 01, 2010 11:51 AM > >To: Rui Paulo > >Cc: freebsd-acpi@freebsd.org > >Subject: Re: ACPICA 20100121 regression > > > >On Monday 01 February 2010 02:36 pm, Rui Paulo wrote: > >> On 1 Feb 2010, at 19:33, Jung-uk Kim wrote: > >> > On Monday 01 February 2010 02:25 pm, Rui Paulo wrote: > >> >> On 1 Feb 2010, at 19:21, Jung-uk Kim wrote: > >> >>> On Saturday 30 January 2010 10:49 am, Rui Paulo wrote: > >> >>>> Hi, > >> >>>> Latest ACPICA can't find my ASUS010 HID. It worked fine > >> >>>> with FreeBSD 8, which has ACPICA 20090521. > >> >>>> > >> >>>> The ASL is located at: > >> >>>> http://people.freebsd.org/~rpaulo/asus-1005ha.asl.gz > >> >>>> > >> >>>> What I'm seeing is ACPI_ID_PROBE() returning always NULL > >> >>>> for "ASUS010" and "ATK0100" devids. > >> >>> > >> >>> It seems the ASL disables ASUS010 when the OS is "Windows > >> >>> 2009" (aka Windows 7). FYI, current ACPI-CA just returns > >> >>> okay for any Microsoft OSes when _OSI method is used in ASL. > >> >>> Thus, it thinks you are running Windows 7. You can comment > >> >>> out or remove line 3626-3629 and override DSDT to re-enable > >> >>> the device, I think. > >> >> > >> >> You're right, but I'm left wondering why it worked with a > >> >> previous ACPICA. > >> > > >> > Because "Windows 2009" was added in 20090903. :-) > >> > >> I understand now. Still, I think this is ACPICA's fault, but I > >> understand that other laptops may rely on this behavior from > >> ACPICA, so the fix may cause even more problems.. > > > >I agree that it is ACPI-CA's fault but it was debated in Linux > >community for a while and they decided it is the best course of > >action for ACPI-CA, AFAIK. Basically, a lot of ACPI > > implementations out there just disable some "features" based on > > Windows versions. Even worse, many features are disabled when it > > matches "Linux". So, they decided returning the latest and > > greatest Windows version instead is the best choice. Luckily (or > > unluckily), not so many ACPI implementations match "FreeBSD". :-( > > > >Jung-uk Kim > >_______________________________________________ > >freebsd-acpi@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > >To unsubscribe, send any mail to > > "freebsd-acpi-unsubscribe@freebsd.org"