> >> Exposing the ATT MTU through Bluez D-BUS API would solve my issue even if it >> is a workaround in term of GATT specification. For diagnostic purpose, it >> might still be helpful to have the MTU exposed in D-BUS API. >> I am happy to have a try to add the support for ATT MTU to Bluez D-BUS >> Device API myself if you think it is feasible and the patches will be >> accepted (obviously after being approved on the mailing-list). > > It would have the same treatment as AcquireWrite and AcquireNotify so > at the start it would probably be marked as experimental. Note that I have a patch for this exact need (reading the negotiated MTU), which I can submit later today for consideration. Jonah-- 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
