Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Stanislav Brabec <utx@penguin.cz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Adding screen dimensions to machine configs
Date: Sun, 08 Jul 2007 14:00:51 +0200	[thread overview]
Message-ID: <1183896051.5647.24.camel@utx.lan> (raw)
In-Reply-To: <1183886795.6407.15.camel@localhost.localdomain>

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).

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.


________________________________________________________________________
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus




  reply	other threads:[~2007-07-08 12:06 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08  1:11 [RFC] Adding screen dimensions to machine configs Paul Sokolovsky
2007-07-08  7:16 ` Koen Kooi
2007-07-08  8:39   ` Dr. Michael Lauer
2007-07-08  9:26   ` Richard Purdie
2007-07-08 12:00     ` Stanislav Brabec [this message]
2007-07-08 14:27       ` Richard Purdie
2007-07-09  0:53   ` Rod Whitby
2007-07-09  5:31     ` Stelios Koroneos
2007-07-09 12:43   ` Paul Sokolovsky
2007-07-09 13:17     ` Graeme Gregory
2007-07-09 13:35       ` Dr. Michael Lauer
2007-07-09 13:42         ` Graeme Gregory
2007-07-09 13:52           ` Dr. Michael Lauer
2007-07-09 14:03             ` Graeme Gregory
2007-07-09 14:19               ` Dr. Michael Lauer
2007-07-09 14:25                 ` Graeme Gregory
2007-07-09 14:40                   ` Paul Sokolovsky
2007-07-09 15:15                   ` Marcin Juszkiewicz
2007-07-09 20:30                     ` Koen Kooi
2007-07-09 22:03                       ` Richard Purdie
2007-07-09 15:44                 ` Florian Boor
2007-07-09 14:23               ` Marcin Juszkiewicz
2007-07-09 14:25               ` Paul Sokolovsky
2007-07-09 15:11                 ` Marcin Juszkiewicz
2007-07-09 13:57         ` Paul Sokolovsky
2007-07-09 13:41       ` Paul Sokolovsky
2007-07-09 15:55     ` Richard Purdie
2007-07-09 20:01       ` Dr. Michael Lauer
2007-07-09 20:19         ` Graeme Gregory
2007-07-09 20:44           ` Richard Purdie
2007-07-09 20:21         ` Koen Kooi
2007-07-09 21:36           ` Paul Sokolovsky
2007-07-09 21:21         ` Paul Sokolovsky
2007-07-10 10:33           ` Dr. Michael Lauer
2007-07-12 12:36             ` Paul Sokolovsky
2007-07-08 11:36 ` Michael Krelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1183896051.5647.24.camel@utx.lan \
    --to=utx@penguin.cz \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox