From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Broadcom 2035 SCO question
Date: Tue, 18 Jul 2006 19:12:03 +0200 [thread overview]
Message-ID: <1153242723.21024.15.camel@localhost> (raw)
In-Reply-To: <44BB3BFB.80104@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.
> >
>
> Yes. It is not perfect (i have some noise sometimes at startup), but it
> is enough to make it work.
>
> Please find attached one-line patch for this.
a patch for this is in my tree now.
Regards
Marcel
-------------------------------------------------------------------------
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=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-07-18 17:12 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
2006-07-17 7:27 ` Fabien Chevalier
2006-07-18 17:12 ` 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=1153242723.21024.15.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).