From owner-acpi-jp@jp.FreeBSD.org Tue Sep 23 19:17:38 2003
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) id h8NAHcw32731;
	Tue, 23 Sep 2003 19:17:38 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from st68.arena.ne.jp (st68.arena.ne.jp [203.138.213.2])
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) with SMTP/inet id h8NAHcJ32726
	for <acpi-jp@jp.FreeBSD.org>; Tue, 23 Sep 2003 19:17:38 +0900 (JST)
	(envelope-from aizu@navi.org)
Received: (qmail 17557 invoked by SAV 20030922.3); 23 Sep 2003 19:17:37 +0900
Received: from unknown (HELO localhost) (219.167.191.127)
  by st68.arena.ne.jp with SMTP; 23 Sep 2003 19:17:37 +0900
From: Hiroyuki Aizu <aizu@navi.org>
To: acpi-jp@jp.FreeBSD.org
Message-Id: <20030923191736.5132af10.aizu@navi.org>
In-Reply-To: <20030923003457.P44831@root.org>
References: <20030923072516.GC645@hermes.nixsys.be>
	<20030923003457.P44831@root.org>
Organization: navi.org
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i386-portbld-freebsd5.1)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Tue, 23 Sep 2003 19:17:36 +0900
X-Sequence: acpi-jp 2693
Subject: [acpi-jp 2693] Re: Driver for Asus extras
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: aizu@navi.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+030902


On Tue, 23 Sep 2003 00:36:21 -0700
Nate Lawson <nate@root.org> wrote:

> > I'll write a little manual (asus(4)) later today, and also think about a way
> > to handle the events the machine notifies.
> >
> > In the interests of simplicity, would it be a good idea to 'translate' the
> > device-specific notifies into some known constants?  Something like:
> >
> >   #define ACPI_HOTK_BUTTON0     0x0001
> >   #define ACPI_HOTK_BUTTON1     0x0002
> >
> > That adds a bit more code to the different drivers, but it makes the daemon a
> > lot easier to maintain and implement.  Any thoughts on that?
> 
> I've thought about this and am looking over some code a developer supplied
> that does something like this and am working on a model to unify Toshiba
> and ASUS (and anything else that comes up).  I'll get back to you with an
> API.

I think it is better that these Hot key event should be translate to
some keycode and pass through virtual keyboard driver.
Application can read the code from /dev/kbd1 etc. It is simmilar to 
USB keyboard driver and already existent framework. The keyboard framework
is easy to customize keymaps. I think it is profitable for application 
programmer.
However it is little tiresome that write keyboard driver...

--
Hiroyuki Aizu
