From: Wolfgang Grandegger <wg@domain.hid>
To: witzel.thomas@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] RTDM/ALSA hybrid driver ?
Date: Wed, 01 Nov 2006 14:28:08 +0100 [thread overview]
Message-ID: <4548A0E8.3070005@domain.hid> (raw)
In-Reply-To: <200611010745.23388.witzel.thomas@domain.hid>
Thomas Witzel wrote:
> On Wednesday 01 November 2006 01:58, Romain Lenglet wrote:
>> Since you wanted to develop/port your own device driver anyway, I
>> just suggested to use JACK as an interface with your
>> applications, instead of the ALSA interface. I believe that the
>> JACK API/interface is better suited for realtime applications.
>> So why not develop your own new JACK hard-realtime backend with
>> your RTDM driver?
> I just wanted to modify an existing driver Intel8x0 AC97 to do realtime
> playback of a sample. I'm still pursuing this.
> I have implemented a regular Linux userspace application for this at first and
> it provides a response latency smaller than 1 ms for 19 out of 20 triggers,
> but the 20th (on average) has latencies up to 20ms, which is totally
> unacceptable.
Linux should be able to do better than that. Is your application
prioritized properly (check for real-time priorities with "man
sched_setscheduler")? And the kernel option CONFIG_PREEMPT should also
help.
Wolfgang.
next prev parent reply other threads:[~2006-11-01 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 20:10 [Xenomai-help] RTDM/ALSA hybrid driver ? Thomas Witzel
2006-10-25 20:34 ` Jan Kiszka
2006-10-26 3:13 ` Romain Lenglet
2006-11-01 5:18 ` Thomas Witzel
2006-11-01 6:58 ` Romain Lenglet
2006-11-01 12:45 ` Thomas Witzel
2006-11-01 13:28 ` Wolfgang Grandegger [this message]
[not found] ` <200610251640.22737.witzel.thomas@domain.hid>
[not found] ` <453FEE9F.9080209@domain.hid>
2006-11-01 2:45 ` Thomas Witzel
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=4548A0E8.3070005@domain.hid \
--to=wg@domain.hid \
--cc=witzel.thomas@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.