From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Possible Patch: list paired devices
Date: Tue, 21 Feb 2006 12:37:37 +0100 [thread overview]
Message-ID: <1140521857.10008.12.camel@localhost> (raw)
In-Reply-To: <200602211837.00121.denis.kenzior@trolltech.com>
Hi Denis,
> I noticed that there is no way to list paired devices from hcitool/hciconfig,
> at least I couldn't find a way to do so. Here is a proposed patch to
> hcitool which will show a list of paired devices.
>
> I'm not sure if this is the right solution, since it requires hcitool to be
> run with effective permissions to access the linkkeys file (e.g. root on my
> system). If there is a better way let me know.
you can use standard tools like grep and awk to get this information and
since we have the limitation with the root access, I am not going to add
this. Use the new D-Bus interface to retrieve this information.
> Also, will the patch for 128 bit UUID searching in sdptool get merged into
> CVS, or did I mess something up again?
The patch is in my todo stack, but I haven't looked at it.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-02-21 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 8:36 [Bluez-devel] Possible Patch: list paired devices Denis KENZIOR
2006-02-21 11:37 ` Marcel Holtmann [this message]
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=1140521857.10008.12.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@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;
as well as URLs for NNTP newsgroup(s).