From: Stefan Behlert <behlert@suse.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] hcitool bug
Date: Wed, 23 Feb 2005 16:48:58 +0100 [thread overview]
Message-ID: <20050223154857.GE5777@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0502231536460.9757@sphinx.mythic-beasts.com>
On Feb 23, 05 15:41:45 +0000, Pete Stevens wrote:
> Hi,
>
> This confuses me, can anyone explain why I get this?
>
> [root@pstevens bluetooth-pc-tag]# hcitool dev
> Devices:
> hci0 00:0C:76:47:6A:94
>
> [root@pstevens bluetooth-pc-tag]# hcitool -i 00:0C:76:47:6A:94 info
> 00:0E:6D:13:D8:74
> Requesting information ...
> Get connection info failed: No such file or directory
>
> [root@pstevens bluetooth-pc-tag]# hcitool info 00:0E:6D:13:D8:74
> Requesting information ...
> BD Address: 00:0E:6D:13:D8:74
Nice. With version 2.15 this fails with me. Do you have more than one
Bluetooth dongle in your computer?
[...]
I think it has to fail, because '-i <dev>' explicitly says "send it out
using this interface" and only affects remote devices. I don't think you
should be able to ask local devices for information in this way. But I may
be wrong.
ciao,
Stefan
--
Stefan Behlert
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-02-23 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 15:41 [Bluez-users] hcitool bug Pete Stevens
2005-02-23 15:48 ` Stefan Behlert [this message]
2005-02-23 16:04 ` Pete Stevens
2005-02-23 16:14 ` Stefan Behlert
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=20050223154857.GE5777@suse.de \
--to=behlert@suse.de \
--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