Update on DeviceKit
Holger Macht
hmacht at suse.de
Thu May 8 06:00:10 PDT 2008
On Wed 07. May - 12:11:00, David Zeuthen wrote:
> On Wed, 2008-05-07 at 13:47 +0200, Holger Macht wrote:
> > On Mi 07. Mai - 13:38:21, Danny Kukawka wrote:
> > > On Mittwoch, 7. Mai 2008, Bastien Nocera wrote:
> > > > On Wed, 2008-05-07 at 03:40 -0400, David Zeuthen wrote:
> > > > > For other subsystems, such as Firewire, audio and input my answer for
> > > > > this is to, for notifications and enumeration, rely on the core
> > > > > DeviceKit daemon and values exported by the OS kernel (e.g. sysfs on
> > > > > Linux). In effect, this is not any different from using HAL today.
> > > >
> > > > What about brightness controls
> > >
> > > IMO powermanagement
> >
> > Yes, I think of it like following:
> >
> > Having a subsystem daemon for power management incuding:
> >
> > org.freedesktop.PowerManagement.*
> > .PowerSupply
> > .CPUFreq
> > .Backlight
> > .Sleep
> > .WakeOnLAN (maybe better fitting to NetworkManager)
>
> What I have right now (IIRC) is
>
> - org.freedesktop.DeviceKit.Power
> - Sleep, Hibernate
> - org.freedesktop.DeviceKit.Power.Source
>
> It's very simple. Also other questions
>
> - I'm in the camp that thinks we should leave backlight to X. But I'll
> reply elsewhere on that.
>
> - Is CPUFreq still something we want?
>
> - WakeOnLAN - probably agree to punt that to NetworkManager
And... consider reading this thread :-)
http://mail.gnome.org/archives/networkmanager-list/2007-June/msg00277.html
Regards,
Holger
More information about the hal
mailing list