From: Marcel Holtmann <marcel@holtmann.org>
To: Daryl Van Vorst <daryl@wideray.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Missing data in ACL packets from CSR chip
Date: Fri, 13 Feb 2004 18:44:37 +0100 [thread overview]
Message-ID: <1076694277.2671.184.camel@pegasus> (raw)
In-Reply-To: <000501c3f257$c4649af0$1a01010a@baked>
Hi Daryl,
> It looks like a UART problem to me too, but it's probably not on my side
> because both the sniffer and the host saw the same error.
is it reproduceable when you use a Casira?
> I would like to try BCSP. Are there tools available to put the module in
> BCSP mode?
The pskey tool can do this, but at your own risc. Otherwise you must
write it by yourself, because I don't provide any source code that is
able to modify the PS.
Regards
Marcel
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-02-13 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 17:53 [Bluez-devel] Missing data in ACL packets from CSR chip Daryl Van Vorst
2004-02-13 16:00 ` Marcel Holtmann
2004-02-13 17:35 ` Daryl Van Vorst
2004-02-13 17:44 ` Marcel Holtmann [this message]
2004-02-13 18:53 ` Daryl Van Vorst
2004-02-13 19:22 ` Marcel Holtmann
2004-02-13 19:42 ` Daryl Van Vorst
2004-02-13 20:04 ` Marcel Holtmann
2004-02-13 19:11 ` Daryl Van Vorst
2004-02-13 19:40 ` Marcel Holtmann
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=1076694277.2671.184.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=daryl@wideray.com \
/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.