public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
* Owner ID wraparound problem during _BST
@ 2003-08-10  2:51 Manish Prasad
       [not found] ` <Pine.GSO.4.53.0308092239430.8919-0/pBV72GoN7BkAz3hwFLjg@public.gmane.org>
  0 siblings, 1 reply; 2+ messages in thread
From: Manish Prasad @ 2003-08-10  2:51 UTC (permalink / raw)
  To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f

Hi

I'm using 2.4.20 kernel with ACPI-patch 20021212. I found on sourceforge
that 20030523 has fixed the OwnerId wraparound problem. I'm currently
looking at the new sources and if I'm getting it right, the only change
related to this is in aclocal.h, where the values of ACPI_FIRST_METHOD_ID
and ACPI_FIRST_TABLE_ID have been changed to provide more room for
TYPE_METHOD owner_ids to grow before wrapping around (upto 0xF000 as
opposed to 0x8000 earlier). Would be great if some one could confirm if
this is indeed the only change related to fixing this problem. Also, what
exactly is the reason why this value *has* to be 16-bit and not bigger.

Thanks in advance !

Best,
--Manish


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Battery status update resolution
       [not found] ` <Pine.GSO.4.53.0308092239430.8919-0/pBV72GoN7BkAz3hwFLjg@public.gmane.org>
@ 2003-08-10  6:14   ` Manish Prasad
  0 siblings, 0 replies; 2+ messages in thread
From: Manish Prasad @ 2003-08-10  6:14 UTC (permalink / raw)
  To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f

Hi

I apologize upfront, if this is not totally relevant to this list.
Some questions about the update resolution of the battery remaining
capacity status:

What is the capacity status update resolution of a state-of-the-art
'smart' battery ? I'm currently using a Dell Inspiron 2600 with a Sanyo
LION control method battery, which updates its capacity status only for a
change of 30 - 40 mAh in the capacity (as observed through _BST control
method). What exactly is this limitation due to, is it the AML implementation
of the _BST method by the OEM or is it the battery hardware itself (say
number of bits in the A/D converter of the smart battery) ?

Any insights would be greatly appreciated.

Thanks,
--Manish





-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-08-10  6:14 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-08-10  2:51 Owner ID wraparound problem during _BST Manish Prasad
     [not found] ` <Pine.GSO.4.53.0308092239430.8919-0/pBV72GoN7BkAz3hwFLjg@public.gmane.org>
2003-08-10  6:14   ` Battery status update resolution Manish Prasad

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox