diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2017-06-26 20:03:09 -0700 |
---|---|---|
committer | Dirk Hohndel <dirk@hohndel.org> | 2017-06-26 22:21:14 -0700 |
commit | 4f3a9cdb354215f036d51457eef01a066f1cc62f (patch) | |
tree | c30fe90eaf5717e6917a08e272b606ce9fcbb0d6 /descriptor3.tsv | |
parent | d0c3ef4cf88149ccc337b1e7c05625957216d4e1 (diff) | |
download | subsurface-4f3a9cdb354215f036d51457eef01a066f1cc62f.tar.gz |
BT serial: recognize LE-only devices, and fall back to emulated serial
This is somewhat hacky, but it allows at least the Shearwater
libdivecomputer backend to continue to treat even the BLE GATT model as
just a serial protocol.
What it does is create a special "emulate serial behavior over the
packetized BLE protocol" helper layer, that qtserialbluetooth falls back
on when rfcomm is not available.
NOTE! This still requires some BLE packet code changes to work with the
odd way that Shearwater sets up their BLE GATT communication. So note
that no further patches are necessary to *libdivecomputer*, but some
updates are needed for the subsurface qt-ble.cpp code.
I have those updates in my tree, and this code is all tested on my
Perdix AI, but those patches are currently too ugly to commit as-is.
I've cleaned up this "fake serial" code sufficiently, that cleanup comes
next.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Diffstat (limited to 'descriptor3.tsv')
0 files changed, 0 insertions, 0 deletions