| |||||||||||||
Wakelocks and the embedded problemWakelocks and the embedded problemPosted Feb 11, 2009 16:38 UTC (Wed) by droundy (subscriber, #4559)In reply to: Wakelocks and the embedded problem by michaeljt Parent article: Wakelocks and the embedded problem
I imagine the problem with this idea is that usually interfaces are trickier than implementations, and it's very hard to know if an interface is "right" without also having a decent implementation. e.g. presumably the problem with pm_qos that made it inadequate for android's needs probably wasn't obvious when that code was reviewed (and is still not clear to me).
(Log in to post comments)
Wakelocks and the embedded problem Posted Feb 11, 2009 18:19 UTC (Wed) by michaeljt (subscriber, #39183) [Link]
They could still explain though, why the existing interfaces did not suit them and what they proposed to/were in the process of creating instead. That would at least give some valuable feedback as to how likely the changes are to get in. The embedded people do create implementations. Even that limited feedback as they went along might make everyone's life easier.
|
|||||||||||||