From: Benjamin Herrenschmidt <bh40@calva.net>
To: dmalek@jlc.net, linuxppc-dev@lists.linuxppc.org
Subject: Re: patches: MacOS-like Wallstreet sound in/out controls
Date: Sun, 19 Sep 1999 10:54:01 +0200 [thread overview]
Message-ID: <19990919105401.015601@smtp.calvacom.fr> (raw)
On Sun, Sep 19, 1999, Dan Malek <dmalek@jlc.net> wrote:
>Since I was the last one to check in changes to the driver, I have kind of
>been nominated to do this again. I have patches from several people for some
>functional updates on new hardware. I can add these in/out controls if
>people really want them.
>
>
>While I understand the convenience of these in/out controls, I personally
>don't
>like them. I run a variety of programs that perform these operations for me.
>Sometimes I want to run both line out and speakers at the same time, or
select
>the microphone without having to unplug line in. I guess the in/out doesn't
>prevent
>me from doing this, just that a change (plug in or out) will cause a
>configuration
>change without my mixer knowing. If people generally want these, I'll put
>them
>in along with the other changes I am making.
A better solution would be to make the appropriate infos available to
userland (eventually via a private ioctl of the sound driver). Then, we
could have an optional damon handling all this automatically that can be
unplugged for people who like controlling everything manually. If no-one
have time to write this, then you may include the patches anyway but
wrapped in a compile option. (I'd like the volume button patch anyway).
On a similar way, I'm wondering what is the best way for the eth driver
to tell userland about it's link status. I'd like to add to Paul's pmud a
way to have scripts run when the link goes down and up. (basically, this
would ifdown eth0 completely to remove it from the router, change my
default route to the one I need for PPP, etc...)
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-09-19 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-19 8:54 Benjamin Herrenschmidt [this message]
1999-09-19 16:15 ` patches: MacOS-like Wallstreet sound in/out controls Joseph Garcia
1999-09-19 16:54 ` Shaw Terwilliger
1999-09-19 16:59 ` sound sleep Joseph Garcia
1999-09-19 17:18 ` sound sleep (more) Joseph Garcia
1999-09-20 2:17 ` sound sleep Takashi Oe
1999-09-20 22:24 ` Joseph Garcia
-- strict thread matches above, loose matches on Subject: below --
1999-09-19 6:55 patches: MacOS-like Wallstreet sound in/out controls Joseph Garcia
1999-09-19 7:55 ` Dan Malek
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=19990919105401.015601@smtp.calvacom.fr \
--to=bh40@calva.net \
--cc=dmalek@jlc.net \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).