From: Joseph Garcia <jpgarcia@execpc.com>
To: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: patches: MacOS-like Wallstreet sound in/out controls
Date: Sun, 19 Sep 1999 11:15:37 -0500 [thread overview]
Message-ID: <37E50C29.CA2CE536@execpc.com> (raw)
In-Reply-To: 19990919105401.015601@smtp.calvacom.fr
Benjamin Herrenschmidt wrote:
> 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...)
since we aren't psychics, the daemon should have a configuration and script
place in /etc (/etc/pmu?). the config would allow the user to control some
standard responses on how it acts internally. (like volume control, switching,
etc) then the option to do additional things in scripts. Given the potential
flexibility people may want, does this mean C is too static, and thus perl or
another more script-friendly language should be used?
If all goes well, we may eventually have a "apmd" for ppc. any reason we
shouldn't try to use apmd as a framework? have a so-called "apmd-compatibility"
mode where we can use the standard PC apmd as our frontend? or does it not have
features like eth detect, so its not worth the bother? (never had a pc laptop)
a few ideas from a peanut.
--
Joseph P. Garcia jpgarcia@execpc.com jpgarcia@lidar.ssec.wisc.edu
CS Undergraduate Student Employee - Systems Programmer
University of Wisconsin - Madison UW Lidar Group
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-19 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-19 8:54 patches: MacOS-like Wallstreet sound in/out controls Benjamin Herrenschmidt
1999-09-19 16:15 ` Joseph Garcia [this message]
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=37E50C29.CA2CE536@execpc.com \
--to=jpgarcia@execpc.com \
--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).