public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Lars Grunewaldt <lgw@dark-reality.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] "comlicated" setup - known issues for	hid	and	SCO?
Date: Tue, 10 Aug 2004 14:49:02 +0200	[thread overview]
Message-ID: <1092142142.4564.101.camel@pegasus> (raw)
In-Reply-To: <4118BEBE.2010505@dark-reality.de>

Hi Lars,

> | so both devices are in the same piconet. There should be no problem, but
> | from my position I can't tell you anything more.
> 
> I think this message might have something to do with the problem:
> 
> hci_scodata_packet: hci0 SCO packet for unknown connection handle 44
> 
> My main problem does not even seem to be connected to the mouse, because
> it also happens when the mouse is far far away and not connected.

this can also happen when the connection is already closed and then some
data packets arrive. Maybe it is a chip problem, because as I know CSR
never official supported the SCO over HCI/USB transport. Or the USB host
controller has problems with the ISOC transfers.

> In about 50% of SCO connections the sound coming from the headset is
> totally garbage (not the sound send TO the headset!); I think this might
> be connected to another report here on the list when someone mentioned
> he had to cut the first byte when recording audio from an SCO channel
> (because I'm using 16bit right now, too). This never happend with 8bit
> transmissions over SCO.

This can be that problem. We need an algorithm in the hci_usb driver to
detect this.

Regards

Marcel




-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2004-08-10 12:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 16:40 [Bluez-devel] "comlicated" setup - known issues for hid and SCO? Lars Grunewaldt
2004-08-09 17:13 ` Marcel Holtmann
2004-08-09 17:25   ` Lars Grunewaldt
2004-08-09 17:44     ` Marcel Holtmann
     [not found]       ` <4117BA71.5000800@dark-reality.de>
2004-08-09 22:29         ` Marcel Holtmann
2004-08-10  0:03           ` Lars Grunewaldt
2004-08-10 12:51             ` Marcel Holtmann
2004-08-10 12:25           ` Lars Grunewaldt
2004-08-10 12:49             ` Marcel Holtmann [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=1092142142.4564.101.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=lgw@dark-reality.de \
    /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