Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: ibm-acpi-devel@lists.sourceforge.net,
	alsa-devel@lists.sourceforge.net, Theodore Tso <tytso@mit.edu>
Subject: Re: [ibm-acpi-devel] Adding a alsa mixer interface	to	ibm-acpi
Date: Fri, 09 Mar 2007 17:29:57 +0100	[thread overview]
Message-ID: <s5htzwugz22.wl%tiwai@suse.de> (raw)
In-Reply-To: <20070308003806.GC12070@khazad-dum.debian.net>

At Wed, 7 Mar 2007 21:38:06 -0300,
Henrique de Moraes Holschuh wrote:
> 
> On Wed, 07 Mar 2007, Tobin Davis wrote:
> > Another question comes to mind.  Why would the volume need to be
> > controlled if there is no sound driver to generate sound?  I'm trying
> > to understand the usage model here for that aspect.
> 
> Because the firmware will happly beep away, and you may want to control the
> volume of those beeps.  And it also controls the volume of the PC buzzer
> (the BIOS makes sure whatever sound hardware is in the machine lets that one
> through by default).

OTOH, from the usability POV, it's really annoying to have two
individual "devices" for the very same output.  That's why I'm in
favor of either built-in-sound-driver or add-on style.

And, if you'll ALSA API for controlling volumes, it assumes that any
sound system is running.   So, it appears logical to me that the
beep-control driver also belongs to a sound driver.

Anyway, if you'd like a stand-alone implementation, we can introduce a
Kconfig, too.  But, note that one merit to use the add-on style
(referring to the exported symbol of snd-intel8x0 driver) is that this
dependency will resolve the module loading order, too.


Takashi

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2007-03-09 16:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-25  1:20 Adding a alsa mixer interface to ibm-acpi Henrique de Moraes Holschuh
2007-02-26 15:31 ` Takashi Iwai
     [not found]   ` <s5h649pue8z.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
2007-02-26 16:28     ` [Alsa-devel] " Henrique de Moraes Holschuh
2007-02-26 16:36       ` [ibm-acpi-devel] " Takashi Iwai
2007-02-26 17:41         ` Henrique de Moraes Holschuh
     [not found]           ` <20070226174145.GF2909-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org>
2007-02-27  1:50             ` [Alsa-devel] " Theodore Tso
2007-02-27  2:14               ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
2007-03-07 21:59                 ` Takashi Iwai
     [not found]                   ` <s5hd53kaf5r.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
2007-03-07 23:02                     ` [Alsa-devel] " Henrique de Moraes Holschuh
2007-03-07 23:12                     ` Shem Multinymous
2007-03-07 23:23                       ` [ibm-acpi-devel] " Tobin Davis
2007-03-07 23:41                         ` Shem Multinymous
2007-03-07 23:42                       ` Henrique de Moraes Holschuh
2007-03-07 23:55                         ` Tobin Davis
     [not found]                           ` <1173311709.4531.30.camel-lPoCD4h/KdUU2NE2KMwFWnnhMCiq3JZZ@public.gmane.org>
2007-03-08  0:38                             ` [Alsa-devel] " Henrique de Moraes Holschuh
2007-03-09 16:29                               ` Takashi Iwai [this message]
     [not found]                                 ` <s5htzwugz22.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
2007-03-10  3:50                                   ` Henrique de Moraes Holschuh
2007-03-12 12:03                                     ` [ibm-acpi-devel] " Takashi Iwai
2007-03-12 21:00                                       ` Henrique de Moraes Holschuh
2007-03-12 22:00                                         ` Alex Deucher

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=s5htzwugz22.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=hmh@hmh.eng.br \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --cc=tytso@mit.edu \
    /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