From owner-acpi-jp@jp.freebsd.org  Fri Dec 15 16:00:41 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id QAA40661;
	Fri, 15 Dec 2000 16:00:41 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from tasogare.imasy.or.jp (daemon@tasogare.imasy.or.jp [202.227.24.5])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id QAA40654
	for <acpi-jp@jp.freebsd.org>; Fri, 15 Dec 2000 16:00:39 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92])
	by tasogare.imasy.or.jp (8.11.1+3.4W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id eBF70Zk30446;
	Fri, 15 Dec 2000 16:00:35 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
To: acpi-jp@jp.freebsd.org, takawata@shidahara1.planet.sci.kobe-u.ac.jp
In-Reply-To: <200012141631.BAA19409@shidahara1.planet.sci.kobe-u.ac.jp>
References: <20001215002538P.iwasaki@jp.FreeBSD.org>
	<200012141631.BAA19409@shidahara1.planet.sci.kobe-u.ac.jp>
X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20001215160035P.iwasaki@jp.FreeBSD.org>
Date: Fri, 15 Dec 2000 16:00:35 +0900
From: Mitsuru IWASAKI <iwasaki@jp.freebsd.org>
X-Dispatcher: imput version 20000228(IM140)
Lines: 19
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 970
Subject: [acpi-jp 970] Re: Some power device driver. 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: iwasaki@jp.freebsd.org

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

Yes, I thought it already.  I think it depends on whether we are going
to support notifications only from ACPI or prepare new abstracted
layers for each purposes (eg. power management, temperature, etc.)

Now that we have several ways to get battery status (temperature also),
so I prefer the latter.
