On Wed, 3 Feb 2010, Daniel T. Cobra wrote: > Basically, do you think the failure to reply to the L2CAP information > request is a non-compliance to the protocol on the part of this > particular mouse model, or does it implement an older version of the > protocol, or something like that? (The delay does not happen under MS > Windows, if it means anything.) I think the mouse is non-compliant, as the L2CAP Information request has been present since at least 1.1 of the specification which says that a valid response should be sent. Sending such a request is optional however, and probably the people who wrote that mouse stack never tested it against anything that sent one. Even if it didn't understand it, it should reply with a "command not understood" message.. > From the hci dump, it seems the mouse replies to the HCI Read Remote > Supported Features: that is unrelated regards, iain -- 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
