From: Simon Vogl <vogl@soft.uni-linz.ac.at>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] sco / csr final notes
Date: Wed, 31 Mar 2004 13:48:15 +0200 [thread overview]
Message-ID: <406AAFFF.6040504@soft.uni-linz.ac.at> (raw)
In-Reply-To: 1080730774.2674.6.camel@pegasus
oh, sorry: well, after trying for weeks, I see always the same behavior of
the sco data: after a connect of the sco channel, the data is either byte-swapped
or offset by one byte, but no indication in any header etc. can be found why
this is the case.
The original assumption that there might be packets with a byte (or more)
missing has not turned out to be right (could not find an indication of this).
Anyway, as a workaround, I have implemented a small signal analysis function that
tests, in short, if the incoming signal is gaussian or even distributed (the latter
is an indication for a byte swap) - upon which I adapt the output accordingly.
(the code is at http://www.soft.uni-linz.ac.at/_wiki/tiki-index.php?page=ProjectBluezHandsfree)
Marcel, do you I can bug with this at csr?
Simon
Simon
Marcel Holtmann wrote:
> Hi Simon,
>
>
>>well now I have a heuristic that works most of the time. Looking at the
>>transmitted data, I wonder if there could be a big endian/little endian
>>switch that is toggled randomly in the firmware for the 16bit sco data.
>>
>>Is there a lucky person with a developer kit out there who is able
>>to confirm this?
>
>
> please remind us about what your are talking, because it seems that at
> least I forgot it. If you think you found a bug and you are able to
> reproduce it, you should make a detailed description, so the CSR guys
> can fix it.
>
> Regards
>
> Marcel
>
--
_______________________________________________________________________
Dr. Simon Vogl
Institut für Pervasive Computing, Johannes Kepler Universität Linz
Altenberger Straße 69, A-4040 Linz, Austria
Tel: +43 732 2468-8517, Fax: +43 732 2468-8426
mailto: vogl@soft.uni-linz.ac.at, http://www.soft.uni-linz.ac.at/
next prev parent reply other threads:[~2004-03-31 11:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 10:32 [Bluez-devel] sco / csr final notes Simon Vogl
2004-03-31 10:59 ` Marcel Holtmann
2004-03-31 11:48 ` Simon Vogl [this message]
2004-03-31 15:09 ` Steven Singer
2004-03-31 15:13 ` Simon Vogl
2004-03-31 16:26 ` Steven Singer
2004-03-31 19:10 ` James Courtier-Dutton
2004-03-31 19:36 ` Marcel Holtmann
2004-03-31 20:18 ` James Courtier-Dutton
2004-03-31 20:29 ` 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=406AAFFF.6040504@soft.uni-linz.ac.at \
--to=vogl@soft.uni-linz.ac.at \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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.