From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] How to set packet-type and role from source-code?
Date: Thu, 05 Apr 2007 11:31:26 +0200 [thread overview]
Message-ID: <1175765486.5815.598.camel@violet> (raw)
In-Reply-To: <4614A31C.4010806@free2move.net>
Hi Markus,
> I need to set SCO packet type to HV1 as well as I'd like to specify
> that my device should be the "master" in a SCO connection. I known
> that I can do this from the command-line using the hci* utilities, but
> I'd like to set the packet-types to a known state when I initialize my
> application (from code) and I'm sorry to say that I cannot find how to
> go about and to that...
>
> It has to be possible, but I've search through the hci_lib but without
> success - yet ;)
> Could someone point me in the right direction?
since hciconfig and hcitool can do it, you might wanna have a look at
their source code and see how they handle it.
However I can't advise you to play with the packet types at all. Leave
them as they are. The link manager of the Bluetooth chip knows best what
to do and what packet type to choose.
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:[~2007-04-05 9:31 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 [this message]
2007-04-05 9:51 ` Markus Adolfsson
2007-04-05 9:56 ` Marcel Holtmann
2007-04-05 10:02 ` Mayank BATRA
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=1175765486.5815.598.camel@violet \
--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