From owner-freebsd-bluetooth@FreeBSD.ORG  Thu Jul 28 09:43:24 2005
Return-Path: <owner-freebsd-bluetooth@FreeBSD.ORG>
X-Original-To: freebsd-bluetooth@freebsd.org
Delivered-To: freebsd-bluetooth@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D157E16A41F
	for <freebsd-bluetooth@freebsd.org>;
	Thu, 28 Jul 2005 09:43:24 +0000 (GMT)
	(envelope-from urnenfel@tiscali.es)
Received: from smtp018.mail.yahoo.com (smtp018.mail.yahoo.com
	[216.136.174.115])
	by mx1.FreeBSD.org (Postfix) with SMTP id 9288B43D46
	for <freebsd-bluetooth@freebsd.org>;
	Thu, 28 Jul 2005 09:43:24 +0000 (GMT)
	(envelope-from urnenfel@tiscali.es)
Received: (qmail 37245 invoked from network); 28 Jul 2005 09:43:24 -0000
Received: from unknown (HELO @vodafone.es) (urnen81@84.173.174.209 with login)
	by smtp018.mail.yahoo.com with SMTP; 28 Jul 2005 09:43:22 -0000
Date: Thu, 28 Jul 2005 11:37:13 +0000
From: Oliver <urnenfel@tiscali.es>
Message-Id: <20050728113713.2925.5@@vodafone.es>
Mime-Version: 1.0
To: freebsd-bluetooth@freebsd.org
User-Agent: Beam yT Release
Content-Type: text/plain;
 charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: SCO / eSCO
X-BeenThere: freebsd-bluetooth@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Using Bluetooth in FreeBSD environments
	<freebsd-bluetooth.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bluetooth>
List-Post: <mailto:freebsd-bluetooth@freebsd.org>
List-Help: <mailto:freebsd-bluetooth-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2005 09:43:24 -0000

Hi to the list.

I am taking a deep look to the FreBSD bt stack, net_graph etc to understand 
it completely and being able to help somehow(if needed).

A first question is (if we do)where do we implement the SCO 
protocol/link_type

If not how should it be done? 
As upper protocols of the HCI layer?
keeping 3 upper protocols for the HCI: L2CAP SCO eSCO ?

Are those 3 different from each other? L2CAP<->SCO I guess radically yes, 
but is planned/designed to implement eSCO together with SCO in the same 
ng_node?

Thanks a lot in advance! 

		
______________________________________________ 
Renovamos el Correo Yahoo! 
Nuevos servicios, más seguridad 
http://correo.yahoo.es