Sascha Silbe si...@activitycentral.com writes:
[...]
1. UPower API
UPower has a D-Bus API to set latency requirements [1,2]. The
UPower back-end code uses the kernel PM QoS interface [3] to set the
requested CPU (DMA) latency (in µs, up to ~35 minutes) and network
throughput (in
[CC'ing devel@l.l.o because it touches operation of low-level software
components on OLPC OS]
Paul Fox p...@laptop.org writes:
the problem is that there's no good operating system mechanism that
powerd can use to know that audio is truly in use.
it's possible to know that the audio device
Gonzalo Odiard godi...@sugarlabs.org writes:
[...]
That is a complete nonsense to me. [...]
I'm not going to reply to your mail in detail because it wasn't
constructive in any way; I even felt it to be slightly ad-hominem.
See my other mails (including a patch, and maybe another one later
On 05/09/2012 05:56 PM, Paul Fox wrote:
gonzalo wrote:
On Wed, May 9, 2012 at 12:42 PM, Paul Foxp...@laptop.org wrote:
i would much prefer that we could prevent suspend during any
audio playback, rather than have to have anyone that wants
to make noise do it
Ok, so I am still not clear on the whys. Why does the machine suspend
when there is audio being played back? That sounds wrong to me. It would
be the same as suspending why I am moving the mouse. Can someone provide
some background information on this?
Regards,
Simon
On 05/17/2012 08:08
Powerd (/usr/sbin/powerd) itself is not that hard to read; it is just a
shell script.
On XOs, powerd is willing to aggressively suspend the system (and enable
the DCON) if certain criteria are met which seem to indicate that the XO is
not in use. These criteria include:
- CPU usage below a
Hi Paul,
thanks again for getting back on this!
On 05/18/2012 03:10 PM, Paul Fox wrote:
simon wrote:
On 05/09/2012 05:56 PM, Paul Fox wrote:
gonzalo wrote:
On Wed, May 9, 2012 at 12:42 PM, Paul Foxp...@laptop.org
wrote:
i would much prefer that we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 16 May 2012 01:21 AM, Sascha Silbe wrote:
Gonzalo Odiard godi...@sugarlabs.org writes:
Using powerd-inhibit-suspend directory is how ALL the activities
are working today,
Quantity isn't the same as quality. That everybody is
On Tue, May 15, 2012 at 4:51 PM, Sascha Silbe si...@activitycentral.comwrote:
Gonzalo Odiard godi...@sugarlabs.org writes:
Using powerd-inhibit-suspend directory is how ALL the activities are
working today,
Quantity isn't the same as quality. That everybody is doing it doesn't
make it
Using powerd-inhibit-suspend directory is how ALL the activities are
working today,
and how powerd is used.
We can work in a new feature to sugar 0.98, to have a more generic power
management communication, in fact, would be great no need to copy/paste
similar code in a lot of activities, but I
Gonzalo Odiard godi...@sugarlabs.org writes:
Using powerd-inhibit-suspend directory is how ALL the activities are
working today,
Quantity isn't the same as quality. That everybody is doing it doesn't
make it suddenly a good idea. Quite the contrary, as platform developers
we have the
godi...@sugarlabs.org writes:
To avoid stoping playing the text when the xo go to sleep.
This patch creates a file in /var/run/powerd-inhibit-suspend/
and remove it when finish.
/var/run/powerd-* is an implementation detail of a particular downstream
implementation of power management (namely
On Thu, May 10, 2012 at 12:58 AM, James Cameron qu...@laptop.org wrote:
Regarding your general approach, this is okay for the moment, since
nothing else in the Sugar shell process will use it, but watch out in
future.
/var/run/powerd-inhibit-suspend/%s is unique by process id only.
See
From: Gonzalo Odiard godi...@gmail.com
To avoid stoping playing the text when the xo go to sleep.
This patch creates a file in /var/run/powerd-inhibit-suspend/
and remove it when finish. Is the same technique used in activities
(the code is copied from Distance activity) but we need decide
if is
Reviewed-by: James Cameron qu...@laptop.org
--
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
From: Gonzalo Odiard godi...@gmail.com
To avoid stoping playing the text when the xo go to sleep.
This patch creates a file in /var/run/powerd-inhibit-suspend/
and remove it when finish. Is the same technique used in activities
(the code is copied from Distance activity) but we need decide
if is
i would much prefer that we could prevent suspend during any
audio playback, rather than have to have anyone that wants
to make noise do it individually.
that being said, you can eliminate any of the code below that deals
with the ohm keystore. if we move away from powerd, it likely won't
be
On Wed, May 9, 2012 at 12:42 PM, Paul Fox p...@laptop.org wrote:
i would much prefer that we could prevent suspend during any
audio playback, rather than have to have anyone that wants
to make noise do it individually.
But this should be done at a lower level, right?
that being said, you
gonzalo wrote:
On Wed, May 9, 2012 at 12:42 PM, Paul Fox p...@laptop.org wrote:
i would much prefer that we could prevent suspend during any
audio playback, rather than have to have anyone that wants
to make noise do it individually.
But this should be done at a lower level,
From: Gonzalo Odiard godi...@gmail.com
To avoid stoping playing the text when the xo go to sleep.
This patch creates a file in /var/run/powerd-inhibit-suspend/
and remove it when finish. Is the same technique used in activities
(the code is copied from Distance activity) but we need decide
if is
Regarding your general approach, this is okay for the moment, since
nothing else in the Sugar shell process will use it, but watch out in
future.
/var/run/powerd-inhibit-suspend/%s is unique by process id only.
See stopwatch.git/powerd.py for a reference counted implementation
that would avoid
21 matches
Mail list logo
