From: Simon Vogl <vogl@soft.uni-linz.ac.at>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] zeevo module and h4 implementation
Date: Wed, 20 Jul 2005 09:31:32 +0200 [thread overview]
Message-ID: <42DDFDD4.7050204@soft.uni-linz.ac.at> (raw)
Hi,
I have a Zeevo module here with a firmware that is not fully compliant
to the BT specification, as it seems: The module sends hci command packet=
s(!)
over the uart, which of course confuses the stack, and blocks further com=
munication.
Details: It seems like the module has the PIN stored on-device and sends
the link_key_failed command to the host as an indication for an unsuccess=
ful
pairing attempt.
Besides me looking for a different firmware, are there any objections to =
extend
the h4 module with command packet reading support? And what should I do w=
ith them
afterwards besides ignoring - would hcid be interested in this informatio=
n, or
a d-bus interface?
cheers
Simon
--=20
_______________________________________________________________________
Dr. Simon Vogl
ARC Seibersdorf research GmbH
Research Studios Austria, Studio Pervasive Computing Applications
Altenberger Stra=C3=9Fe 69, A-4040 Linz, Austria
Tel: +43 732 2468-8517, Fax: +43 732 2468-8426
mailto: simon.vogl@researchstudio.at
-------------------------------------------------------
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
reply other threads:[~2005-07-20 7:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42DDFDD4.7050204@soft.uni-linz.ac.at \
--to=vogl@soft.uni-linz.ac.at \
--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