From: Flávio <flavio.henriques@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] TPL (transmit power level)
Date: Tue, 22 Feb 2005 02:16:43 +0000 [thread overview]
Message-ID: <de33c8be050221181635c1a751@mail.gmail.com> (raw)
In-Reply-To: <1109028291.7626.45.camel@pegasus>
Hi Marcel,=20
nice to see you back :)
About the the patch for the bug i can=B4t do it because i don=B4t know how!
Linux isn=B4t my usual OS ,sorry!
One more question about this topic.
In bluetooth core says that the range of the tpl (transmit power
level) is between -30<=3D N<=3D20 and the step (resolution) is one
unit,but when i execute the command hci_read_tpl (transmit power
level) all the values that i receive are:
17 ; 14 ; 10 ; 6 ; 2 ; -2 ; -6 ; -9 and no more :(
why? it=B4s something about Bluez or is the Firmware (of my dongle usb)
that realy gives that values for tpl?
thanks in advanced
Regards Fl=E1vio!
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-02-22 2:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 12:25 [Bluez-devel] TPL (transmit power level) Flávio
2005-02-21 23:24 ` Marcel Holtmann
2005-02-22 2:16 ` Flávio [this message]
2005-02-22 2:28 ` Marcel Holtmann
2005-02-22 3:09 ` Flávio
2005-02-22 3:16 ` Marcel Holtmann
2005-02-22 14:43 ` Flávio
2005-02-22 15:08 ` Marcel Holtmann
2005-02-22 15:20 ` Flávio
2005-02-22 16:59 ` Steven Singer
2005-02-22 19:20 ` Flávio
2005-02-23 14:43 ` Steven Singer
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=de33c8be050221181635c1a751@mail.gmail.com \
--to=flavio.henriques@gmail.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.