From: Johan Hedin <sua@home.se>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] HCI reset problem
Date: Sun, 3 Jul 2005 18:09:41 +0200 [thread overview]
Message-ID: <200507031809.41745.sua@home.se> (raw)
In-Reply-To: <1120404389.10273.56.camel@pegasus>
On Sunday 03 July 2005 17.26, Marcel Holtmann wrote:
> Hi Johan,
>
> > This is what I see when the reset happens (and yes, there are two output
> > lines from hcidump):
> >
> > [root@x300 ~]# hcidump -t -X -V
> > 2005-07-02 14:09:10.093053 < HCI Command: Reset (0x03|0x0003) plen 0
> > 2005-07-02 14:09:10.093053 < HCI Command: Reset (0x03|0x0003) plen 0
>
> this is a bug that I introduced with bluez-hcidump-1.22 release. I did
> some type changes and was a little bit too lazy to check their users. In
> this case you should only see one HCI_Reset and then hcidump should
> terminate, because the device is gone. A fix for it is in the CVS now.
Ok, I almost suspected this because hcidump behaved as you describe in a
previous release I used.
One problem less to be sleepless over then :-)
/ Johan
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-07-03 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 17:12 [Bluez-devel] HCI reset problem Johan Hedin
2005-07-02 21:15 ` Ronny L Nilsson
2005-07-03 14:53 ` Johan Hedin
2005-07-06 0:10 ` Ronny L Nilsson
2005-07-06 20:28 ` Johan Hedin
2005-07-03 15:26 ` Marcel Holtmann
2005-07-03 16:09 ` Johan Hedin [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=200507031809.41745.sua@home.se \
--to=sua@home.se \
--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