From: Mayank BATRA <mayank.batra@st.com>
To: "'BlueZ development'" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] How to set packet-type and role from source-code?
Date: Thu, 5 Apr 2007 15:32:26 +0530 [thread overview]
Message-ID: <008c01c77769$838ff6b0$9d0cc70a@dlh.st.com> (raw)
In-Reply-To: <4614C6B7.9040008@free2move.net>
Hi Markus ,
> If I connect multiple SCO connections from my embedded platform, will
the packet-types dynamically adjust when I add a second and even third
SCO connection? This is why I though I had to specifically set
packet-type to HV1... Could you (or someone that feel for it) just
confirm my thoughts? ;)
First of all you can have only one HV1 SCO link at a time. If you want
three, use HV3. This is because an HV1 packet carries only 10 bytes of
data. Thus in order to have a 64 Kbps HV1 link, SCO packets will have to
be sent every second slot (Tsco = 2) => there is no room for another SCO
link. 64 Kbps HV1 SCO link will cover 100% bluetooth bandwidth. Whereas
HV3 packet carries 30 bytes of data => you can maintain (theoretically
atleast) 3 SCO Links.
Best Regards,
Mayank
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-04-05 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 7:19 [Bluez-devel] How to set packet-type and role from source-code? Markus Adolfsson
2007-04-05 9:31 ` Marcel Holtmann
2007-04-05 9:51 ` Markus Adolfsson
2007-04-05 9:56 ` Marcel Holtmann
2007-04-05 10:02 ` Mayank BATRA [this message]
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='008c01c77769$838ff6b0$9d0cc70a@dlh.st.com' \
--to=mayank.batra@st.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