From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Andre Dieb Martins <andre.dieb@signove.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC 1/2] Add Type property to Device
Date: Mon, 11 Apr 2011 13:00:58 -0300 [thread overview]
Message-ID: <20110411160058.GB2195@joana> (raw)
In-Reply-To: <1301510036-17282-1-git-send-email-andre.dieb@signove.com>
* Andre Dieb Martins <andre.dieb@signove.com> [2011-03-30 15:33:55 -0300]:
> ---
> doc/device-api.txt | 4 ++++
> src/device.c | 18 ++++++++++++++++++
> src/device.h | 2 ++
> 3 files changed, 24 insertions(+), 0 deletions(-)
>
> diff --git a/doc/device-api.txt b/doc/device-api.txt
> index d1feb18..a667296 100644
> --- a/doc/device-api.txt
> +++ b/doc/device-api.txt
> @@ -130,6 +130,10 @@ Properties string Address [readonly]
> Proposed icon name according to the freedesktop.org
> icon naming specification.
>
> + string Type [readonly]
> +
> + Device type (BR/EDR, LE, BR/EDR/LE).
> +
> uint32 Class [readonly]
>
> The Bluetooth class of device of the remote device.
> diff --git a/src/device.c b/src/device.c
> index d567952..96683de 100644
> --- a/src/device.c
> +++ b/src/device.c
> @@ -228,6 +228,20 @@ static void device_free(gpointer user_data)
> g_free(device);
> }
>
> +const char *devtype2str(device_type_t type)
> +{
> + switch (type) {
> + case DEVICE_TYPE_BREDR:
> + return "BR/EDR";
> + case DEVICE_TYPE_LE:
> + return "LE";
> + case DEVICE_TYPE_DUALMODE:
> + return "BR/EDR/LE";
I think that use "Dual Mode" is much better here.
--
Gustavo F. Padovan
http://profusion.mobi
next prev parent reply other threads:[~2011-04-11 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 18:33 [RFC 1/2] Add Type property to Device Andre Dieb Martins
2011-03-30 18:33 ` [RFC 2/2] Add type property to Adapter Andre Dieb Martins
2011-03-31 20:44 ` [RFC 1/2] Add Type property to Device Claudio Takahasi
2011-04-11 13:08 ` Elvis Pfutzenreuter
2011-04-11 16:00 ` Gustavo F. Padovan [this message]
2011-04-11 17:18 ` Claudio Takahasi
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=20110411160058.GB2195@joana \
--to=padovan@profusion.mobi \
--cc=andre.dieb@signove.com \
--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