All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
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 16:28:27 +0200	[thread overview]
Message-ID: <20060718142827.GP10190@suse.de> (raw)
In-Reply-To: <1152885278.25660.27.camel@localhost>

Hi,

On Fri, Jul 14, 2006 at 03:54:38PM +0200, Marcel Holtmann wrote:
> Hi Stefan,
> =

> > > actually with isco=3D1 the SCO transfers are still on, but limited to
> > > 8-bit instead of 16-bit with isoc=3D2. So if you have isoc=3D2 it fil=
ls up
> > > your syslog. Can you extract some of these SCO packets with hcidump f=
or
> > > 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 pairi=
ng
> > 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=3D1 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 s=
ound
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 :-)

Details for your blacklisting pleasure:
cf51:~ # lsusb -s 1:19
Bus 001 Device 019: ID 0400:080a National Semiconductor Corp.
cf51:~ # hciconfig -a
hci0:   Type: USB
        BD Address: 00:0C:78:31:11:0A ACL MTU: 339:4 SCO MTU: 64:9
        UP RUNNING PSCAN ISCAN
        RX bytes:1108 acl:0 sco:0 events:63 errors:0
        TX bytes:348 acl:0 sco:0 commands:24 errors:0
        Features: 0xff 0xff 0x81 0x00 0x18 0x18 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'BlueZ cf51 (0)'
        Class: 0x100100
        Service Classes: Object Transfer
        Device Class: Computer, Uncategorized
        HCI Ver: 1.2 (0x2) HCI Rev: 0x222 LMP Ver: 1.2 (0x2) LMP Subver: 0x=
222
        Manufacturer: RTX Telecom A/S (21)
-- =

Stefan Seyfried                  \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices      \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, N=FCrnberg \                    -- Leonard Cohen

-------------------------------------------------------------------------
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=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2006-07-18 14:28 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 [this message]
2006-07-18 16:03             ` 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=20060718142827.GP10190@suse.de \
    --to=seife@suse.de \
    --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 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.