From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] New bluetooth-headset release 20061109 : nickname 'dogfood' ; -)
Date: Mon, 20 Nov 2006 16:06:35 -0700 [thread overview]
Message-ID: <456234FB.4020506@xmission.com> (raw)
In-Reply-To: <45622D23.7070105@vasmac.com>
Jose
> 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...
Brad
-------------------------------------------------------------------------
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-20 23:06 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 [this message]
2006-11-21 7:35 ` Marcel Holtmann
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=456234FB.4020506@xmission.com \
--to=bmidgley@xmission.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 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.