Linux bluetooth development
 help / color / mirror / Atom feed
From: Stefan Magdalinski <smagdali@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Bluez + 6630 rfcomm was working, suddenly died.
Date: Thu, 21 Apr 2005 12:58:33 +0100	[thread overview]
Message-ID: <e9a6e82b0504210458a0ba170@mail.gmail.com> (raw)
In-Reply-To: <1114013959.2469.189.camel@pegasus>

On 4/20/05, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Stefan,
>=20
> > looks like the version of hcidump (1.1.2) is too old for -V, but
> > here's what I get for -X
>=20
> then install a new one, because I am not going to decode the HCI parts
> any time again by hand.

fair enough.

so I rebuilt everything from the latest sources, was running 'hcidump
-X -V', and when I tried to connect this time, it was working again,
and I can pair the devices ok.

so thanks for your help. I'll see how it goes over the next few days.

>=20
> > is there a repository I should be adding to sources.list to pull a newe=
r one?
>=20
> The source is available.


-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2005-04-21 11:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 14:42 [Bluez-users] Bluez + 6630 rfcomm was working, suddenly died Stefan Magdalinski
2005-04-20 14:51 ` Marcel Holtmann
2005-04-20 16:15   ` Stefan Magdalinski
2005-04-20 16:19     ` Marcel Holtmann
2005-04-21 11:58       ` Stefan Magdalinski [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=e9a6e82b0504210458a0ba170@mail.gmail.com \
    --to=smagdali@gmail.com \
    --cc=bluez-users@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