From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <45232AE9.40605@xmission.com> Date: Tue, 03 Oct 2006 21:30:49 -0600 From: Brad Midgley MIME-Version: 1.0 To: BlueZ development References: <4521D857.8000705@vasmac.com> In-Reply-To: <4521D857.8000705@vasmac.com> Subject: Re: [Bluez-devel] SCO packet processing Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net Jose > I realize SCO handling has not been a priority and it sort of works. > Is there much interest in getting it right? I'm very interested in it but I've only been able to address the application side of things. It looks like you've dug in and reached a decent understanding of where problems are. Developers of embedded systems are passing linux/bluez over because voice is too important to just have it "mostly" work. It's unfortunate that Fabien is not still working at it too. I was hoping he would keep a dialog going long enough to find an approach that Marcel likes but it seems like Fabien got tired of pushing it. Brad ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel