From: Chase Douglas <cndougla@purdue.edu>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: Developing Broadcom driver support
Date: Sun, 12 Feb 2006 19:12:47 -0500 [thread overview]
Message-ID: <43EFCEFF.60707@purdue.edu> (raw)
In-Reply-To: <495ce9180602121500i5cb97395o@mail.gmail.com>
I have an iogear gb211, which has a broadcom chipset.
localhost chase # hciconfig -a
hci0: Type: USB
BD Address: 00:02:72:C3:C5:2E ACL MTU: 377:10 SCO MTU: 16:8
UP RUNNING PSCAN ISCAN
RX bytes:14392 acl:25 sco:0 events:799 errors:0
TX bytes:4813 acl:18 sco:0 commands:752 errors:0
Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ (0)'
Class: 0xff0408
Service Classes: Positioning, Networking, Rendering, Capturing
Device Class: Audio/Video, Hands-free
HCI Ver: 1.2 (0x2) HCI Rev: 0x14 LMP Ver: 1.2 (0x2) LMP Subver:
0x309
Manufacturer: Broadcom Corporation (15)
localhost chase # hciconfig hci0 scomtu 64:8
localhost chase # hciconfig -a
hci0: Type: USB
BD Address: 00:02:72:C3:C5:2E ACL MTU: 377:10 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:14392 acl:25 sco:0 events:799 errors:0
TX bytes:4813 acl:18 sco:0 commands:752 errors:0
Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ (0)'
Class: 0xff0408
Service Classes: Positioning, Networking, Rendering, Capturing
Device Class: Audio/Video, Hands-free
HCI Ver: 1.2 (0x2) HCI Rev: 0x14 LMP Ver: 1.2 (0x2) LMP Subver:
0x309
Manufacturer: Broadcom Corporation (15)
I can't get anything from or to my headset, although I can transmit and
receive when using a D-Link DBT-120 rev. B4. I had also applied the
first patch about the mtu stuff, but not the one to set the mtu by default.
Let me know if you know of anything to try.
Thanks
Mario wrote:
>2006/2/12, Brad Midgley <bmidgley@xmission.com>:
>
>
>>We should find out exactly what that second poster "whoopie" was doing
>>to set the mtu. Apparently he was only asking if the modified patch
>>would work but he had gotten it working by using the original patch and
>>tweaking the mtu at runtime.
>>
>>
>
>It's incredible! Without any patch to the kernel.
>
>hciconfig hci0 scomtu 64:8
>
>IT WORKS!! A nasty Broadcom BT Chipset works! :\
>
>root@legolas:~# hciconfig hci0 revision
>hci0: Type: USB
> BD Address: 00:10:C6:59:7A:FC ACL MTU: 377:10 SCO MTU: 16:0
> Firmware 2.105 / 97
>
>root@legolas:~# hciconfig hci0 scomtu 64:8
>
>root@legolas:~# hciconfig hci0 revision
>hci0: Type: USB
> BD Address: 00:10:C6:59:7A:FC ACL MTU: 377:10 SCO MTU: 64:8
> Firmware 2.105 / 97
>
>Now my Plantronics Voyager 510 BT headset works (I have to test it
>better with applications now...).
>
>Mario :D
>
>
>-------------------------------------------------------
>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://sel.as-us.falkag.net/sel?cmd_______________________________________________
>Bluez-devel mailing list
>Bluez-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
-------------------------------------------------------
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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&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-02-13 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 19:05 [Bluez-devel] Re: Developing Broadcom driver support Keith Bannister
2006-02-12 6:17 ` Brad Midgley
2006-02-12 23:00 ` Mario
2006-02-13 0:12 ` Chase Douglas [this message]
2006-02-13 17:27 ` Brad Midgley
2006-02-15 10:02 ` Mario
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=43EFCEFF.60707@purdue.edu \
--to=cndougla@purdue.edu \
--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).