From owner-acpi-jp@jp.FreeBSD.org Tue Sep 23 19:34:21 2003
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) id h8NAYLf37937;
	Tue, 23 Sep 2003 19:34:21 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from hermes.nixsys.be (postfix@hermes.nixsys.be [2001:ab8:2007:0:20c:6eff:fe4b:23f])
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) with ESMTP/inet6 id h8NAYKJ37830
	for <acpi-jp@jp.FreeBSD.org>; Tue, 23 Sep 2003 19:34:20 +0900 (JST)
	(envelope-from philip@nixsys.be)
Received: by hermes.nixsys.be (Postfix, from userid 1001)
	id D862F6D; Tue, 23 Sep 2003 12:34:14 +0200 (CEST)
From: Philip Paeps <philip+freebsd@paeps.cx>
To: acpi-jp@jp.FreeBSD.org
Message-ID: <20030923103414.GI645@hermes.nixsys.be>
Mail-Followup-To: acpi-jp@jp.FreeBSD.org
References: <20030923072516.GC645@hermes.nixsys.be> <20030923003457.P44831@root.org> <20030923191736.5132af10.aizu@navi.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030923191736.5132af10.aizu@navi.org>
X-Date-in-Rome: ante diem IX Kalendas Octobres MMDCCLVI ab Urbe Condida
X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879
X-Message-Flag: Get a proper mailclient!  Mutt: <http://www.mutt.org/>
User-Agent: Mutt/1.5.4i
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Tue, 23 Sep 2003 12:34:14 +0200
X-Sequence: acpi-jp 2696
Subject: [acpi-jp 2696] Re: Driver for Asus extras
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: philip+freebsd@paeps.cx
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+030902

On 2003-09-23 19:17:36 (+0900), Hiroyuki Aizu <aizu@navi.org> wrote:
> 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. 

I think we could do something similar within the driver itself by creating a
character device which can be read from or written to.  I don't see any
advantages to that over the sysctl-interface though?

> 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...

Going through the keyboard-driver might interfere with other keyboards though?
If someone uses an external keyboard with a million extra buttons, it's likely
that one or more of those buttons might overlap with one of the hotkeys on the
laptop.  I can't think of a reason to use the laptop hotkeys when an external
keyboard is around, but there are some strange people out there :-)

 - Philip

-- 
Philip Paeps                                          Please don't CC me, I am
                                                       subscribed to the list.

  BOFH Excuse #49:
    Bogon emissions
