Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Benno Senoner <sbenno@gardena.net>
To: linux-sound@vger.kernel.org
Subject: Re: [linux-audio-dev] Re: HZ > 100 overhead
Date: Fri, 29 Oct 1999 00:02:09 +0000	[thread overview]
Message-ID: <marc-linux-sound-94118118519929@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-94113791209316@msgid-missing>

On Thu, 28 Oct 1999, Paul Barton-Davis wrote:
> 
> take a system in which, say, Quasimodo was running through the server
> or was the server and SoftWerk ran along side it. SoftWerk doesn't
> talk to the audio h/w at all, but it wants timing from the RTC. the
> server might want timing from the RTC. a 3rd program runs and wants to
> to use the RTC for something completely non-audio related.
> 
> in these kinds of situations, you don't want to have merged RTC
> service into an "multimedia server" - someone who wants to use the RTC
> for something completely different is going to be unhappy at being
> forced to connect to the multimedia server if the server is running
> (and thus owns the RTC).


> 
> that's why I think that the RTC *must* be considered a standalone
> system utilized either by a single (greedy) application, or by a
> server *that does nothing else* but distribute timing info to clients.

You convinced me  :-) 
Agreed, rtcd will run as standalone app and 
the multimedia API will provide a timerwrapper which connects
to rtcd if requested , ok ?

Benno.

      reply	other threads:[~1999-10-29  0:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-28 15:59 [linux-audio-dev] Re: HZ > 100 overhead Paul Barton-Davis
1999-10-29  0:02 ` Benno Senoner [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=marc-linux-sound-94118118519929@msgid-missing \
    --to=sbenno@gardena.net \
    --cc=linux-sound@vger.kernel.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