All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Sjoerd Simons <sjoerd@spring.luon.net>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] btaddr <-> name bug ?
Date: Wed, 30 Jun 2004 23:18:24 +0200	[thread overview]
Message-ID: <1088630304.4540.188.camel@pegasus> (raw)
In-Reply-To: <20040630190206.GB26352@spring.luon.net>

Hi Sjoerd,

>   Doing hcitool scan a few times gives some weird output:
> 
> $ hcitool scan
> Scanning ...
>         00:0D:93:08:60:89       familiar (0)
>         00:02:C7:0B:97:F9       spring-0
> $ hcitool scan
> Scanning ...
>         00:0D:93:08:60:89       spring-0
>         00:02:C7:0B:97:F9       familiar (0)
> $ hcitool scan
> Scanning ...
>         00:0D:93:08:60:89       spring-0
>         00:02:C7:0B:97:F9       familiar (0)
> $ hcitool scan
> Scanning ...
>         00:0D:93:08:60:89       familiar (0)
>         00:02:C7:0B:97:F9       spring-0
> 
> The second and third run provide the right information, the first and last are 
> wrong.

provide us with the output of "hcidump -x" while you are running
"hcitool scan".

Regards

Marcel




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-06-30 21:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30 19:02 [Bluez-devel] btaddr <-> name bug ? Sjoerd Simons
2004-06-30 21:18 ` Marcel Holtmann [this message]
2004-06-30 21:30   ` Sjoerd Simons

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=1088630304.4540.188.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=sjoerd@spring.luon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.