From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Help - power control
Date: Tue, 01 Feb 2005 17:15:59 +0100 [thread overview]
Message-ID: <1107274559.9652.55.camel@pegasus> (raw)
In-Reply-To: <de33c8be0502010808e419a69@mail.gmail.com>
Hi Flavio,
> I=B4m trying to make a program with the library BlueZ but
> without detailed information about the functions is very dificult
> (even reading the bluetooth specifications)! where i could find that
> information? BlueZ don=B4t have manual :( :(
but you can use the source, Luke ;)
> The tutorials indicated in www.bluez.org don=B4t give me any help since
> the program need to work in a low level (example, power control)!
If you talk about transmit power then this is not controllable from your
application, because it is the job of the link manager.
> Second:
> How can i make a dongle bluetooth comunicate always with the sa=
me power?
> The functions related with the power are:
> _read_rssi -> the power received;
> _transmit_power-> the power in transmition.
Again, this is job of the link manager.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-02-01 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 16:08 [Bluez-devel] Help - power control Flávio
2005-02-01 16:15 ` Marcel Holtmann [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=1107274559.9652.55.camel@pegasus \
--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