From: Pierre-Yves Paulus <py@idlum.be>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluez and dbus - how to turn on discovery?
Date: Tue, 16 Jan 2007 15:04:41 +0100 [thread overview]
Message-ID: <45ACDB79.1060002@idlum.be> (raw)
In-Reply-To: <200701160828.37391.akohlsmith-bluez@benshaw.com>
Hello Andrew,
> The latest bluez (3.8) does return a grammatically correct XML response now
> (empty node). I must ask again though -- how does one see which
> methods/properties bluez makes available through dbus? How does one find out
> which bluetooth interfaces (hci0, hci1, etc.) are available?
For now, have a look at
http://bluez.cvs.sourceforge.net/bluez/utils/hcid/dbus-api.txt?view=markup
You will find that there is a ListAdapters() method in the Manager
hierarchy which will let you list current adapters, along the list of
all other methods.
Regards,
Pierre-Yves
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-01-16 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 13:02 [Bluez-users] bluez and dbus - how to turn on discovery? Andrew Kohlsmith
2007-01-15 13:24 ` Marcel Holtmann
2007-01-15 15:33 ` Andrew Kohlsmith
2007-01-16 13:02 ` Ulisses Furquim
2007-01-16 13:28 ` Andrew Kohlsmith
2007-01-16 13:59 ` Marcel Holtmann
2007-01-16 14:04 ` Pierre-Yves Paulus [this message]
2007-01-15 16:08 ` Andrew Kohlsmith
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=45ACDB79.1060002@idlum.be \
--to=py@idlum.be \
--cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox