[ltp] tp_smapi 0.09 (dual battery, extended status support)

[Shem Multinymous]

Hi,

On 12/13/05, Volker Gropp <mail@gropp.org> wrote:
> no idea, but current1 looks like present rate to me, and current2 like
> some average over last minute?

That would be useful for analyzing component power draw.

Can anyone confirm?


> > * Are design_capacity and last_full_capacity reversed?
> yes, design_capacity is last_full_capacity and vice versa

Will be fixed.


> > * Where are the activity (charging etc.) bits?
> hmm, i only noticed yet discharging is 40 d0 in first lines of
> dump, c0 c0 is "charged".

The MSB of the first byte probably means "AC connected" (which reminds
me, I forgot to mention the new
/sys/devices/platform/smapi/ac_connected). So it's probably something
in the 2nd.

I see this in the 2nd byte:

Idle:             0xc0
Discharging: 0xd0
Charging:     0xe0

Does anyone see other values?


> One thing i noticed, stop threshold isnt supported on x40 as i already
> supported, but trying to set it, results in:
>
> echo 90 > /sys/devices/platform/smapi/BAT0/stop_charge_thresh
>
> tp_smapi: battery 0: changed start threshold to 88
> tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=3D21=
1a)
> tp_smapi: cannot get stop thresh of battery 0: Function is not supported =
by SMAPI BIOS
>
> So even when stop failes, the values minus 2 will be set as start
> threshold.

Oops. Will be fixed.

  Shem