|
From: Alain P. <apa...@us...> - 2002-08-09 09:03:38
|
The following file was modified in linux/drivers/char/bluetooth:
Name Old version New version Tag Comment
---- ----------- ----------- --- -------
rfcomm.c 1.135 1.136=20=20=20=20=20=20=20=20=20=20=20=20=20
The accompanying log:
I temporarly removed the information of the server channel during deconnect=
ion, because the behavior is not always the same. It depends on what stack =
is on the other side.
You now still have deconnection information, but it will always say "0" as =
server channel. I hope I'll correct that soon.
The diff of the modified file(s):
--- rfcomm.c 9 Aug 2002 07:15:53 -0000 1.135
+++ rfcomm.c 9 Aug 2002 09:03:36 -0000 1.136
@@ -1258,6 +1258,7 @@
rfcomm->dlci[tmp_dlci].state =3D DISCONNECTED;
send_ua(rfcomm, tmp_dlci);
=20=09=09=09
+#if 0 /* Removed temporarly, because this generates two informations (wit=
h the previous) */=09=09
#ifdef CONFIG_BLUETOOTH_PROC
new_con_srv_channel =3D tmp_dlci >> 1;
new_con_line =3D rfcomm->line;
@@ -1265,6 +1266,7 @@
/* Wake up if someone reads the proc file */
wake_up_interruptible(&channel_con_wq);=09=09
#endif
+#endif /* if 0 */
D_CTRL("dlci %d was disconnected\n", tmp_dlci);
bt_disconnect_ind(CREATE_RFCOMM_ID(rfcomm->line,=20
tmp_dlci));
|