From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SCO in BlueZ
Date: Mon, 18 Jul 2005 12:43:42 -0600 [thread overview]
Message-ID: <42DBF85E.8040407@xmission.com> (raw)
In-Reply-To: <20050718180329.52966.qmail@web26909.mail.ukl.yahoo.com>
Javi,
sco/esco is passed directly through the hci layer.
l2cap is only involved in handsfree/headset profiles for negotiating the
connection via the separate rfcomm connection. this rfcomm connection
uses AT commands.
brad
javier labella wrote:
> Hi,
> I'm thinking to develop a profile on BlueZ, but even I'm not sure that
> with bluez I could implement a profile that uses SCO links, that is to
> say, I don't know if the SCO links are implemented in the l2cap.
>
> Thanks for reading,
> Javi.
>
> ------------------------------------------------------------------------
>
> Correo Yahoo!
> Comprueba qué es nuevo, aquí
> <http://us.rd.yahoo.com/mail/es/whatsnew/*http://es.whatsnew.mail.yahoo.com/>
> http://correo.yahoo.es
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-07-18 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 18:03 [Bluez-devel] SCO in BlueZ javier labella
2005-07-18 18:34 ` Marcel Holtmann
2005-07-18 18:43 ` Brad Midgley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42DBF85E.8040407@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox