From owner-freebsd-acpi@FreeBSD.ORG Fri Mar 19 02:08:17 2010 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC4D4106566B for ; Fri, 19 Mar 2010 02:08:16 +0000 (UTC) (envelope-from gaijin.k@ovi.com) Received: from outfallback9-1.us5.outblaze.com (outfallback9-1.us5.outblaze.com [69.25.61.74]) by mx1.freebsd.org (Postfix) with ESMTP id B651A8FC1C for ; Fri, 19 Mar 2010 02:08:16 +0000 (UTC) Received: from outbound9-2.us5.outblaze.com (outbound9-2.us5.outblaze.com.int [192.168.12.70]) by outfallback9-1.us5.outblaze.com (Postfix) with ESMTP id 4B5674FA360 for ; Fri, 19 Mar 2010 01:57:13 +0000 (GMT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by outbound9-2.us5.outblaze.com (Postfix) with ESMTP id EFFBB98052 for ; Fri, 19 Mar 2010 01:57:11 +0000 (GMT) Received: from outfilter9-2.us5.outblaze.com (outfilter9-2.us5.outblaze.com.int [192.168.12.73]) by localhost.localdomain (8.14.3/8.14.3) with ESMTP id o2J1vBta015112 for ; Fri, 19 Mar 2010 01:57:11 GMT Received: from ws9-2.us5.outblaze.com.int (ws9-2.us5.outblaze.com [192.168.12.98]) (sender gaijin.k@ovi.com) by outfilter9-2.us5.outblaze.com (LotusLive iNotes outfilter/0.91) with SMTP; Fri, 19 Mar 2010 01:57:11 +0000 Received: (qmail 485 invoked from network); 19 Mar 2010 01:57:11 -0000 X-ob-auth: gaijin.k:ovi.com@ovi.com Received: from unknown (HELO ?10.0.3.231?) (gaijin.k@ovi.com@74.105.210.169) by ws9-2.us5.outblaze.com.nat with SMTP; 19 Mar 2010 01:57:10 -0000 From: "Alexandre \"Sunny\" Kovalenko" To: Joerg Wunsch In-Reply-To: <20100318195312.GQ52442@uriah.heep.sax.de> References: <20100315062028.GC52442@uriah.heep.sax.de> <20100317070428.GA2924@server.vk2pj.dyndns.org> <20100317074549.GC52442@uriah.heep.sax.de> <1268829363.6171.13.camel@RabbitsDen> <20100318195312.GQ52442@uriah.heep.sax.de> Content-Type: text/plain; charset="UTF-8" Date: Thu, 18 Mar 2010 21:56:44 -0400 Message-ID: <1268963804.47240.16.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Content-Disposition: inline X-Scanned-By: MIMEDefang 2.65 on 192.168.12.70 Cc: freebsd-acpi@freebsd.org Subject: Re: Funny battery values (nx6325) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Mar 2010 02:08:17 -0000 On Thu, 2010-03-18 at 20:53 +0100, Joerg Wunsch wrote: > As Alexandre Sunny Kovalenko wrote: > > > You can dump your ASL (see Handbook for instructions) and search for > > something like: > > ... > > > and try to track down where the actual values came from. Chapter 10 > > of the ACPI specification (http://www.acpi.info/spec.htm) should > > provide you with more information on the subject. > > OK, the machine's back here now. Meanwhile, I already tried all that > on all available laptops around, and while I can basically follow the > logic of most of those ASL files, I'm completely confused about the > ASL file I'm getting from the nx6325. Perhaps that confusion about it > is also what confuses acpiconf -i0... ;-) > > I'm attaching both, the acpiconf -i0 output as well as the ASL file. > Is anybody able to hint me where the _BIF and _BST methods get their > actual data from? > > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" Unfortunately, it looks like values are coming straight from Embedded Controller without any modifications: Method (C1AC, 1, Serialized) { ... If (C14C) { Store (Arg0, C160) Store (C164, Local0) // This is your design capacity Store (Local0, Index (DerefOf (Index (C1AF, Arg0)), 0x01)) // This is your last full capacity Store (Local0, Index (DerefOf (Index (C1AF, Arg0)), 0x02)) // And yes they are the same by design of your BIOS ;) ... and OperationRegion (C153, EmbeddedControl, 0x00, 0xFF) Field (C153, ByteAcc, NoLock, Preserve) { Offset (0x86), C160, 4, Offset (0x87), ... Offset (0x8D), C164, 16, Offset (0x91), ... and Name (C1AF, Package (0x02) { Package (0x0D) { 0x01, 0xFFFFFFFF, 0xFFFFFFFF, 0x01, 0xFFFFFFFF, 0x00, 0x00, 0x64, 0x64, "Primary", "100000", "LIon", "Hewlett-Packard" }, ... Given that you are not getting default values, something is actually being read and returned. Unfortunately you are going to need somebody smarter then myself to tell you whether magic number they store and offsets they use to read the values are indeed valid. You have couple of options you can try yourself, though: * play with OS names (you can find possible variants in the ASL) and see if any of them make a difference. * build ACPI module with the debug information and see what is being stored and read, and, more importantly, if there are any warnings and/or errors. Information on how to do either of these things could be found at http://www.freebsd.org/doc/handbook/acpi-debug.html Out of sheer curiosity... what does acpiconf -i1 say? -- Alexandre Kovalenko (Олександр Коваленко) -------------------------------------------------------------- Ovi Store: Fresh apps and more http://store.ovi.com/?cid=ovistore-fw-bac-na-acq-na-ovimail-g0-na-4