From owner-freebsd-acpi@FreeBSD.ORG Thu Jan 31 00:45:37 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8E3816A41A for ; Thu, 31 Jan 2008 00:45:37 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id B308113C459 for ; Thu, 31 Jan 2008 00:45:37 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 68465 invoked from network); 31 Jan 2008 00:45:39 -0000 Received: from 209-128-117-003.bayarea.net (HELO ?10.0.8.5?) (nate-mail@209.128.117.3) by root.org with ESMTPA; 31 Jan 2008 00:45:39 -0000 Message-ID: <47A11ACD.8000409@root.org> Date: Wed, 30 Jan 2008 16:48:13 -0800 From: Nate Lawson User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: =?UTF-8?B?QXJ0dXIgQmHEhw==?= References: <200801261837.26708.artur@ebasoft.com.pl> <1201387323.7237.2.camel@localhost> <200801280411.29358.artur@ebasoft.com.pl> <479F7B2A.2070900@root.org> <47A073F1.2020701@ebasoft.com.pl> In-Reply-To: <47A073F1.2020701@ebasoft.com.pl> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-acpi@freebsd.org Subject: Re: Need info about ACPI - implementing, done .... 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: Thu, 31 Jan 2008 00:45:38 -0000 Artur Bać wrote: > Nate Lawson pisze: >> Artur Bać wrote: >>> There is no ACPI , there is Microsoft invention combo of ACPI+WMI+MOF >>> so we call acpi method which calls wmi method with code located in >>> bios or embbeded as MOF data into acpi ... >> >> Yeah, it would be better to implement a generic WMI driver and then >> call it from your wireless switch driver. Not all laptops will >> support this method of calling into WMI via ACPI since it's not a >> standard. >> > > After reading ... > http://antitrust.slated.org/www.iowaconsumercase.org/011607/3000/PX03020.pdf > > I'm frustrated with the knowlege that Hi was able/he tryed to make my > privte hardware, laptop making useles in areas where it suits me best. > > This article shows why there is a mix of WMI+ACPI in my laptop, and why > we are unable to use only ACPI to take the best from it. > > He is realy a big sucker. > This is a bit off-topic. However, I think the combination of an over-complicated spec and the secrecy/anonymity of OEMs is the real enabler of acpi problems. You do know that some small shop in Taiwan actually defined and built your BIOS, not Phoenix or AMI, right? -- Nate