Re: [RFC] Adding screen dimensions to machine configs

[Richard Purdie <rpurdie@rpsys.net>]

On Sun, 2007-07-08 at 14:00 +0200, Stanislav Brabec wrote:
> Richard Purdie wrote:
> > The ideas in formfactor are directly lifted from zaurusd. I still wish
> > zaurusd could become a more generic kind of glue program like the fabled
> > devmand should have been but I can't be the person to do that.
> 
> On my opinion shell script handled events are very ineffective solution.
> It's easy to program it, but it is ugly and slow. For example, look what
> happens at headphones removal event: Loading shell interpreter, parsing
> script, calling alsactl, writing state to /etc, modifying this text
> config by sed, writing it back, calling alsactl again. Think about
> millions of obsolete machine instructions and also obsolete /etc write
> (one flash cycle or one obsolete start of HDD).

This is a tangent to the original point but yes, shell isn't the most
efficient way to do this. FWIW, none of the events handled in zaurusd
needs massive amounts of efficiency and it did need something easy to
program/hack as when it was written, it was meant as a prototype and
hence was subject to change.

> Desktop systems (and devmand proposal) use HAL -> D-BUS -> D-BUS enabled
> app. I guess it's the right way, which prevents calling a bunch of
> scripts for each single event, and instead of it introduces "listen what
> you need, get event, do what you should". Single purpose monitoring
> daemons can turn into D-BUS event providers, applications or action
> daemons can listen and react on whatever they need.
> 
> In upper mentioned example one daemon can listen to keyboard+jack events
> and send it to D-BUS, another daemon linked with alsa will list these
> events and modify mixer directly.

It you look through the archives I've always hinted it would evolve to
use dbus. With the current playing field, it would make sense to work
with OHM for that. Where I disagree with OHM is about the need for a
source for device specific data like dpi. keyboard location etc :-(.

Regards,

Richard