From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Nokia 7610 file transfer to computer
Date: Thu, 09 Dec 2004 20:32:00 +0100 [thread overview]
Message-ID: <1102620720.9988.241.camel@pegasus> (raw)
In-Reply-To: <1102611131.7584.1.camel@nephlim.homenet>
Hi Stefan,
> > Actually I meant its chip information (use "hcitool info ..."), because
> > we need to figure out which Bluetooth chip is the bad one that makes
> > sending out the ACL data packets before the connection complete event. I
> > believe your dongle is the problematic part and if you exchange it with
> > a CSR based one all troubles will be gone.
>
> That was it! :)
I am still interested in the "hcitool info" output.
> With a new BT dongle it now works fine! So much trouble and such a easy
> solution... :/
The more bad dongles or better Bluetooth chips/modules I see on the
market, I think we really need some qualification testing for HCI.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-12-09 19:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 1:02 [Bluez-users] Nokia 7610 file transfer to computer Stefan Torkel
2004-12-07 7:55 ` Marcel Holtmann
2004-12-07 17:00 ` Stefan Torkel
2004-12-08 3:56 ` Marcel Holtmann
2004-12-09 0:44 ` Stefan Torkel
2004-12-09 7:24 ` Marcel Holtmann
2004-12-09 11:11 ` Stefan Torkel
2004-12-09 11:24 ` Marcel Holtmann
2004-12-09 16:52 ` Stefan Torkel
2004-12-09 19:32 ` Marcel Holtmann [this message]
2004-12-09 21:06 ` Stefan Torkel
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=1102620720.9988.241.camel@pegasus \
--to=marcel@holtmann.org \
--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 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.