Date: Tue, 29 Jan 2008 11:14:50 -0800 From: Nate Lawson <nate@root.org> To: =?UTF-8?B?QXJ0dXIgQmHEhw==?= <artur@ebasoft.com.pl> Cc: freebsd-acpi@freebsd.org Subject: Re: Need info about ACPI - implementing, done .... Message-ID: <479F7B2A.2070900@root.org> In-Reply-To: <200801280411.29358.artur@ebasoft.com.pl> References: <200801261837.26708.artur@ebasoft.com.pl> <1201387323.7237.2.camel@localhost> <200801280411.29358.artur@ebasoft.com.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Artur Bać wrote: > Saturday 26 of January 2008 23:42:03 Mikael Ikivesi napisał(a): >> I really hope you can make it. > > Idid it! after 3 days of diging acpi specifications , till i found > > http://www.microsoft.com/whdc/system/pnppwr/wmi/wmi-acpi.mspx Congrats, glad to see people digging into acpi themselves. > I'm so happy becouse this is my first at all kernel module/driver > in my life i have ever written. > > very hot uncleaned code atached bellow. > > Short abstract, tomorrow I will write more, > 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. -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?479F7B2A.2070900>