From owner-acpi-jp@jp.freebsd.org  Wed Nov 29 00:18:26 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id AAA25078;
	Wed, 29 Nov 2000 00:18:26 +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 AAA25073
	for <acpi-jp@jp.freebsd.org>; Wed, 29 Nov 2000 00:18:26 +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 AAA10877
	for <acpi-jp@jp.freebsd.org>; Wed, 29 Nov 2000 00:18:34 +0900 (JST)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
Message-Id: <200011281518.AAA10877@shidahara1.planet.sci.kobe-u.ac.jp>
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Wed, 29 Nov 2000 00:08:43 JST."
             <20001129000843O.haro@tk.kubota.co.jp>
Date: Wed, 29 Nov 2000 00:18:34 +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 930
Subject: [acpi-jp 930] 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 <20001129000843O.haro@tk.kubota.co.jp>, Munehiro Matsuda $B$5$s$$$o$/(B:
>Follow up to my own message:
>
>::I've found small problem with the way _BIF info is kept in acpi_cmbat.c,
>::while fiddling with acpibatt program.
>::
>::Current code assumes that _BIF info does not change while system is up.
>::But, the lfcap (Last Full Charge Capacity) entry may change with each 
>::bettery charges done.
>
>To come to think of it, it may be a bug in my BIOS that fail to generate
>a _BIF notify event even when there's change in lfcap entry?? Hmm...
>
>::I think there are two ways of fixing it, but cannot make up my mind.
>::Which fix would you prefer?  (BTW, both fix are not tested)
>
>So, it may not be a 'fix', but a 'workaround for a bug'. *sigh*

I will fix this problem with config_intrhook . It should be done as
a device initialization process.


$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 
