From: Lee Revell <rlrevell@joe-job.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: mjc@unre.st, linux-kernel@vger.kernel.org
Subject: Re: Updated realtime-preempt documentation
Date: Sat, 30 Apr 2005 14:17:36 -0400 [thread overview]
Message-ID: <1114885056.10415.2.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.44.0504300723260.18872-100000@dhcp153.mvista.com>
On Sat, 2005-04-30 at 07:28 -0700, Daniel Walker wrote:
> On Sat, 30 Apr 2005, Lee Revell wrote:
>
> >
> > I think it's changing too fast for anyone to have bothered to document
> > it yet.
>
> That's true for some of it, but like interrupts in threads hasn't changed
> in a few months .. The config options aren't likely to change ..
>
Right now there's this:
http://www.affenbande.org/~tapas/wiki/index.php?Low%20latency%20for%
20audio%20work%20on%20linux%202.6.x
It's slightly outdated and focuses only on using the RT kernel for low
latency audio with JACK, but I think it's the best user level doc so
far.
Lee
next prev parent reply other threads:[~2005-04-30 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 5:37 Updated realtime-preempt documentation mjc
2005-04-30 6:11 ` Lee Revell
2005-04-30 14:28 ` Daniel Walker
2005-04-30 18:17 ` Lee Revell [this message]
2005-04-30 14:22 ` Daniel Walker
2005-04-30 15:39 ` john cooper
2005-04-30 20:31 ` Jonathan Corbet
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=1114885056.10415.2.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjc@unre.st \
/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