From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Broadcom 2035 SCO question
Date: Tue, 11 Jul 2006 21:04:30 +0200 [thread overview]
Message-ID: <1152644670.15028.42.camel@localhost> (raw)
In-Reply-To: <44B3F51E.1070009@free.fr>
Hi Fabien,
> I recently purchased a class 1 "sweex" bluetooth USB dongle. It has a
> broadcom bcm2035
> usb chip( idVendor = 0x0a5c, idProduct = 0x200a). It advertises SCO
> mtu=16, sco packets = 0.
> I tryed to use it with SCO, no luck.(I wasn't surprised by that, given
> sco packets = 0) Then i looked at hci usb driver and found it was in the
> blacklist, with HCI_BROKEN_ISOC.
>
> I then removed it from this list, forced SCO mtu to 48 and packets
> number to 8 by hacking hci_event.c... and guess what, it works !!
>
> So my question is: shouldn't this product marked as HCI_WRONG_SCO_MTU
> mtu instead of HCI_BROKEN_ISOC?
is it enough to change HCI_BROKEN_ISOC into HCI_WRONG_SCO_MTU to make
this work. If yes, then I am happy to submit a patch.
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
next prev parent reply other threads:[~2006-07-11 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 18:59 [Bluez-devel] Broadcom 2035 SCO question Fabien Chevalier
2006-07-11 19:04 ` Marcel Holtmann [this message]
2006-07-17 7:27 ` Fabien Chevalier
2006-07-18 17:12 ` 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=1152644670.15028.42.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 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.