From owner-freebsd-current@FreeBSD.ORG  Sat Aug  9 17:31:51 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id D15AB37B401; Sat,  9 Aug 2003 17:31:51 -0700 (PDT)
Received: from puma.icir.org (puma.icir.org [192.150.187.73])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4D18143FBD; Sat,  9 Aug 2003 17:31:51 -0700 (PDT)
	(envelope-from hodson@puma.icir.org)
Received: from puma.icir.org (localhost [127.0.0.1])
	by puma.icir.org (8.12.8p1/8.12.3) with ESMTP id h7A0VksL025876;
	Sat, 9 Aug 2003 17:31:46 -0700 (PDT)
	(envelope-from hodson@puma.icir.org)
Message-Id: <200308100031.h7A0VksL025876@puma.icir.org>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.3
To: Kris Kennaway <kris@obsecurity.org>
From: Orion Hodson <orion@freebsd.org>
In-Reply-To: Your message of "Sat, 09 Aug 2003 16:01:30 PDT."
             <20030809230129.GA7359@rot13.obsecurity.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 09 Aug 2003 17:31:46 -0700
Sender: hodson@icir.org
cc: current@freebsd.org
cc: Dmitry Sivachenko <mitya@cavia.pp.ru>
cc: sound@freebsd.org
Subject: Re: LOR in pcm 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Aug 2003 00:31:52 -0000

/-- Kris Kennaway wrote:
| 
| LORs in the pcm system are reported quite regularly, but I haven't
| seen anyone working on the problem.  Is there anyone who can look at
| the locking code used in this system and fix the problems?  Perhaps
| this should be added to the 5.2 TODO list.
| =20

I'm unaware of anybody chasing this though I'm not very closely involved with sound@freebsd.org these days.  Last I knew cg was focusing his energies on a new freebsd sound architecture to better cater for modern audio h/w.

If somebody was interested in taking this issue on, it would be of immediate benefit to the project.

Regards
- Orion