From: Szymon Janc <szymon.janc@codecoup.pl>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC 4/4] client: Print LEAddress type in show and info commands
Date: Mon, 11 Dec 2017 13:40:25 +0100 [thread overview]
Message-ID: <3027942.EkYWvo1UAH@ix> (raw)
In-Reply-To: <CABBYNZK+5JGmazDyGM771=RZhkYKbnDMFupZWk+23k4u6z06LQ@mail.gmail.com>
Hi Luiz,
On Monday, 11 December 2017 13:10:28 CET Luiz Augusto von Dentz wrote:
> Hi Szymon,
>
> On Mon, Dec 11, 2017 at 8:38 AM, Szymon Janc <szymon.janc@codecoup.pl>
wrote:
> > ---
> >
> > client/main.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/client/main.c b/client/main.c
> > index f3369e89a..a1d941e30 100644
> > --- a/client/main.c
> > +++ b/client/main.c
> > @@ -872,6 +872,7 @@ static void cmd_show(int argc, char *argv[])
> >
> > print_property(proxy, "Powered");
> > print_property(proxy, "Discoverable");
> > print_property(proxy, "Pairable");
> >
> > + print_property(proxy, "LEAddressType");
> >
> > print_uuids(proxy);
> > print_property(proxy, "Modalias");
> > print_property(proxy, "Discovering");
> >
> > @@ -1447,6 +1448,7 @@ static void cmd_info(int argc, char *argv[])
> >
> > print_property(proxy, "Blocked");
> > print_property(proxy, "Connected");
> > print_property(proxy, "LegacyPairing");
> >
> > + print_property(proxy, "LEAddressType");
> >
> > print_uuids(proxy);
> > print_property(proxy, "Modalias");
> > print_property(proxy, "ManufacturerData");
> >
> > --
> > 2.14.3
>
> Another alternative to adding the LE specific type would be to add it
> as Manufacturer string so we can add the information of OUI if public
> or add the information of "Static Random", "Resolvable Random", etc.
I'd keep it simple - this should simply match to address type that needs to be
passed when connecting L2CAP socket.
--
pozdrawiam
Szymon Janc
next prev parent reply other threads:[~2017-12-11 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 10:38 [RFC 1/4] Add LEAddressType property for Adapter1 and Device1 interfaces Szymon Janc
2017-12-11 10:38 ` [RFC 2/4] adapter: Add support for LEAddressType property Szymon Janc
2017-12-11 10:38 ` [RFC 3/4] device: " Szymon Janc
2017-12-11 10:38 ` [RFC 4/4] client: Print LEAddress type in show and info commands Szymon Janc
2017-12-11 12:10 ` Luiz Augusto von Dentz
2017-12-11 12:40 ` Szymon Janc [this message]
2017-12-13 8:50 ` Marcel Holtmann
2017-12-11 11:59 ` [RFC 1/4] Add LEAddressType property for Adapter1 and Device1 interfaces Luiz Augusto von Dentz
2017-12-11 12:40 ` Szymon Janc
2017-12-13 8:47 ` Marcel Holtmann
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=3027942.EkYWvo1UAH@ix \
--to=szymon.janc@codecoup.pl \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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