From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 14 19:18:38 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 E3B9A1065680 for ; Fri, 14 Nov 2008 19:18:38 +0000 (UTC) (envelope-from ivan@serezhkin.com) Received: from shustrik.urh.ru (shustrik.urh.ru [89.108.81.81]) by mx1.freebsd.org (Postfix) with ESMTP id A70C48FC16 for ; Fri, 14 Nov 2008 19:18:38 +0000 (UTC) (envelope-from ivan@serezhkin.com) Received: from vany.yandex.ru (dhcp216-36.yandex.ru [213.180.216.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ivan@serezhkin.com) by shustrik.urh.ru (Postfix) with ESMTPSA id 611031D074 for ; Fri, 14 Nov 2008 21:56:35 +0300 (MSK) Message-ID: <491DCAF2.9080507@serezhkin.com> Date: Fri, 14 Nov 2008 22:01:06 +0300 From: "Ivan B. Serezhkin" User-Agent: Thunderbird 2.0.0.17 (X11/20081024) MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Subject: generalized driver for acpi all devices. 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, 14 Nov 2008 19:18:39 -0000 Hello. I now writing device driver for fujitsu siemens notebook hotkeys FUJ02E3, and think, that before understanding how this device works a must write driver, that provide all acpi methods to sysctl and all event to log. I'v done it, but can't understand how this device is working =) I think that it must be musch easy if i already has some ways to call acpi methods and intercept events from userspace by commandline. Now i write driver, that gains, device and methods to provide in sysctl, from kenv, but in some devices this tunablie is too long. Please, explain, how can i access real acpi code from kernel and how can i found devices and methods to provide it ? Also, redirect to good documentation is what i want =) Also, i think to use /dev/acpi as a commandline interface, now there only sysctl acces, i want add some command language to it something like call _SB_.PCI0.LPCB.FEXT.SIRB(1) 0x0 alias _SB_.PCI0.LPCB.FJEX FJEX ok call FJEX.GHKS() 0x0 is this good ? or we must use some other mechanism ? But now i have not enough experience for this =) but i'll try it =) -- Ivan B. Serezhkin Spamooborona, Yandex. http://so.yandex.ru/