diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2018-09-06 17:32:24 -0700 |
---|---|---|
committer | Dirk Hohndel <dirk@hohndel.org> | 2018-09-06 18:35:18 -0700 |
commit | 56a77f0fa3ed952f945b34f13b065124909654ea (patch) | |
tree | d4f53744da832746a4e5b00dae37381770a4b25a /core/save-html.c | |
parent | c03c2b5fd74b3dd8b434f5472cba59328748800d (diff) | |
download | subsurface-56a77f0fa3ed952f945b34f13b065124909654ea.tar.gz |
Garmin devices - like Shearwater - want random BLE addressing
We had a special-case for the Shearwater case, let's just make it
slightly more generic and add Garmin to the list of vendors that want a
random BLE address rather than a static one.
The Bluez model of having to state this explicitly - but not giving the
information to the user - is completely broken and this is all very
annoying, credit goes to Wojciech Więckowski for pointing this out.
Of course, right now we don't actually know how to parse the BLE stream
from the Garmin Descent, but with this (and some libdivecomputer
hackery) I actually get connected and start receiving data. That we
then can't parse, but that's hopefully just a libdivecomputer update
away.
Pointed-out-by: Wojciech Więckowski <xplwowi@gmail.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Diffstat (limited to 'core/save-html.c')
0 files changed, 0 insertions, 0 deletions