diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2020-05-16 11:30:20 -0700 |
---|---|---|
committer | Dirk Hohndel <dirk@hohndel.org> | 2020-05-17 09:29:07 -0700 |
commit | e91c252093e2e12488ae576bf38dbf8859efabea (patch) | |
tree | b5df4073823ab47fa88dcc5865d8255ab84d0d93 /scripts/linux2 | |
parent | a7440ce2779734a59a7495ef44b9d62da4aa9eee (diff) | |
download | subsurface-e91c252093e2e12488ae576bf38dbf8859efabea.tar.gz |
BLE: add list of known good/bad BLE GATT services
We've tried to do this "automagic" service discovery, and it mostly
works, but then occasionally it doesn't.
Making things worse, I think different platforms end up enumerating
services differently, so our "pick the first service that looks like it
might be a serial service" ends up working on some platforms, but not
necessarily on others. Because "first" might be different.
So start a list of known good/bad services - and fall back to the old
logic when you can't decide reliably.
This fills in juat a few cases that I can easily check myself, and the
"details" field for them may be incomplete. For example, I know Nordic
Semiconductor has their vendor-specific UUIDs, and they can be found in
different devices, so calling them "Nordic UART" and "Nordic Flash"
services makes sense.
But the "Scubapro i770R" service? It might indeed be specific to the
Scubapro i770R. Or it might be a general service UUID that Pelagic
uses. Or it might be the service UUID of a particular chip, and found
in dive computers from other designs too (and not necessarily in all
i770R's either).
So this is a preliminary first stab at this, and I'm sure we'll extend
the list and possibly improve on the explanations.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'scripts/linux2')
0 files changed, 0 insertions, 0 deletions