public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Updated sco flow control feature
Date: Tue, 24 Oct 2006 09:34:40 +0200	[thread overview]
Message-ID: <1161675280.10866.127.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <453D2170.8010600@vasmac.com>

Hi Jose,

> Very interesting. I interpreted this to mean that if synchronous
> channels are supported, then synchronous flow control is required.
> Some form of feedback from the HCI device is required to main
> synchronization. If you use timers you run occasional the risk of
> getting out of sync.

that shouldn't be such a problem. It is only audio data.

> All this speculation can be clarified if someone with an actual UART
> dongle can speak up. The patch that I posted should work as long
> as the device implements synchronous  flow control. Maybe the
> solution is to not support SCO on UART until someone can take
> responsibility.

I have a couple of UART based development kits at home and I can
actually test it. However you shouldn't think about the actual transport
at all. This is the job of the driver and not the Bluetooth core. So it
must work with SCO flow control enabled and disabled.

> BTW, the IEEE spec is the base for bluetooth.

That is wrong. The IEEE specification was written based on the Bluetooth
specification. What gets released by the Bluetooth SIG at bluetooth.com
is the specification that counts.

Regards

Marcel



-------------------------------------------------------------------------
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

  reply	other threads:[~2006-10-24  7:34 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
2006-10-23 20:09                 ` Jose Vasconcellos
2006-10-24  7:34                   ` Marcel Holtmann [this message]
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=1161675280.10866.127.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --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