src-test2/sys/netgraph/bluetooth, branch release/5.5.0

MFC to RELENG_5

2005-09-03T03:39:40Z

Fix dangling callout problem in the Bluetooth L2CAP code that leads to panic. The panic happens when outgoing L2CAP connection descriptor is deleted with the L2CAP command(s) pending in the queue. In this case when the last L2CAP command is deleted (due to cleanup) and reference counter for the L2CAP connection goes down to zero the auto disconnect timeout is incorrectly set. pjd gets credit for tracking this down and committing bandaid. Reported by: Jonatan B Approved by: re (scottl)

MFC to RELENG_5

2005-08-29T17:03:51Z

Address minor locking issues. Use taskqueue_swi instead of taskqueue_swi_giant. Approved by: re (scottl)

MFC to RELENG_5

2005-08-25T16:16:18Z

Fix multiple typos in the mutex names. This fixes false positive (and pretty strange looking too) LORs I have seen on my system. Pointy hat to goes to me. Approved by: re (scottl)

Insta-MFC to RELENG_5

2005-07-29T16:45:21Z

Fix typo and check correct (rsp) pointer against the NULL value. Submitted by: Oliver < urnenfel at tiscali dot es > Approved by: re (kensmith)

MFC to RELENG_5 ng_ubt.c v1.25

2005-07-25T16:24:44Z

Add support for AVM BlueFRITZ! USB Bluetooth Adapter v2.0. It appears that there are at least two versions of the adapter. Version 1 (product ID 0x2200) of the adapter does not work with ng_ubt(4) and require special driver and firmware. Version 2 (product ID 0x3800) seems to work just fine, except it does not have bDeviceClass, bDeviceSubClass and bDeviceProtocol set to required (by specification) values. This change forces ng_ubt(4) to attach to the version 2 adapter. Ignore AVM BlueFRITZ! USB Bluetooth Adapter v1.0 (product ID 0x2200). It does not work with ng_ubt(4) and require special driver and firmware. Submitted by: Rainer Goellner < rainer at jabbe dot de > Approved by: re (kensmith) Obtained from: Marcel Holtmann < marcel at holtmann dot org >

MFC to RELENG_5

2005-05-31T16:47:19Z

Move AVM USB Bluetooth-Adapter BlueFritz! from "broken" devices list (where I incorrectly put it initially) to "ignored" devices list (where it should be). Pointy hat goes to me.

MFC to RELENG_5

2005-05-17T17:56:28Z

Get rid of device nodes interface. It is useless and confusing. The original idea was to use it for firmware upgrading and similar operations. In real life almost all Bluetooth USB devices do not need firmware download. If device does require firmware download then ugen(4) (or specialized driver like ubtbcmfw(8)) should be used instead.

MFC to RELENG_5

2005-05-17T17:30:25Z

Mark AVM USB Bluetooth-Adapter BlueFritz! as "broken". This device is not supported by ng_ubt(4) driver and needs its own driver. PR: kern/76205 Submitted by: Tim Hemel < bsd AT timit DOT nl >

MFC to RELENG_5 src/sys/netgraph/bluetooth/socket/ng_btsocket_rfcomm.c, v1.17

2005-05-12T16:48:24Z

In ng_btsocket_rfcomm_receive_frame() correctly set length variable when EA bit is set in hdr->length (16-bit length). This currently has no effect on the rest of the code. It just fixes the debug message.

MFC sys/netgraph/bluetooth/socket/ng_btsocket_rfcomm.c,v 1.16

2005-05-12T16:45:10Z

move ptr use down to after null check Noticed by: Coverity Prevent analysis tool Submitted by: sam