From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] kernel: hci_scodata_packet: hci1 SCO packet for unknown connection handle 0
Date: Tue, 18 Jul 2006 18:03:05 +0200 [thread overview]
Message-ID: <1153238585.21024.2.camel@localhost> (raw)
In-Reply-To: <20060718142827.GP10190@suse.de>
Hi Stefan,
> > > > actually with isco=1 the SCO transfers are still on, but limited to
> > > > 8-bit instead of 16-bit with isoc=2. So if you have isoc=2 it fills up
> > > > your syslog. Can you extract some of these SCO packets with hcidump for
> > > > me.
>
> > > root@strolchi:~# hcidump -i hci1
> > > HCI sniffer - Bluetooth packet analyzer ver 1.29
> > > device: hci1 snap_len: 1028 filter: 0xffffffff
> > > > SCO data: handle 0 dlen 0
> > > > SCO data: handle 0 dlen 0
>
> > > This happens immediately after plugging the thing in, there is no pairing
> > > or any application involved that might trigger this AFAICT.
> >
> > Another RTX based dongle with RTX chip (0400:0807) has already been
> > blacklisted by me. I have no idea, why they can't get this right.
>
> > It would be interesting if this will work with isoc=1 and a 16-bit PCM
> > stream. You should really try some stuff from the btsco package.
>
> I did this and could not get it to work at all, means it did not play any sound
> with btsco and aplay to a Belkin F8T060xHDST headset. I got some "pops" on the
> earpiece when opening the device, but it did not play back anything.
>
> The headset worked with a Belkin F8T013 after applying the SCO MTU patch and
> with a Gigabyte GN-BTD02 out of the box. The SCO MTU patch did not help for
> the Abe dongle.
>
> I guess this piece of silicon is just plain crap :-)
it is the same as the Vivanco one, which I also have a bug report for:
lsusb: Bus 003 Device 004: ID 0400:080a National Semiconductor Corp.
And yes, they are a piece of crap when it comes to ISOC transfers. We
can only mark the SCO support as broken.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-07-18 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 9:42 [Bluez-devel] kernel: hci_scodata_packet: hci1 SCO packet for unknown connection handle 0 Stefan Seyfried
2006-07-11 11:24 ` Marcel Holtmann
2006-07-11 13:39 ` Stefan Seyfried
2006-07-11 13:46 ` Marcel Holtmann
2006-07-11 15:45 ` Stefan Seyfried
2006-07-14 13:54 ` Marcel Holtmann
2006-07-14 15:38 ` Stefan Seyfried
2006-07-18 14:28 ` Stefan Seyfried
2006-07-18 16:03 ` 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=1153238585.21024.2.camel@localhost \
--to=marcel@holtmann.org \
--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