src/sys/netgraph/bluetooth, branch release/6.0.0_cvs FreeBSD source tree This commit was manufactured by cvs2svn to create tag 2005-11-03T00:35:26+00:00 cvs2svn cvs2svn@FreeBSD.org 2005-11-03T00:35:26+00:00 3640cb54210edbb7edbf1b12ef0127ecfcea967d 'RELENG_6_0_0_RELEASE'. This commit was manufactured to restore the state of the 6.0-RELEASE image. 
'RELENG_6_0_0_RELEASE'.

This commit was manufactured to restore the state of the 6.0-RELEASE image.
MFC to RELENG 6 2005-09-03T03:34:23+00:00 Maksim Yevmenkin emax@FreeBSD.org 2005-09-03T03:34:23+00:00 b6d7001810940c26fe666fe6690a45feb31e3d3e 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 <onatan at gmail dot com> Approved by: re (scottl) 
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 <onatan at gmail dot com>
Approved by:	re (scottl)
MFC to RELENG_6 2005-08-29T17:00:54+00:00 Maksim Yevmenkin emax@FreeBSD.org 2005-08-29T17:00:54+00:00 1b3533dff23865afb70d374f35e987afb86440f7 Address minor locking issues. Use taskqueue_swi instead of taskqueue_swi_giant. Approved by: re (scottl) 
Address minor locking issues. Use taskqueue_swi instead of taskqueue_swi_giant.

Approved by:	re (scottl)
MFC to RELENG_6 2005-08-25T16:14:33+00:00 Maksim Yevmenkin emax@FreeBSD.org 2005-08-25T16:14:33+00:00 8dbc923ce7efd296993dae6b078c2bed4b7e9a69 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) 
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_6 2005-07-29T16:42:42+00:00 Maksim Yevmenkin emax@FreeBSD.org 2005-07-29T16:42:42+00:00 2e3f0078e6dc119d47ffd9796db74372097dc122 Fix typo and check correct (rsp) pointer against the NULL value. Submitted by: Oliver < urnenfel at tiscali dot es > Approved by: re (kensmith) 
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_6 ng_ubt.c v1.25 2005-07-25T16:22:38+00:00 Maksim Yevmenkin emax@FreeBSD.org 2005-07-25T16:22:38+00:00 bfab6bd09d0c285c72e196318c73a3a4508acf1c 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 > 
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 >
Eliminate unused argument in PCMCIA_CARD macro. 2005-06-24T14:36:54+00:00 Warner Losh imp@FreeBSD.org 2005-06-24T14:36:54+00:00 ab581af7793365b219b8d57024e809a5b0e9c0ad Provide a backwards compatible way to have the extra macro by defining PCCARD_API_LEVEL 5 before including pccarddevs for driver writers that want/need to have the same driver on 5 and 6 with pccard attachments. Approved by: re (dwhite) 
Provide a backwards compatible way to have the extra macro by defining
PCCARD_API_LEVEL 5 before including pccarddevs for driver writers that
want/need to have the same driver on 5 and 6 with pccard attachments.

Approved by: re (dwhite)
Move AVM USB Bluetooth-Adapter BlueFritz! from "broken" devices list 2005-05-28T00:48:42+00:00 Maksim Yevmenkin emax@FreeBSD.org 2005-05-28T00:48:42+00:00 b7e44b056b5b0f7548347a2d54551de8da8dc499 (where I incorrectly put it initially) to "ignored" devices list (where it should be). Pointy hat goes to me. MFC after: 3 days 
(where I incorrectly put it initially) to "ignored" devices list (where
it should be). Pointy hat goes to me.

MFC after:	3 days
Mark AVM USB Bluetooth-Adapter BlueFritz! as "broken". This device is not 2005-05-10T16:25:58+00:00 Maksim Yevmenkin emax@FreeBSD.org 2005-05-10T16:25:58+00:00 c18a1440f0034c0da5c486d9ee5206ff0a199f9d supported by ng_ubt(4) driver and needs its own driver. PR: kern/76205 Submitted by: Tim Hemel < bsd AT timit DOT nl > MFC after: 1 week 
supported by ng_ubt(4) driver and needs its own driver.

PR:		kern/76205
Submitted by:	Tim Hemel < bsd AT timit DOT nl >
MFC after:	1 week
Change the embedded module name from "bluetooth" to "ng_bluetooth" to match 2005-04-08T05:13:53+00:00 Peter Wemm peter@FreeBSD.org 2005-04-08T05:13:53+00:00 e76ce25370bd9df6dfa270355bd098033b5c42f1 the rest of the names assigned to this object. 
the rest of the names assigned to this object.