Hi Marcel, On Wed, Oct 4, 2017 at 10:03 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: > 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? Both the spec and the testing spec, quoted above, impose API requirements to add bearer detail onto the attributes themselves. In the other hand, this only affects 4.0 devices which were unable to connect LE alongside BR/EDR. -- Luiz Augusto von Dentz -- 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
