Hi, Advertising cache seem to temporarily store the peer_addr_type info, if we reboot, then we loose the information and subsequent connection fails as we don't have the peer_addr_type, unless we re-scan The better approach may be 1) bluez while receiving the advertising events would also store the peer_addr_type info ( may be in dev_info structure in hciops ) 2) while initiating connection bluez may pass the peer_addr_type as part of bt_io_connect in l2cap_connect (attrib/client.c) as part of new option BT_IO_OPT_ Please let me know your comments on above, or if any better approaches/alternatives on the same, thx Regards Vishwanath -- 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
