Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, lrg@slimlogic.co.uk,
	Lukasz Stelmach <stlman@poczta.fm>
Subject: Re: [PATCH - amixer] listen to D-Bus for volume-up, volume-down and mute signals.
Date: Mon, 3 Aug 2009 13:17:47 +0100	[thread overview]
Message-ID: <20090803121747.GD5959@sirena.org.uk> (raw)
In-Reply-To: <s5hiqh5ccyr.wl%tiwai@suse.de>

On Mon, Aug 03, 2009 at 02:13:16PM +0200, Takashi Iwai wrote:
> Lukasz Stelmach wrote:

> > No worries ;) there is --with(out)--dbus option for configure to
> > disable all this code which is enough for initrd because most often
> > (AFAIK) initrd binaries are not the same that in the live system.

> Usually same binaries are used for initrd nowadays in many distros.
> So, configure option doesn't help.

> And, I really prefer this as a separate daemon, so it be as small as
> possible.  Seeing amixer as a daemon is somewhat strange...

I tend to agree, merging it into amixer seems kind of arbatrary.  Such a
daemon (and its dbus interface) may also be useful for handling things
like scenario management so I can see it growing over time.

  reply	other threads:[~2009-08-03 12:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 10:43 [PATCH - amixer] listen to D-Bus for volume-up, volume-down and mute signals Łukasz Stelmach
2009-08-03 10:51 ` Takashi Iwai
2009-08-03 12:04   ` Lukasz Stelmach
2009-08-03 12:13     ` Takashi Iwai
2009-08-03 12:17       ` Mark Brown [this message]
2009-08-03 16:59         ` Lukasz Stelmach
2009-08-03 17:02           ` Mark Brown
2009-08-03 17:34             ` Lukasz Stelmach
2009-08-03 19:29               ` Liam Girdwood
2009-08-03 16:29       ` Lennart Poettering
2009-08-03 17:29         ` Lukasz Stelmach
2009-08-05 12:58           ` Lennart Poettering
2009-08-05 15:58           ` Colin Guthrie
2009-08-03 17:07       ` Lukasz Stelmach

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=20090803121747.GD5959@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=stlman@poczta.fm \
    --cc=tiwai@suse.de \
    /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