On Fri, 2009-02-06 at 17:24 -0500, David Zeuthen wrote:
> So unless there are really good reasons (for example if
> privileges are required) for exposing this functionality via IPC I
> think we may want to remove it and make the users (e.g. g-p-m) use the
> native kernel interfaces instead.
Two re
On Fri, 2009-02-06 at 14:58 -0500, Bill Nottingham wrote:
> David Zeuthen ([email protected]) said:
> > Also, why this on D-Bus in the first place? Why can't interested parties
> > read /proc themselves? AFAICT, it doesn't require any privileges...
>
> The above statement could be read to apply to b
David Zeuthen ([email protected]) said:
> Also, why this on D-Bus in the first place? Why can't interested parties
> read /proc themselves? AFAICT, it doesn't require any privileges...
The above statement could be read to apply to battery data too,
with probably the same answer.
Bill
__
Hi,
Hmm. I think we need to rework how the Wakeups interface work. I suggest
getting rid of all existing methods and signals and just have a single
method to get the wakeup data. Then interested parties can just do that;
it's overkill having signals, you are never going to have more than one
user
On Thu, 2009-02-05 at 20:51 -0500, David Zeuthen wrote:
> On Thu, 2009-02-05 at 20:37 -0500, David Zeuthen wrote:
> > On Mon, 2009-02-02 at 15:35 +, Richard Hughes wrote:
> > > Version 005
> > > ~~~
> > > Released: 2009-02-02
> > >
> > > New Features:
> > > - Add a wakeups interface s
On Thu, 2009-02-05 at 20:37 -0500, David Zeuthen wrote:
> On Mon, 2009-02-02 at 15:35 +, Richard Hughes wrote:
> > Version 005
> > ~~~
> > Released: 2009-02-02
> >
> > New Features:
> > - Add a wakeups interface so we can get data from the system over DBus
> > (Richard Hughes)
> > -
On Mon, 2009-02-02 at 15:35 +, Richard Hughes wrote:
> Version 005
> ~~~
> Released: 2009-02-02
>
> New Features:
> - Add a wakeups interface so we can get data from the system over DBus
> (Richard Hughes)
> - Allow showing the wakeup data in the devkit-power command line tool
> (R
