Hi David,
> And here's a patch that lets the user know the MTU size over DBus:
>
> diff --git a/doc/gatt-api.txt b/doc/gatt-api.txt
> index 2a8da75b0..a0db65383 100644
> --- a/doc/gatt-api.txt
> +++ b/doc/gatt-api.txt
> @@ -68,6 +68,7 @@ Methods array{byte} ReadValue(dict options)
> operation was successful.
>
> Possible options: "offset": uint16 offset
> + "MTU": Exchanged MTU (Server only)
> "device": Object Device (Server only)
>
> Possible Errors: org.bluez.Error.Failed
> @@ -83,6 +84,7 @@ Methods array{byte} ReadValue(dict options)
> characteristic.
>
> Possible options: "offset": Start offset
> + "MTU": Exchanged MTU (Server only)
I prefer "mtu" as option name here. We kept them all lowercase. Other option is to use "max-transfer-unit".
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
