From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SCO stuck on a Netgear WGT634U (mips)
Date: Mon, 06 Mar 2006 12:10:16 -0700 [thread overview]
Message-ID: <440C8918.7050304@xmission.com> (raw)
In-Reply-To: <20060306090140.e1e882d5.henryk@ploetzli.ch>
Henryk
>>I'm using a Energic BT-001 headset (bluetooth 1.1, Motorale chipset)
>>and had a terrible distortion as well. After having disabled
>>automatic endianness fixup in the snd_bt_sco kernel module (line 32
>>btsco.c:
>>#undef AUTO_FIXUP_BYTESHIFT) it works flawlessly :).
>
> Yeah, I found that part of the code suspicious too.
I was hoping to take it out when we fixed the underlying problem, but I
can do it sooner if it causes new problems.
For some reason, it appears that damaged sco frames are not tossed out.
They are still accepted and processed. A missing byte in the middle
mixes up byte order and turns the stream into static.
Brad
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-03-06 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 0:14 [Bluez-devel] SCO stuck on a Netgear WGT634U (mips) Henryk Plötz
2006-03-03 4:27 ` Brad Midgley
2006-03-04 1:41 ` Henryk Plötz
2006-03-04 7:47 ` Henryk Plötz
2006-03-06 7:43 ` Pieter Poorthuis
2006-03-06 8:01 ` Henryk Plötz
2006-03-06 19:10 ` Brad Midgley [this message]
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=440C8918.7050304@xmission.com \
--to=bmidgley@xmission.com \
--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;
as well as URLs for NNTP newsgroup(s).