All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Thomas Charbonnel <thomas@undata.org>
Cc: perex@suse.cz, alsa-devel@alsa-project.org
Subject: Re: future ALSA development
Date: Mon, 07 Jul 2003 13:37:05 +0200	[thread overview]
Message-ID: <s5h8yraeffi.wl@alsa2.suse.de> (raw)
In-Reply-To: <32900.81.50.18.84.1057248308.squirrel@www.undata.org>

At Thu, 3 Jul 2003 18:05:08 +0200 (CEST),
Thomas Charbonnel wrote:
> 
> > Hello all,
> >
> > 	here are my next goals for the ALSA library development (short
> > term). I invite all developers to comment these directions.
> >
> 
> [...]
> 
> > * initiate a development of a graphical tool which will manage
> >   the alsa configuration files (~/.asoundrc)
> >   - we need a rapid development tool; I slowly became a fan of python
> > and
> >     Qt has rich number of widgets; python + PyQt seems to me a good idea
> >   - using python requires to write a GPLed ALSA 0.9 -> python wrapper
> >
> 
> One point I would like to bring to focus is how sound hardware state
> persistance is dealt with. The limits of alsactl are showing up with
> hardware like the hdsp, were the card might not be fully initialized (or
> not even present yet, e.g. cardbus) at boot time. We're more and more
> likely to have to deal with such external hotpluggable devices (pcmcia,
> firewire, usb), where full initialization can happen any time after the
> boot process, and we can't expect the average user to be scripting around.
> 
> IMHO state restoration could be :
> * triggered by the driver, at the appropriate time, depending maybe on
> some system configuration options.

it would be feasible only if we have a certain daemon.
otherwise, i don't think its a good style to invoke a user-space tool
from the kernel driver.

> * initiated by the user, through the configuration GUI.
 
or: more clever hotplug scripts.

basically, the whole initialization stuff for such dynamic devices is
the job of hotplug manager.  so, we can provide a proper init/delete
script for each card.  e.g. loading the firmware, then set up the
default or restore the last status.

but yes, for this way, it would be nice to have a "state", so that
alsactl can know whether the data to restore matches with the current
state.  in this way, the unmatching data can be ignored by the first
call of alsactl in the init script.


Takashi



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01

      reply	other threads:[~2003-07-07 11:37 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22 19:10 future ALSA development Jaroslav Kysela
2003-06-23 11:14 ` Takashi Iwai
2003-06-23 12:01   ` Jaroslav Kysela
2003-06-23 13:13     ` Takashi Iwai
2003-06-23 13:41       ` Paul Davis
2003-06-23 13:51         ` Takashi Iwai
2003-06-23 14:18           ` Paul Davis
2003-06-23 22:22     ` Joern Nettingsmeier
2003-06-24  7:51       ` mru
2003-06-24  8:14       ` Jaroslav Kysela
2003-06-24 11:19         ` Abramo Bagnara
2003-06-24 11:43         ` Paul Davis
2003-06-24 11:56           ` Jaroslav Kysela
2003-06-24 12:16             ` Paul Davis
2003-06-24 17:11               ` Takashi Iwai
2003-06-24 18:28                 ` Jaroslav Kysela
2003-06-25 17:49                   ` PCMCIA In Kernel Or In ALSA Driver? Len Moskowitz
2003-06-25 18:51                     ` Jaroslav Kysela
2003-06-30 10:17                   ` future ALSA development Takashi Iwai
2003-06-24  8:28       ` iriXx
2003-07-03 13:39       ` Kai Vehmanen
2003-07-07 11:26         ` Takashi Iwai
2003-10-01  9:37           ` ALSA in embedded use (was: Re: future ALSA development) Kai Vehmanen
2003-10-01 13:13             ` Takashi Iwai
2003-06-24 12:52   ` future ALSA development Giuliano Pochini
2003-06-24 13:04     ` Jaroslav Kysela
2003-06-24 17:12       ` Takashi Iwai
2003-07-03 14:21 ` Kai Vehmanen
2003-07-03 14:36   ` Kai Vehmanen
2003-07-03 16:05 ` Thomas Charbonnel
2003-07-07 11:37   ` Takashi Iwai [this message]

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=s5h8yraeffi.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@suse.cz \
    --cc=thomas@undata.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.