Hi Luiz, > ATT over BR/EDR requires bearer specific access types in order to pass > tests such as: > > 4.5.71 TP/GAR/CL/BI-34-C [Read Characteristic Value – Invalid Transport > Access over BR/EDR] > Verify Generic Attribute Profile client behavior when an attempt to use > BR/EDR transport to execute the Read Characteristic Value procedure on > a characteristic contained within a service defined for use only over > LE transport. > > On top of that the CCC are considerer bearer specific so for each bearer > supported we would have to maintain different storages: > > In the case where multiple ATT bearers from the same device are supported > by the GATT server, each ATT bearer shall be considered to have a separate > GATT client instance. Therefore each GATT client shall have a separate > Client Characteristic Configuration. > --- > src/gatt-database.c | 120 ---------------------------------------------------- > 1 file changed, 120 deletions(-) I do not understand this patch. Why would we be removing support for GATT over BR/EDR? 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
