* Long Characteristic Reads
@ 2018-04-05 17:53 ken Clark
0 siblings, 0 replies; only message in thread
From: ken Clark @ 2018-04-05 17:53 UTC (permalink / raw)
To: linux-bluetooth
Trying to determine how to respond to long characteristic reads over d-bus.
My application is based on client/bluetoothctl
When I read a characteristic of > MTU size, I get multiple callbacks
to chrc_read_value, with the different offsets that need to be send in
the next transaction.
However I do not see a path in gatt.c to get the MTU for the current
connection, so I know how much data to send.
When I hardcode MTU everything works, but MTU is going to be dynamic
in our application.
Is there a way to access the connections MTU, or is there another
method for handling long reads requests?
Thanks,
Ken
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-04-05 17:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-04-05 17:53 Long Characteristic Reads ken Clark
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).