All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Duncan Sands <baldrick@wanadoo.fr>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: init script with hotplug & usb audio
Date: Mon, 30 Sep 2002 12:04:35 +0200	[thread overview]
Message-ID: <s5hheg7lrnw.wl@alsa2.suse.de> (raw)
In-Reply-To: <200209300955.14788.baldrick@wanadoo.fr>

At Mon, 30 Sep 2002 09:55:14 +0200,
Duncan Sands wrote:
> 
> On Friday 27 September 2002 19:53, Takashi Iwai wrote:
> > except for the check of /proc/asound, the hotplug problem can be
> > sorted to the following:
> >
> > 1. hotplug may be called before alsa init script.
> >
> > 2. hotplug needs to manage the mixer configuration of plugged /
> >    unplugged devices dynamically.
> >
> > 3. alsa initscript itself should be independent from hotplug.
> >
> > they are not all but certainly a major part of the problems.
> >
> >
> > the first one is not easy, because the network devices can belong to
> > hotplug, too.  the scenario is like this:
> >   many alsa files are located under /usr
> >     -> a networkfs (e.g. NFS) is required before the alsa service
> >       -> the network must be initialized in prior
> >         -> the network base = hotplug is needed to run before alsa!
> >
> > the second problem is also tough.
> > alsa driver needs to access the device to get the current mixer
> > values, but at the remove callback of hotplug, the device was actually
> > unplugged...  probably implementing cache would be necessary.
> 
> Another point to keep in mind here, is that a lot of people are now
> using journaled filesystems, and may just turn off the computer
> without shutting down.  You could say that they deserve what they
> get, but I'm not so sure.  Imagine someone using alsamixer to change
> mixer settings.  They quit alsamixer then turn off the machine.  Are
> they wrong to expect the mixer settings to still be there on reboot?

yes.  the infromation will be lost.

> After all, they "saved the settings" when they left alsamixer didn't they?

no, the setting is on memory, thus not saved when you turn the power
off.  he can run "alsactl store" manually (or write a equivalent
wrapper script for alsamixer) instead.
but this should not be standard, i think.


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-09-30 10:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-26  8:20 init script with hotplug & usb audio Duncan Sands
2002-09-26 10:40 ` Tim Goetze
2002-09-27  7:11   ` Duncan Sands
2002-09-26 11:49 ` Takashi Iwai
2002-09-27  7:08   ` Duncan Sands
2002-09-27 17:53     ` Takashi Iwai
2002-09-30  7:55       ` Duncan Sands
2002-09-30 10:04         ` Takashi Iwai [this message]
2002-10-01  6:46           ` Duncan Sands

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=s5hheg7lrnw.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=baldrick@wanadoo.fr \
    /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.