linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 14 Jul 2006 15:54:38 +0200	[thread overview]
Message-ID: <1152885278.25660.27.camel@localhost> (raw)
In-Reply-To: <20060711154501.GE13809@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.
> 
> ok, it looks like this (hoping that i invoked hcidump correctly, i am still
> learning this bluetooth thingy :-):

the preferred way would be "hcidump -i hci1 -X -V" to have full decoding
support, but for SCO this doesn't really matter.

> 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
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
> > 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.
 
> > Any chance of a name or identification of this dongle?
> 
> It is an Abe UB20S, http://www.abe-hk.com/english/products/ub12-22/ub12-22.htm
> The FCC ID is NV6-CS8024.
> It is sold e.g. by conrad.com in germany and pretty cheap (around 10 Euro),
> and it is pretty small (this is why i bought it, i can leave it plugged in
> when putting the notebook into the bag :-)

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.

Regards

Marcel




-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-07-14 13:54 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 [this message]
2006-07-14 15:38           ` Stefan Seyfried
2006-07-18 14:28           ` Stefan Seyfried
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=1152885278.25660.27.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;
as well as URLs for NNTP newsgroup(s).