From owner-freebsd-acpi@FreeBSD.ORG  Wed Jan 30 13:40:23 2008
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
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 5E38916A421
	for <freebsd-acpi@freebsd.org>; Wed, 30 Jan 2008 13:40:23 +0000 (UTC)
	(envelope-from artur@ebasoft.com.pl)
Received: from poczta.ebasoft.com.pl (www.ebasoft.com.pl [85.237.185.105])
	by mx1.freebsd.org (Postfix) with ESMTP id B9B1B13C44B
	for <freebsd-acpi@freebsd.org>; Wed, 30 Jan 2008 13:40:22 +0000 (UTC)
	(envelope-from artur@ebasoft.com.pl)
Received: from localhost (localhost [127.0.0.1])
	by poczta.ebasoft.com.pl (Postfix) with ESMTP id BE2621AF4C9
	for <freebsd-acpi@freebsd.org>; Wed, 30 Jan 2008 13:56:22 +0100 (CET)
X-Virus-Scanned: amavisd-new 2.4.4 (20061120) at ebasoft.com.pl
Received: from poczta.ebasoft.com.pl ([127.0.0.1])
	by localhost (ns.ebasoft.com.pl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cCFXilMYjDJc for <freebsd-acpi@freebsd.org>;
	Wed, 30 Jan 2008 13:56:18 +0100 (CET)
Received: from [192.168.0.49] (unknown [192.168.0.49])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by poczta.ebasoft.com.pl (Postfix) with ESMTP id 509641AF4C8
	for <freebsd-acpi@freebsd.org>; Wed, 30 Jan 2008 13:56:17 +0100 (CET)
Message-ID: <47A073F1.2020701@ebasoft.com.pl>
Date: Wed, 30 Jan 2008 13:56:17 +0100
From: =?UTF-8?B?QXJ0dXIgQmHEhw==?= <artur@ebasoft.com.pl>
Organization: EBASoft
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
CC: freebsd-acpi@freebsd.org
References: <200801261837.26708.artur@ebasoft.com.pl>	<1201387323.7237.2.camel@localhost>
	<200801280411.29358.artur@ebasoft.com.pl>
	<479F7B2A.2070900@root.org>
In-Reply-To: <479F7B2A.2070900@root.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
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 <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2008 13:40:23 -0000

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.