[Trac #315] HAL doesn't know about generic battery class devices.

[Zarro Boogs per Child]

#315: HAL doesn't know about generic battery class devices.
---------------------+------------------------------------------------------
 Reporter:  dwmw2    |        Owner:  davidz 
     Type:  defect   |       Status:  new    
 Priority:  blocker  |    Milestone:  BTest-1
Component:  distro   |   Resolution:         
 Keywords:           |  
---------------------+------------------------------------------------------
Comment (by davidz):

 Someone else (J5 for example) should probably own this

 It's easy to plug this into HAL given the kernel abstraction is there.

 I assume the EC will provide an interrupt that the battery kernel driver
 will process. This is ticket 224 - is this work done?

 It's not clear to me from reading LKML thread that /sys/class/battery code
 is going to work long term and support many kinds of batteries:

    - Is the code going to be merged into mainline or are there still split
 opinions about the interface?

    - How is HAL going to receive events from kernel? I suggested providing
 a timestamp file here http://lkml.org/lkml/2006/10/23/354

    - HAL needs to poll when no updates are being sent; I guess we want to
 do that every 60 secs or so if no interrupt have been issued. This is not
 important for OLPC (we have the EC), however it's important for other
 platforms that don't provide interrupts so I want to make sure the kernel
 abstraction works

-- 
Ticket URL: <http://dev.laptop.org/ticket/315#comment:2>
One Laptop Per Child <http://laptop.org/>