Hi, Luiz
In order to implement packet fragmentation/assembly in upper layer
application, may we get ATT MTU extraction API in peripheral/server
side? Basic idea is to get ATT mtu after MTU exchange complete and
write comes in. This patch is the draft implementation.
Thanks
Best wishes
Yunhan
On Thu, Sep 14, 2017 at 4:47 PM, Yunhan Wang <yunhanw@xxxxxxxxxx> wrote:
> Add updateMTU in gatt method to get att mtu value in server side.
> Add MTU property in gatt property.
> ---
> doc/gatt-api.txt | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/doc/gatt-api.txt b/doc/gatt-api.txt
> index cdd15f301..419308a7e 100644
> --- a/doc/gatt-api.txt
> +++ b/doc/gatt-api.txt
> @@ -169,6 +169,13 @@ Methods array{byte} ReadValue(dict options)
>
> Possible Errors: org.bluez.Error.Failed
>
> + void UpdateMTU() [optional] (Server only)
> +
> + This method doesn't expect a reply so it is just
> + MTU value update in user space at server side.
> +
> + Possible Errors: org.bluez.Error.Failed
> +
> Properties string UUID [read-only]
>
> 128-bit characteristic UUID.
> @@ -225,6 +232,10 @@ Properties string UUID [read-only]
> "secure-read" (Server only)
> "secure-write" (Server only)
>
> + uint16_t MTU [read-only, optional]
> +
> + ATT MTU value
> +
> Characteristic Descriptors hierarchy
> ====================================
>
> --
> 2.14.1.690.gbb1197296e-goog
>
--
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
