real reason to split it out to a seperate file. Additionally the
seperate file was not listed in build_docs.sh and therefore was not
included in the PDF documentation.
If there was a section of supported hardware as an appendix to the
documentation that we could move it back, but that should be done for
GPS, RX's, LED, Buzzers, etc and all at the same time.
"Applications with low acceleration and speed, e.g. how a pedestrian
would move. Low acceleration assumed. MAX Altitude [m]: 9000, MAX
Velocity [m/s]: 30, MAX Vertical Velocity [m/s]: 20, Sanity check type:
Altitude and Velocity, Max Position Deviation: Small"
It was noticed that GPS startup time increased when the change was made
from using EGNOS by default to using AUTO by default.
The default is still AUTO but faster GPS startup times may be achieved
by telling the GPS receiver what region you are in.
This also removes more unfinished MTK gps provider support.