Hal 0.5.0

[Richard Hughes]

On Thu, 2005-03-24 at 10:54 -0500, David Zeuthen wrote:
> However, there's a certain limit to what we can get out of the hardware.
> Similarly, e.g. APM exports both my batteries in my old Dell Inspiron
> 7500 as a single one. It's just something we need to deal with.

No problem.

> > battery.charge_level.rate = 0 (hardcoded to zero as unknown)
> > (Mandatory in HAL spec)
> 
> I thought I made that optional, oh, I did, here is the patch I committed
> for that:
> 
> >              <row>
> >                <entry><literal>battery.charge_level.rate</literal>
> > (int)</entry>
> >                <entry></entry>
> > -              <entry>Yes</entry>
> > +              <entry>No</entry>
> 
> It's optional because we don't necessarily know, and if we don't know we
> shouldn't set it to zero, because obviously battery charge is
> decreasing/increasing and we shouldn't lie to the user :-)

Point taken, if we don't know, we shouldn't lie....

> > battery.charge_level.unit = "CSR"
> 
> No, you got it wrong; CSR is just the name of the protocol used to
> extract this kind of information. 

Sure, okay, but I figured if CSR is always 0 to 7 it would be nice to
know. No problem tho.

> All this just means that programs like g-p-m need to be a bit careful in
> what properties to expect. Yes, that's a pain, but that's
> programming :-)

I know. I'm thinking of buying a wireless mouse to try this with. What
ones work with CSR? What have you got? Sergey too.

Richard.


_______________________________________________
hal mailing list
hal at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/hal