From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Updated sco flow control feature
Date: Mon, 23 Oct 2006 20:42:05 +0200 [thread overview]
Message-ID: <453D0CFD.1030909@free.fr> (raw)
In-Reply-To: <453BAAFC.1090206@vasmac.com>
Hello Jose,
The documents i used as reference are the ones from bluetooth SIG. I
don't know who copied the others, but they are closely similar to the
one from IEEE :-)
Concerning SCO flow control over UART link, it is stated nowhere it is
mandatory nor optionnal. :-(
However, having a look at the Bluetooth 2.0+EDR spec (available on
www.bluetooth.com), section 6.26 "Supported commands" describes the
bitmask that lists the supported hci commands for a given
implementation, stating that *It is implied that if a command is listed
as supported, the feature underlying that command is also supported.*
And guess what ?.... in the bitmask there is a bit for the "Write
Synchronous flow control enable" command. ;-)
*** cut here ***
0 Read Hold Mode Activity
1 Write Hold Mode Activity
2 Read Transmit Power Level
3 Read Synchronous Flow Control Enable
10
4 Write Synchronous Flow Control Enable
5 Set Host Controller To Host Flow Control
6 Host Buffer Size
7 Host Number Of Completed Packets
*** cut here ***
Having analysed all these informations, my guess is that it is
synchronous flow control is 'optionnal', even for uart links.
Cheers,
Fabien
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-10-23 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 18:09 [Bluez-devel] [PATCH] Updated sco flow control feature Fabien Chevalier
2006-10-12 19:39 ` Jose Vasconcellos
2006-10-13 2:28 ` Brad Midgley
2006-10-13 16:19 ` Fabien Chevalier
2006-10-13 16:19 ` Fabien Chevalier
2006-10-13 18:34 ` Jose Vasconcellos
2006-10-14 16:02 ` Fabien Chevalier
2006-10-14 16:47 ` Jose Vasconcellos
2006-10-22 16:41 ` Fabien Chevalier
2006-10-22 17:31 ` Jose Vasconcellos
2006-10-23 18:42 ` Fabien Chevalier [this message]
2006-10-23 20:09 ` Jose Vasconcellos
2006-10-24 7:34 ` Marcel Holtmann
2006-10-13 2:19 ` Brad Midgley
2006-10-19 17:53 ` Brad Midgley
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=453D0CFD.1030909@free.fr \
--to=fabchevalier@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.