From owner-freebsd-mobile@FreeBSD.ORG  Thu Oct 20 10:43:57 2011
Return-Path: <owner-freebsd-mobile@FreeBSD.ORG>
Delivered-To: freebsd-mobile@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 22EEC106566C
	for <freebsd-mobile@freebsd.org>; Thu, 20 Oct 2011 10:43:57 +0000 (UTC)
	(envelope-from onyx@z-up.ru)
Received: from mx.z-up.ru (mx.z-up.ru [92.50.244.44])
	by mx1.freebsd.org (Postfix) with ESMTP id CE0CA8FC15
	for <freebsd-mobile@freebsd.org>; Thu, 20 Oct 2011 10:43:56 +0000 (UTC)
Received: from ob15_2.ktz.lan (unknown [172.16.0.4])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx.z-up.ru (Postfix) with ESMTPSA id CAFA91149C
	for <freebsd-mobile@freebsd.org>; Thu, 20 Oct 2011 14:43:46 +0400 (MSD)
From: Dmitry Kolosov <onyx@z-up.ru>
To: freebsd-mobile@freebsd.org
Date: Thu, 20 Oct 2011 14:45:25 +0400
User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; i386; ; )
References: <201110182335.15862.onyx@z-up.ru> <201110191713.02435.onyx@z-up.ru>
	<201110201434.50399.onyx@z-up.ru>
In-Reply-To: <201110201434.50399.onyx@z-up.ru>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="koi8-r"
Content-Transfer-Encoding: 7bit
Message-Id: <201110201445.25632.onyx@z-up.ru>
Subject: Re: Battery charge limiting
X-BeenThere: freebsd-mobile@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile computing with FreeBSD <freebsd-mobile.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>, 
	<mailto:freebsd-mobile-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mobile>
List-Post: <mailto:freebsd-mobile@freebsd.org>
List-Help: <mailto:freebsd-mobile-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2011 10:43:57 -0000

> so what's next? we need to sniff/trace/debug a win32 application/driver.

hm.. seems linux have something about it. and it calls SMAPI.
http://www.thinkwiki.org/wiki/SMAPI_support_for_Linux
http://www.thinkwiki.org/wiki/Tp_smapi