From: Jose Vasconcellos <jose@vasmac.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] SCO flow control patches
Date: Tue, 19 Sep 2006 22:07:46 -0400 [thread overview]
Message-ID: <4510A272.6000402@vasmac.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
Hello,
Last May, Fabien Chevalier posted some SCO flow control patches
(now included in bluetooth-alsa). I've tried these in Ubuntu 6.06
(based on kernel 2.6.15.7) without much luck. My problem is that
packets are sent every 50ms. Anyone else tried these?
I do agree that it should be the responsibility of the driver to take
care of any timing issues. But it's not clear to me why this is not
done in the hci_usb driver.
Jose
[-- Attachment #2: jose.vcf --]
[-- Type: text/x-vcard, Size: 288 bytes --]
begin:vcard
fn:Jose Vasconcellos
n:Vasconcellos;Jose
org:Vas & Mac Enterprises LLC
adr:;;P.O. Box 567;Red Bank;NJ;07701;USA
email;internet:jose@vasmac.com
title:Managing Member and CTO
tel;work:+1 732 978 4680 x102
tel;fax:+1 206 888 6951
url:http://www.vasmac.com
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 348 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-09-20 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 2:07 Jose Vasconcellos [this message]
2006-09-25 21:51 ` [Bluez-devel] SCO flow control patches 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=4510A272.6000402@vasmac.com \
--to=jose@vasmac.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