From alsa-devel-owner@alsa.jcu.cz  Wed Jan 27 01:47:27 1999
Received: from pm-ppp43.triton.net (pm-ppp43.triton.net [209.172.11.43])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id BAA22358
	for <alsa-devel@alsa.jcu.cz>; Wed, 27 Jan 1999 01:47:08 +0100
Received: (from kor@localhost)
	by pm-ppp43.triton.net (8.9.1/8.9.1) id TAA22134
	for alsa-devel@alsa.jcu.cz; Tue, 26 Jan 1999 19:47:00 -0500
Message-ID: <19990126194659.A22025@pm-ppp43.triton.net>
Date: Tue, 26 Jan 1999 19:46:59 -0500
From: Adam Scislowicz <core@triron.net>
To: alsa-devel@alsa.jcu.cz
Subject: Driver Support
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

Sorry to bother you all with this, but I saw mention that someone from
creative labs was wanting to work out a way for the SBLive to gain driver
support from ALSA? is there any more information, how soon could this happen?

Also I would really appreciate it if someone could add DEVFS support to ALSA,
it will most likely be included in the standard kernel very soon, it would
require the devices to be kept in /dev/sound though, which is much cleaner,
and really since ALSA is still fairly new, not all that many apps need to be
patched, and the patch would be very small... Symlinks could be maintained for
a few months to keep compatibility...

-- 
Adam D. Scislowicz
core@triton.net

