From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] sco link problem
Date: Thu, 24 Nov 2005 05:23:37 +0100 [thread overview]
Message-ID: <1132806217.5982.22.camel@blade> (raw)
In-Reply-To: <000f01c5efcb$c4258540$6201a8c0@hujie>
Hi Luchine,
> I've problem by make SCO link using the dongle with BCM2035 chip.It's seemed
> SCO link up,but NO any of data responsed.:(
> hci_usb.c file, I found some piece like:
> {USB_DEVICE(0x0a5c, 0x200a), .driver_info = HCI_RESET |
> HCI_BROKEN_ISOC }
> it's disabled all of BCM2035 dongle SCO driver with id by 0x0a5c &
> 0x200a,what's idea about this? My dongle matchs this id.
> Is Broadcom makes chip abnormally behavior with 0x0a5c,0x200a ?
last time I check one of these devices, the ISOC transfers were broken
and they were making this device unusable. So I flagged it. Remove the
quirk identify and try if it works.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-11-24 4:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051122195412.F2DBC88BC7@sc8-sf-spam1.sourceforge.net>
2005-11-23 1:18 ` [Bluez-devel] sco link problem lcstudio@gmail
2005-11-24 4:23 ` Marcel Holtmann [this message]
2006-02-02 9:53 [Bluez-devel] SCO " Israel Guío
2006-02-07 11:10 ` 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=1132806217.5982.22.camel@blade \
--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).