On Wednesday 09 February 2011 13:33:31 ext Carsten Munk, you wrote: > 2011/2/9 Rémi Denis-Courmont <[email protected]>: > > On Saturday 29 January 2011 10:42:28 ext Carsten Munk, you wrote: > >> 2011/1/29 Lego Ming <[email protected]>: > >> > Hi all, > >> > We want to study the Battery Management Mechanism on MeeGo Handset. > >> > >> The battery management mechanism on MeeGo handset is up to the > >> individual hardware adaptation. You're likely to have to implement > >> that yourself depending on your hardware. > > > > Shouldn't the values be readable with the standard power_supply device > > class in Linux sysfs at least? > > In practice, contextkit values is what should matter to apps and give > the most flexibility, I believe..
That's the discussion whether apps should/could get the value from sysfs, (lib)udev, ContextKit, QtMobility, FreeDesktop D-Bus PowerManager, and/or the proprietary BME message queue protocol. And that was not my point. MeeGo is not just a standardized developer API. It's an operating system and an implementation of that API. I am questioning not how the value should be read, but where the value should come from. Unless there is a reason why reimplementing the API back-end with every MeeGo products is unavoidable, this stuff should be commoditized. I mean, we already have the Linux kernel as our HAL with all the per-hardware drivers. -- Rémi Denis-Courmont Nokia Devices R&D, Maemo Software, Helsinki _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
