Message-ID: <409B833B.8070203@superbug.demon.co.uk>
From: James Courtier-Dutton <James@superbug.demon.co.uk>
MIME-Version: 1.0
To: "Nicholas A. Preyss" <nalp@gmx.net>
CC: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] questions about BT audio headset support...
References: <409AD45D.6080102@dark-reality.de> <20040507113025.GA23044@gmx.net>
In-Reply-To: <20040507113025.GA23044@gmx.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Date: Fri, 07 May 2004 12:38:19 +0000

Nicholas A. Preyss wrote:
> 
> 
> In my opinion, the whole connection handling should be done in
> user-space. In kernel-space only a generic "sco channel" - "alsa device" 
> binding interface should stay. 
> 
> nicholas
> 
> 

I think it might be worth trying to find out if one can get alsa-lib to 
use a user-space device driver. Then everything will stay in user space 
until it reaches the bluez code.

Cheers
James


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel