From: Marcel Holtmann <marcel@holtmann.org>
To: Simon Vogl <vogl@soft.uni-linz.ac.at>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] sco / csr final notes
Date: Wed, 31 Mar 2004 12:59:34 +0200 [thread overview]
Message-ID: <1080730774.2674.6.camel@pegasus> (raw)
In-Reply-To: <406A9E23.9000406@soft.uni-linz.ac.at>
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
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&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-03-31 10:59 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 [this message]
2004-03-31 11:48 ` Simon Vogl
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=1080730774.2674.6.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=vogl@soft.uni-linz.ac.at \
/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