From alsa-devel-owner@alsa.jcu.cz  Thu May 14 18:54:41 1998
Received: from ife.ee.ethz.ch (ife-ife1.ee.ethz.ch [129.132.25.65])
	by marvin.jcu.cz (8.8.8/8.8.8) with ESMTP id SAA31843
	for <alsa-devel@jcu.cz>; Thu, 14 May 1998 18:54:40 +0200
Received: from eldrich.ee.ethz.ch (eldrich.ee.ethz.ch [129.132.24.203])
	by ife.ee.ethz.ch (8.8.5/8.8.5) with SMTP id SAA16168
	for <alsa-devel@jcu.cz>; Thu, 14 May 1998 18:54:40 +0200 (MET DST)
Message-ID: <355B21CF.3014@ife.ee.ethz.ch>
Date: Thu, 14 May 1998 18:54:39 +0200
From: Thomas Sailer <sailer@ife.ee.ethz.ch>
MIME-Version: 1.0
To: alsa-devel@jcu.cz
Subject: Re: driver 0.1.0 released
References: <199805111947.VAA24018@obelix.fvdpol.inter.nl.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

> With the POSIX real-time stuff it _might_ be possible to put it in user land

I've done modem stuff with the current Linux RT scheduling which is extremely
latency critical, and it worked.

> but that will introduce more latency, because we can't do event passing from
> interrupt code (eg. on receiving MIDI bytes). We then always need to go
> through the linux scheduler. With the timing stuff in kernel, and this low

So what?  MIDI/Synth stuff isn't exactly high bandwidth/high speed.

Tom

