Hi Daniel, > For me, this is going to be a shot in the dark, not being familiar with > the Bluetooth protocol, but could one of you developers please say if > any of what follows makes sense? > > Comparing the hci dumps from my mouse's reconnection and Stefan's, I am > suspicious of the first line below: > > [...] > 2010-01-08 00:15:03.136170 < ACL data: handle 42 flags 0x02 dlen 10 > L2CAP(s): Info req: type 2 > 2010-01-08 00:15:03.144090 > HCI Event: Command Status (0x0f) plen 4 > Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1 I totally missed this command. Yes, you are on the right track. We have a timeout for devices not responding to information request. #define L2CAP_INFO_TIMEOUT (4000) /* 4 seconds */ Problem here is that information request is actually needed to determine the features of the remote L2CAP stack. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
