linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Raffael Stocker <r.stocker@mnet-mail.de>
To: linux-bluetooth@vger.kernel.org
Subject: BlueZ/D-Bus: Interpretation of service classes and UUIDs
Date: Sat, 09 Nov 2019 01:50:59 +0100	[thread overview]
Message-ID: <87a795vpn0.fsf@mnet-mail.de> (raw)

I have recently written a bluetooth package for Emacs using the BlueZ
D-Bus interface.  For the interpretation of device and service classes,
and other UUIDs, I hand-scraped the bluetooth.com website, although much
of the information seems to be available somewhere in BlueZ, at least
on a source code/C library interface level, if not on D-Bus.

Have I overlooked any way to query BlueZ for a human-readable
interpretation of UUIDs etc. over D-Bus?

If not, could such an interface be implemented in BlueZ?  I think it
would be very useful if applications building on BlueZ could all offer
the same textual representation of UUIDs without each replicating the
same data over and over again.

Regards,
        Raffael

                 reply	other threads:[~2019-11-09  0:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87a795vpn0.fsf@mnet-mail.de \
    --to=r.stocker@mnet-mail.de \
    --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;
as well as URLs for NNTP newsgroup(s).