Date: Mon, 1 Feb 2010 19:36:51 +0000 From: Rui Paulo <rpaulo@freebsd.org> To: Jung-uk Kim <jkim@FreeBSD.org> Cc: freebsd-acpi@freebsd.org Subject: Re: ACPICA 20100121 regression Message-ID: <976B4942-6DD5-438D-B8C3-1A1E7B1EDEC0@freebsd.org> In-Reply-To: <201002011433.39506.jkim@FreeBSD.org> References: <875CBAC3-245A-4199-94DC-BBB047318681@freebsd.org> <201002011421.22465.jkim@FreeBSD.org> <A22974AA-0BB0-4A62-9DE3-A66E354F704C@freebsd.org> <201002011433.39506.jkim@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. >>>>=20 >>>> The ASL is located at: >>>> http://people.freebsd.org/~rpaulo/asus-1005ha.asl.gz >>>>=20 >>>> What I'm seeing is ACPI_ID_PROBE() returning always NULL for >>>> "ASUS010" and "ATK0100" devids. >>>=20 >>> 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. >>=20 >> You're right, but I'm left wondering why it worked with a previous >> ACPICA. >=20 > 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.. -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?976B4942-6DD5-438D-B8C3-1A1E7B1EDEC0>