From: Lee Revell <rlrevell@joe-job.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: "Brown, Len" <len.brown@intel.com>,
Bill Davidsen <davidsen@tmr.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: Variable ticks
Date: Wed, 27 Jul 2005 16:43:07 -0400 [thread overview]
Message-ID: <1122496987.22844.3.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.61.0507270212080.7784@montezuma.fsmlabs.com>
On Wed, 2005-07-27 at 02:13 -0600, Zwane Mwaikambo wrote:
> > What about audio? If there is a sound server running then you're going
> > to have a constant stream of interrupts and DMA activity from the sound
> > card even if the machine is idle and there aren't any sounds playing.
>
> Doesn't artsd at least close the audio device after some configurable idle
> time? In which case that sounds like a userspace issue.
Well, as of ALSA 1.0.9 which does software mixing and volume control by
default, all the sound servers are obsolete. So this should be a
non-issue with a modern distro.
As far as legacy support, AFAIK esd and artsd both grab the sound device
on startup and never release it.
Lee
next prev parent reply other threads:[~2005-07-27 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 21:19 Variable ticks Brown, Len
2005-07-25 21:25 ` Lee Revell
2005-07-27 8:13 ` Zwane Mwaikambo
2005-07-27 20:43 ` Lee Revell [this message]
2005-07-27 21:06 ` Valdis.Kletnieks
2005-07-27 22:03 ` Zwane Mwaikambo
2005-07-26 15:50 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2005-07-26 16:08 Brown, Len
2005-07-25 19:10 Brown, Len
2005-07-25 21:05 ` Bill Davidsen
2005-07-25 18:59 Bill Davidsen
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=1122496987.22844.3.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=davidsen@tmr.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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