From owner-freebsd-acpi@FreeBSD.ORG Fri Feb 17 21:04:17 2006 Return-Path: X-Original-To: freebsd-acpi@FreeBSD.org Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD89C16A422; Fri, 17 Feb 2006 21:04:17 +0000 (GMT) (envelope-from robert.moore@intel.com) Received: from orsfmr005.jf.intel.com (fmr20.intel.com [134.134.136.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1539F43D45; Fri, 17 Feb 2006 21:04:16 +0000 (GMT) (envelope-from robert.moore@intel.com) Received: from orsfmr100.jf.intel.com (orsfmr100.jf.intel.com [10.7.209.16]) by orsfmr005.jf.intel.com (8.12.10/8.12.10/d: major-outer.mc,v 1.1 2004/09/17 17:50:56 root Exp $) with ESMTP id k1HL4GxD023910; Fri, 17 Feb 2006 21:04:16 GMT Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) by orsfmr100.jf.intel.com (8.12.10/8.12.10/d: major-inner.mc,v 1.2 2004/09/17 18:05:01 root Exp $) with SMTP id k1HL48kv019360; Fri, 17 Feb 2006 21:04:16 GMT Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56]) by orsmsxvs040.jf.intel.com (SAVSMTP 3.1.7.47) with SMTP id M2006021713041628849 ; Fri, 17 Feb 2006 13:04:16 -0800 Received: from orsmsx403.amr.corp.intel.com ([192.168.65.209]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 17 Feb 2006 13:04:16 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 17 Feb 2006 13:04:14 -0800 Message-ID: <971FCB6690CD0E4898387DBF7552B90E04650068@orsmsx403.amr.corp.intel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: How can I fix these problems of the asl of my computer? Thread-Index: AcYyhoOSA1OKlOhbSgGakntKgGo8bgBfx08g From: "Moore, Robert" To: "Jung-uk Kim" , X-OriginalArrivalTime: 17 Feb 2006 21:04:16.0127 (UTC) FILETIME=[B619E8F0:01C63405] X-Scanned-By: MIMEDefang 2.52 on 10.7.209.16 Cc: huangxiangkui@gmail.com Subject: RE: How can I fix these problems of the asl of my computer? 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: Fri, 17 Feb 2006 21:04:18 -0000 17 February 2006. Summary of changes for version 20060217: 2) iASL Compiler/Disassembler: Implemented support for new reserved names: _WDG and _WED are Microsoft extensions for Windows Instrumentation Management, _TDL is a new ACPI-defined method (Throttling Depth Limit.) > -----Original Message----- > From: Jung-uk Kim [mailto:jkim@FreeBSD.org] > Sent: Wednesday, February 15, 2006 3:20 PM > To: freebsd-acpi@FreeBSD.org > Cc: Moore, Robert; huangxiangkui@gmail.com > Subject: Re: How can I fix these problems of the asl of my computer? >=20 > On Wednesday 15 February 2006 06:06 pm, Moore, Robert wrote: > > I had a sneaking suspicion that MS might be involved in this. >=20 > :-) >=20 > > I can add these to the compiler's reserved list to eliminate future > > warnings. >=20 > Great. >=20 > > BTW, I meant that most everyone goes nearly blind attempting to > > read the ACPI spec. >=20 > Yes, I think I am going to be the next victim. ;-) >=20 > Jung-uk Kim >=20 > > > -----Original Message----- > > > From: Jung-uk Kim [mailto:jkim@FreeBSD.org] > > > Sent: Wednesday, February 15, 2006 2:58 PM > > > To: freebsd-acpi@FreeBSD.org > > > Cc: Moore, Robert; huangxiangkui@gmail.com > > > Subject: Re: How can I fix these problems of the asl of my > > > computer? > > > > > > On Wednesday 15 February 2006 05:39 pm, Moore, Robert wrote: > > > > ze2205au.asl 4138: Name (_WDG, Buffer (0x50) > > > > Warning 2033 - Unknown reserved name ^ (_WDG) > > > > > > > > ze2205au.asl 4699: Method (_WED, 1, NotSerialized) > > > > Warning 2033 - Unknown reserved name ^ (_WED) > > > > > > This is a very common problem with all recent HP/Compaq laptops: > > > http://gentoo-wiki.com/Talk:HOWTO_Fix_Common_ACPI_Problems > > > > > > > 2) Ignore the warnings. Your BIOS writers did not read the ACPI > > > > spec or became blind sometime in the middle of it, highly > > > > probable. > > > > > > > > :-) > > > > > > No, they are not blind. They just work for the dark side. ;-) > > > > > > Both _WDG and _WED are Microsoft extensions: > > > http://www.microsoft.com/whdc/system/pnppwr/wmi/wmi-acpi.mspx > > > > > > Jung-uk Kim