linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denis KENZIOR <denis.kenzior@trolltech.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Esco implementation patch
Date: Thu, 3 May 2007 15:00:05 +1000	[thread overview]
Message-ID: <200705031500.06707.denis.kenzior@trolltech.com> (raw)
In-Reply-To: <001501c78d3c$dd4f3ba0$9d0cc70a@dlh.st.com>

Mayank,

> How about the 2-EV* and 3-EV* packet types? The spec says that a 0 for
> these bits means they have been enabled. Shouldn't you also check for their
> support in the feature mask?

Good question.  I'm not entirely sure of this, however I did not interpret the 
specification in this manner.  All it says is that there is a specific 
feature mask to disable 2-EV and 3-EV packets.  There is nothing to say 
whether or not they are explicitly enabled.  Also the examples in the 
specification use the esco feature masks in the same manner as I do.  So I 
would assume that if EV3 support is not enabled, then 2-EV3 and 3-EV3 packets 
will not be used by the controller as well.  However, I could be wrong.

>
> > I've tested it on several machines here, including eSco->eSco
> > connection, eSco->sco connection for both incoming and outgoing
> > scenarios, everything seems fine, however I'm sure more testing is
> > required.
>
> How did you mangage to set up an eSCO since you are using only HV* packet
> types (ESCO_PTYPE_MASK)? Or is it because the 2-EV* and 3-EV* bits are "0"
> thus the controller thinks you want to enable those packet types?

Well, it comes down to what the controller labels as an eSCO connection.  E.g. 
the link_type returned in the connection complete and sync connection 
complete events.  Doing BlueZ<->BlueZ which both use the patch, I get 
link_type of eSCO.  Doing BlueZ<->BlueZ with one end not using the patch, I 
get a link_type of SCO.  Perhaps it is the particular hardware I'm using?

Setup is a STLC2500 serial device connected to a BT1.2 USB dongle on a 
non-patched kernel and a BT 2.0 USB dongle on a patched kernel.

Regards,
-Denis


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-05-03  5:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25  6:58 [Bluez-devel] Esco implementation patch Sumeet VERMA
2007-04-25  7:44 ` Marcel Holtmann
2007-04-26  4:56   ` Sumeet VERMA
2007-04-26  5:19     ` Denis KENZIOR
2007-04-26  6:24       ` Mayank BATRA
2007-04-26  6:29       ` Sumeet VERMA
2007-04-26 10:19         ` dkenzior
2007-04-26 10:36           ` Sumeet VERMA
2007-04-26 14:18             ` Marcel Holtmann
2007-04-26 19:40         ` Marcel Holtmann
2007-04-27  7:50           ` Sumeet VERMA
2007-05-01 11:24             ` Marcel Holtmann
2007-05-03  3:57               ` Denis KENZIOR
2007-05-03  4:38                 ` Mayank BATRA
2007-05-03  5:00                   ` Denis KENZIOR [this message]
2007-05-03  5:16                     ` Marcel Holtmann
2007-05-03  5:23                       ` Mayank BATRA
2007-05-03  5:29                         ` Marcel Holtmann
2007-05-03  5:24                       ` Denis KENZIOR
2007-05-03  5:28                         ` Marcel Holtmann
2007-05-03  5:25                 ` Marcel Holtmann
2007-05-04  7:36                   ` Denis KENZIOR
2007-05-04  8:53                     ` [Bluez-devel] sdpd and multiple bluetooth devices Olivier Le Pogam
2007-05-04  9:18                       ` Marcel Holtmann

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=200705031500.06707.denis.kenzior@trolltech.com \
    --to=denis.kenzior@trolltech.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;
as well as URLs for NNTP newsgroup(s).