From: Johan Hedin <sua@home.se>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] HCI reset problem
References: <200507021912.29173.sua@home.se> <1120404389.10273.56.camel@pegasus>
In-Reply-To: <1120404389.10273.56.camel@pegasus>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Message-Id: <200507031809.41745.sua@home.se>
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Reply-To: bluez-devel@lists.sourceforge.net
Date: Sun, 3 Jul 2005 18:09:41 +0200

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