All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Vogl <vogl@soft.uni-linz.ac.at>
To: Steven Singer <steven.singer@csr.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] sco / csr final notes
Date: Wed, 31 Mar 2004 17:13:43 +0200	[thread overview]
Message-ID: <406AE027.7030000@soft.uni-linz.ac.at> (raw)
In-Reply-To: 406ADF3E.4020502@csr.com



Steven Singer wrote:
> Simon Vogl wrote:
> 
>>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.
> 
> 
> Is the problem that the link spontaneously changes from correct to noisy
> in the middle of a link, or is it that when you start up a link it's
> either OK for the durection of the link, or noisy for the duration of
> the link and then when you tear it down and start a fresh link, the next
> one is, independently, correct our noisy?
> 
> If it's the latter case, is the first link after a full reset (BCCMD
> reset or power cycle - not merely an HCI reset) ever noisy?
> 
the latter is the case. Whenever a fresh sco link starts, I have a 50% chance of
getting the wrong byte order..

I still have to try how it reacts after a cold reset, as I dont have a developer kit -
I just downloaded the bccmd spec, and I need to write a small piece of software to
transmit this command.... But I will tell you as soon as I know.

> 
>>Marcel, do you I can bug with this at csr?
> 
> 
> You should use the CSR public newsgroups (follow the links from the CSR
> web site), though, in practice, making enough noise on this mailing list
> will eventually attract the attention from someone at CSR (there are
> several people here who subscribe).

I have already, thanks, and will beat the bush shortly. I have to get several other
flaws straight first - I am over an important project deadline already, but that's
a different story :(

Simon

> 
> 	- Steven


-- 
_______________________________________________________________________
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/

  reply	other threads:[~2004-03-31 15:13 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
2004-03-31 15:09     ` Steven Singer
2004-03-31 15:13       ` Simon Vogl [this message]
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=406AE027.7030000@soft.uni-linz.ac.at \
    --to=vogl@soft.uni-linz.ac.at \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    --cc=steven.singer@csr.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.