The major change in these patches is to register Primary Services into the SDP databases as required when registering them into the attrib-server's database. The Core v4.0 specification indicates that the only valid/foolproof way for a BR/EDR client to query a server for Primary Services is to do so via an SDP query. This is from Core v4.0, Vol 3, Part G, Sec 4.4: "GATT service discovery over BR/EDR transport will list services that only run over an LE transport and therefore only SDP service discovery shall be used on BR/EDR." This also means that there can be "LE Only" primary services that do NOT need to be in the SDP database, so if a valid range is not specified when registering a Primary Service, it will be omitted from SDP, and only appear when performing a GATT based Primary Service Discover. Also -- The ATT_UUID we were using was incorrect, and I extended the functionality of the gatttool to allow for listening without sending anything, and ability to perform both a char-write and char-cmd. -- Brian Gix bgix@xxxxxxxxxxxxxx Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum -- 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
