From owner-acpi-jp@jp.freebsd.org  Fri Dec 15 01:32:06 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id BAA85649;
	Fri, 15 Dec 2000 01:32:06 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id BAA85644
	for <acpi-jp@jp.freebsd.org>; Fri, 15 Dec 2000 01:32:05 +0900 (JST)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1])
	by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id BAA19409
	for <acpi-jp@jp.freebsd.org>; Fri, 15 Dec 2000 01:31:59 +0900 (JST)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
Message-Id: <200012141631.BAA19409@shidahara1.planet.sci.kobe-u.ac.jp>
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Fri, 15 Dec 2000 00:25:38 JST."
             <20001215002538P.iwasaki@jp.FreeBSD.org>
Date: Fri, 15 Dec 2000 01:31:59 +0900
From: Takanori Watanabe <takawata@shidahara1.planet.sci.kobe-u.ac.jp>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 967
Subject: [acpi-jp 967] Re: Some power device driver. 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: takawata@shidahara1.planet.sci.kobe-u.ac.jp

In message <20001215002538P.iwasaki@jp.FreeBSD.org>, Mitsuru IWASAKI $B$5$s$$$o$/(B:
>Hi,
>
>> Now that I've added ioctl registration to /dev/acpi, I hope that you'll 
>> consider just using /dev/acpi, and reserving some ioctls to interface to 
>> the battery, eg.
>
>Thanks mike, I always appreciate what you have done for this project.
>I think this is good enough solution for simple ioctl applications in
>terms of reducing number of device control files under /dev/.
>
>BTW, How about daemon programs which need event notification mechanism
>such as select/poll/kqueue?  I think we'd better to have dedicated 
>control files for this purpose.
>
>Of course your ioctl registration interface would be enough for acpibatt.


One way is adding a device node and all event is catched by poll/select 
the device,just like /dev/apmctl. 
And write a daemon to multiplex the event by unix domain socket.

What do you think?

$BEOJUB:5*(B
$B?@8MBg3XBg3X1!<+A32J3X8&5f2J(BD3$B>pJs%a%G%#%"2J3X@l96(B
<a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html">
Public Key</a>
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 



