All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom K <tomk@runbox.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcid fails to start after upgrade to	bluez-libs/bluez-utils 3.1 (Continued)
Date: Tue, 04 Jul 2006 19:11:18 +0100	[thread overview]
Message-ID: <44AAAF46.7060309@runbox.com> (raw)
In-Reply-To: <e1effdeb0607040642j3c3e0a34l67565401acb2f318@mail.gmail.com>

Claudio Takahasi wrote:
> Hi Tom,
>
> I was not able to reproduce the problem that you described. I found
> some problems with dongles that doesn't support set the inquiry mode,
> but I never noticed "Connection timed out".
> Could you send the hcidump?
>
> BR,
> Claudio.
>   
Thanks for your continued interest, Claudio.

I'm not able to send a hcidump yet, because I need to rebuild hcidump 
against bluez-libs 3.1, and I'm getting an error. Not my day, it seems. :(

I'll send the dump file asap.

Tom.

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-07-04 18:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03 21:55 [Bluez-devel] hcid fails to start after upgrade to bluez-libs/bluez-utils 3.1 (Continued) Tom K
2006-07-04 13:42 ` Claudio Takahasi
2006-07-04 18:11   ` Tom K [this message]
2006-07-04 21:38   ` Tom K
2006-07-07 18:17     ` Claudio Takahasi
2006-07-07 20:48       ` Tom K

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=44AAAF46.7060309@runbox.com \
    --to=tomk@runbox.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 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.