From: Michael Frey <mfrey@pepper.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hcitool scan problems....
Date: Mon, 29 Nov 2004 10:42:05 -0500 [thread overview]
Message-ID: <38C6CE2C-421D-11D9-ADA9-00039390D626@pepper.com> (raw)
In-Reply-To: <1101332931.7538.8.camel@pegasus>
Thanks for the help. The --scan helps.
I am using kernel 2.4.20
Michael
On Nov 24, 2004, at 4:48 PM, Marcel Holtmann wrote:
> Hi Michael,
>
>> I am currently seeing strange behavior while doing "scans".
>>
>> It takes me several scans to see the devices I have in range. Also,
>> sometimes when I issue "hcitool scan" it does not even scan. It just
>> stops immediately after printing "Scanning ...".
>
> what kernel version is this? Try it with --flush.
>
> 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://productguide.itmanagersjournal.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-11-29 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 19:43 [Bluez-devel] hcitool scan problems Michael Frey
2004-11-24 21:48 ` Marcel Holtmann
2004-11-29 15:42 ` Michael Frey [this message]
2004-11-25 8:29 ` Diego Liziero
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=38C6CE2C-421D-11D9-ADA9-00039390D626@pepper.com \
--to=mfrey@pepper.com \
--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