public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] "hci_scodata_packet: hci0 SCO packet for unknown	connection handle 92" for 1131:1001 (issc usb dongle)
Date: Mon, 03 Dec 2007 17:31:13 +0100	[thread overview]
Message-ID: <1196699473.12292.122.camel@violet> (raw)
In-Reply-To: <b88f52540712010301t154c17f2xa5629b5b9fb335d3@mail.gmail.com>

Hi,

> I'm getting the usual "syslog flooded" problem with my usb dongle, id 1131:1001.
> 
> Just for reference, the problem (and other very similar problems) are
> mentioned here:
> http://qa.mandriva.com/show_bug.cgi?id=30638
> http://bugzilla.kernel.org/show_bug.cgi?id=6833
> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/39414
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444603
> 
> 
> I've tried applying the patch mentioned here:
> http://permalink.gmane.org/gmane.linux.bluez.devel/13721
> and the patch appears to fix the problem (and my bluetooth dongle
> seems to continue to work).
> 
> 
> Could you please push this patch upstream? (I've checked
> http://git.kernel.org/?p=linux/kernel/git/holtmann/bluetooth-2.6.git;a=blob_plain;f=drivers/bluetooth/hci_usb.c;hb=HEAD
> and the patch does not yet appear to be included - I may be looking in
> the wrong place, of course!)

it has already been pushed into the upstream kernel.

> One other question - does this quirk make my usb bluetooth dongle
> "inferior" in some way? What do I lose if I don't have "ISOC
> transfers"? (this way, I can work out if I should buy a different
> dongle).

Yes. It will no longer support SCO data. So no headset support will be
possible.

Regards

Marcel



-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-12-03 16:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-01 11:01 [Bluez-devel] "hci_scodata_packet: hci0 SCO packet for unknown connection handle 92" for 1131:1001 (issc usb dongle) j t
2007-12-03 16:31 ` 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=1196699473.12292.122.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sf.net \
    --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