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 -- 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
