From: Marcel Holtmann <marcel@holtmann.org>
To: anderson.briglia@openbossa.org
Cc: linux-bluetooth@vger.kernel.org,
Bruna Moreira <bruna.moreira@openbossa.org>
Subject: Re: [RFC 2/3] Bluetooth: Implement Read Transmit Power Level command
Date: Wed, 13 Jul 2011 20:13:59 +0200 [thread overview]
Message-ID: <1310580840.21109.97.camel@aeonflux> (raw)
In-Reply-To: <4e1da4a8.04bfec0a.4243.00da@mx.google.com>
Hi Anderson,
> Add Read Transmit Power Level command in MGMT Interface and all
> infrastructure need for that.
>
> Read Transmit Power Level command is defined on Part E, section 7.3.35
> of Bluetooth 4.0 Spec.
same applies here. If you want this then let the kernel drive and
automatic poll of these information.
Regards
Marcel
next prev parent reply other threads:[~2011-07-13 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1310565997-31927-1-git-send-email-y>
2011-07-13 14:06 ` [RFC 2/3] Bluetooth: Implement Read Transmit Power Level command anderson.briglia
2011-07-13 18:13 ` Marcel Holtmann [this message]
2011-07-13 14:06 ` [RFC 3/3] Bluetooth: Implement Management command listener anderson.briglia
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=1310580840.21109.97.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=anderson.briglia@openbossa.org \
--cc=bruna.moreira@openbossa.org \
--cc=linux-bluetooth@vger.kernel.org \
/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