Thread (4 messages) read the whole thread 4 messages, 2 authors, 2009-09-18

Re: BNEP problem, hardware dependent?

From: Stefan Seyfried <hidden>
Date: 2009-09-18 10:46:46

On Fri, 18 Sep 2009 12:07:55 +0200
Stefan Seyfried [off-list ref] wrote:
Will do so, too, if I can make it fail again.
Was pretty easy ;), with an el-cheapo dongle:

strolchi:~ # hciconfig -a
hci0:   Type: USB
        BD Address: 00:02:72:C3:4C:58 ACL MTU: 377:10 SCO MTU: 64:8
        UP RUNNING PSCAN
        RX bytes:7145 acl:43 sco:0 events:179 errors:0
        TX bytes:1390 acl:35 sco:0 commands:108 errors:0
        Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy:
        Link mode: SLAVE ACCEPT
        Name: 'Broadcom BCM2035'
        Class: 0x4a010c
        Service Classes: Networking, Capturing, Telephony
        Device Class: Computer, Laptop
        HCI Ver: 1.2 (0x2) HCI Rev: 0xa LMP Ver: 1.2 (0x2) LMP Subver: 0x309
        Manufacturer: Broadcom Corporation (15)

I attached bluetoothd.log (bluetoothd -nd) and hcidump.log
(hcidump -XVt) because of their size.

JFTR: it works fine with the built-in adapter:

strolchi:~ # hciconfig -a
hci0:   Type: USB
        BD Address: 00:16:41:25:5F:C3 ACL MTU: 1017:8 SCO MTU: 64:8
        UP RUNNING PSCAN
        RX bytes:2597 acl:19 sco:0 events:50 errors:0
        TX bytes:2016 acl:18 sco:0 commands:32 errors:0
        Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'strolchi-builtin'
        Class: 0x4a010c
        Service Classes: Networking, Capturing, Telephony
        Device Class: Computer, Laptop
        HCI Ver: 2.0 (0x3) HCI Rev: 0x204a LMP Ver: 2.0 (0x3) LMP Subver: 0x4127
        Manufacturer: Broadcom Corporation (15)


The ACL MTU is bigger on the built in dongle, but I am quite sure that
I did not set anything, it's all plain plug-and-play.

lsusb shows the following for the two dongles:
Bus 002 Device 004: ID 0a5c:200a Broadcom Corp. Bluetooth dongle
Bus 004 Device 019: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module]

The HP is the one that works.

Thanks,

	seife
-- 
Stefan Seyfried

"Any ideas, John?"
"Well, surrounding them's out."

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help