From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hcitool scan question
Date: Fri, 11 Feb 2005 13:03:12 +0100 [thread overview]
Message-ID: <1108123392.18099.16.camel@pegasus> (raw)
In-Reply-To: <Pine.GSO.4.60.0502110314380.12691@columbia.cs.ubc.ca>
Hi Jack,
> I am running hciemu. hciconfig shows VHCI devices up and running and I can
> l2ping the devices, but when I do hcitool scan I get the following:
>
> # hcitool scan
> Scanning ...
> Inquiry failed: Connection timed out
>
> hcidump shows the following:
>
> # hcidump -i hci0 -V
> HCI sniffer - Bluetooth packet analyzer ver 1.17
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Inquiry (0x01|0x0001) plen 5
> > HCI Event: Command Complete (0x0e) plen 4
> Inquiry (0x01|0x0001) ncmd 1
>
> Could you give me some ideas about what I should do to make the scan
> working? Can I achieve that with VHCI devices? hcidump shows hci0 is doing
> the job, but the scan doesn't show it.
the inquiry is not supported by the hciemu. Get yourself a pair of real
Bluetooth devices.
Regards
Marcel
-------------------------------------------------------
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-11 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050211111140.64497886BC@sc8-sf-spam1.sourceforge.net>
2005-02-11 11:35 ` [Bluez-users] hcitool scan question Jack Jia
2005-02-11 12:03 ` Marcel Holtmann [this message]
2005-02-12 14:52 ` [Bluez-users] pand and sdp packages question Jack Jia
2005-02-12 14:58 ` Michal Semler
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=1108123392.18099.16.camel@pegasus \
--to=marcel@holtmann.org \
--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