It looks like the atomic builtins are not available using QuRT and the
Hexagon toolchain, so our best bet is to use `volatile` for the atomics.

When sih (simulation in hardware) was compiled for Snapdragon, we got
the linking problem below. I'm not sure why, supposedly the symbol
`double sin(double)` is missing.

undefined PLT symbol _LSin (705) /libpx4.so (symbol.c:303)

See https://github.com/mavlink/qgroundcontrol/issues/7360

Signed-off-by: Claudio Micheli <claudio@auterion.com>

It implicitly converted STRINGS to STRING.

This fixes a potential dead-lock when 'uorb status' was used via MAVLink
shell.
The dead-lock chain is: DeviceMaster::lock() -> printf -> output to a pipe,
which blocks until a reader reads the data. In that case it's mavlink.
If mavlink makes a call that requires DeviceMaster::lock() (such as
orb_exists), it dead-locks.

This patch moves all printf's out of the locked state.

This should fix the regression where the mag values were not properly
initialized and caused EKF2 to stop in CI.

It is expected that Iris auto-disarms the same as in SITL.

- when either terrain data was temporarily not valid (flying at high
distance to the ground) or the vehicle was not close to the ground
(_param_ekf2_gnd_max_hgt) the ekf switched to using the land detector
ground effect flag.

Signed-off-by: Roman <bapstroman@gmail.com>

    - mavlink v2.0 in PX4/Firmware (a26c25ca5bd0168dd2274dd8aa0392aba10feff2): https://github.com/mavlink/c_library_v2/commit/c6ab0459343c78a6a424514b5f64fa65d8cc0cf8
    - mavlink v2.0 current upstream: https://github.com/mavlink/c_library_v2/commit/d8c4e5def38f2ff6079087e579693b4bd9552584
    - Changes: https://github.com/mavlink/c_library_v2/compare/c6ab0459343c78a6a424514b5f64fa65d8cc0cf8...d8c4e5def38f2ff6079087e579693b4bd9552584

- takeoff help is used for fixed wings, it increases the altitude setpoint
after a launch. A vtol does not need this as it's already sufficiently
high up in the air.

Signed-off-by: Roman <bapstroman@gmail.com>

This reverts commit 4a71984f.

This reverts commit 585b9d8c.

This way we prevent a big dip due to TECS in altitude when the
transition happens at 10 m/s already. Apparently the rule of thumb
is to set this transition speed at the same as airspeed cruise speed.

The noise for airspeed is now applied on the Gazebo side and we can
remove this hack.

Includes:
- Fix for vibration on ground for standard_vtol.
- Noise for diff pressure / airspeed on Gazebo side.
- Fix for macOS magnetometer plugin linking error.

the condition to enter the rc mode switch evaluation was neglecting
the first connection of an RC when "no RC switch changed". this means
depending on the actual initialization values of _last_sp_man and the
desired mode preselected on the RC while connecting it would not get
evaluated.

pure refactor using De Morgan's law to make the condition more intuitive
since you think about when should I enter and not when should I skip

pure refactor of the huge condition into smaller const bool junks

There were multiple comments not addressed in pr #11904.
See commit 4bcb37f9bc9ef20b521ebcf33e7a0ed08fa86ccd

The Pixhawk cube as an internal mag on SPI. If there was a bad register
read (e.g. on an IMU failure), _register_wait was non-zero and there was
no transfer but _mag still published mpu_report.mag.

Auto mode traj - limit yaw setpoint rate of change when generated in the flight task instead of clamping the yaw rate in the controller

Move yaw setpoint slew rate from AutoLineSmoothVel to Auto. The slew rate is now applied consistently to all the auto FlightTasks

Add missing underscore prefix to a member variable in mavlink_main.cpp.h and delete unnecessary struct specifiers in mavlink_main.h.

Migrate an additional set of 16 variable initilializations from the Mavlink class constructor list to their respective declarations.

By declaring the params above the navigator modes inheriting from
mission block we make sure the params in navigator are set before
read in the constructor of mission block.