* Rename EXT option to TELEMETRY
* Change test accordingly
* Rename FRSKY to TELEMETRY_FRSKY
* Rename ARDUPILOT to TELEMETRY_ARDUPILOT
* More renames (JETI, MAVLINK, NMEA)
* Fixes to make commit-test happy
* Further tests added to commit-test
* Cleanup
* Rename EXTSTD to TELEMETRY_NONE
* Fix Multimodule showing up as Crossfire when only multimode and not crossfire is enabled.
* Don't hardcode telemetry to be Frysky on non STM32 arm targets
* Port multi module code to 9X platforms
* Allow Spektrum telemetry protocol to be selected as protocol for the telemetry selection
* Fix infinite loop in spektrum code
* Fix cosmetics
Changes also done for Horus and Taranis UI where appropriate
* Implementation of Spektrum Telemetry for the DYI Multimodule.
I can only test a subset of sensors and these look okay
* Implement conversion from Fahrenheit to Celsius
* Minor fixes for Spektrum telemetry
* Add some more sensors, show sensor ID instead of instance in the overview
- keys beep and haptic refactoring (not anymore audio events)
- trims move/mid/min/max refactoring (trim end splitted to trim min / trim max)
- S6R new alarms
- S6R servos/rx status displayed as a text (not an integer which has no sense)
- Timer countdown configuration
- The splash was not displayed (but the timeout was there) after the first calibration
* Fixes#3463: negative sensor values were invalid if filter was active for the sensor
* Re #3463: enable simultaneous use of `offset` and `filter` (was: when `offset` was enabled, the `filter` was always inactive even if enabled)
I did a refactoring for the latitude and longitude decoding which should be tested carefully for FrSky S.PORT and D telemetry
There was a double conversion in S.PORT protocol, there are less maths now, and perhaps precision will be better
The Fifo is created with ```telemetryRegister``` and elements (ID + Value) are taken from the Fifo with ```telemetryPop```
Not tested at all. Just for review / discussion