From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] New bluetooth-headset release 20061109 : nickname 'dogfood' ; -)
Date: Tue, 21 Nov 2006 08:35:00 +0100 [thread overview]
Message-ID: <1164094500.28429.9.camel@localhost> (raw)
In-Reply-To: <456234FB.4020506@xmission.com>
Hi Brad,
> > Regarding the kernel patches, you know I've taken a different
> > approach. I believe that what I posted is simpler and more reliable
> > as it doesn't depend timers. The flow control approach avoids the
> > possibility of getting out of sync with the dongle.
>
> fyi, I talked to Marcel about this and he likes solving it at a higher
> level so the transports (usb/uart/sdio) don't have to each have their
> own solution. Maybe he could articulate it better...
I am not against using flow control, but we must be really careful if it
supported or not. While for ACL it is mandatory, the SCO channel can be
used without it. However even the use of flow control on SCO is a job
for the Bluetooth core and no driver specific one. All Bluetooth drivers
are transport drivers. They have no intelligence whatsoever and they are
not interfering the HCI data. If they need to know some specific details
about changes in the core then the notify() callback is the right place
and if they need a special setup, then a quirk should be used. Other
than that, they are plain stupid and only moving HCI packets to the
hardware and back.
So from my understanding the high resolution timer are a good choice to
submit SCO packets to the hardware. In addition we can enable the flow
control for SCO to have more control over the hardware. However please
keep in mind that the enabling flow control means for traffic on the ACL
links and so you might see a downgrade in bandwidth. So from my current
point of view, the flow control stuff must be optional.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-11-21 7:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 20:42 [Bluez-devel] New bluetooth-headset release 20061109 : nickname 'dogfood' ; -) Fabien Chevalier
2006-11-20 22:33 ` Jose Vasconcellos
2006-11-20 23:06 ` Brad Midgley
2006-11-21 7:35 ` Marcel Holtmann [this message]
2006-11-21 15:03 ` [Bluez-devel] SCO flow control (Was: New bluetooth-headset release 20061109) Jose Vasconcellos
2006-11-21 15:26 ` Marcel Holtmann
2006-11-21 17:26 ` Jose Vasconcellos
2006-11-21 17:53 ` Marcel Holtmann
2006-11-21 18:52 ` [Bluez-devel] New bluetooth-headset release 20061109 : nickname 'dogfood' ; -) Jose Vasconcellos
2006-11-21 20:05 ` Fabien Chevalier
2006-11-21 20:39 ` Jose Vasconcellos
2006-11-22 11:12 ` Fabien Chevalier
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=1164094500.28429.9.camel@localhost \
--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 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.