Fixing the rebase. Should now be identical to upstream
airspeed: use _retries=1 for I2C retries once initialised

airspeed sensors often need to be on longer cables due to having to be
outside the prop wash.
-> Added APM makefiles to Gitignore.
-> Fixed PX4 makefile so it always copies the NuttX config files to PX4NuttX before rebuilding archives.
Merge remote-tracking branch 'upstream/master'
mixer: fixed stream handle leakage
px4iofirmware: fixed override when FMU dead 

this allows for immediate override if the FMU dies without requiring
that the override RC channel be in a particular position
px4io: added RC_CONFIG, SET_OVERRIDE_OK and CLEAR_OVERRIDE_OK ioctls

this allows for full setup of RC override without needing param_get()
to PX4 specific parameters
px4io: publish pwm values when STATUS_FLAGS_FMU_OK is not set

this allows testing of FMU failure behaviour in px4io by monitoring
the reported PWM output when the vehicle code stops sending
updates. Otherwise testing needs to be done with "px4io status" which
is very tedious.

With this change a GCS can monitor the PWM outputs from the failsafe
mixer using normal mavlink messages
px4io: fixed errno returns to be negative
px4io: added OVERRIDE_IMMEDIATE arming flag

this allows the flight code to choose whether FMU failure gives
immediate manual pilot control, or waits for the mode switch to go
past the override threshold
systemcmds: added reflect command for USB testing
px4io: only check SAFETY_OFF, not OUTPUTS_ARMED for allowing mixer changed

If we check OUTPUTS_ARMED then we can't update trim values and scaling
in flight, as there is no way to clear OUTPUTS_ARMED.

If safety is on then it should be perfectly safe to update the mixer
and RC config
Merge remote-tracking branch 'upstream/master'
px4io: configure APM use of px4io without RC handling
APM: configure px4io for no RC handling and no mavlink pipe
ms5611: enabled debug()
Revert "Stack: lower stack of lpwork and hpwork"

This reverts commit 366f19c2c07f249a6ac51f16f08b86454e2e2da4.

For ardupilot at least we are not low on memory, and I'd like to see
some good analysis before lowering the size of these stacks in APM
Sensors: add support for PWM input from US Digital MA3 encoder.

- "make archives is" essential, as this change slightly modifies the NuttX
	configuration (turns off input flow control on USART2).
- MA3 PWM-output encoder can be read on the PX4v1 FMU USART2 RTS pin.
	This pin is not used for communications (the header is TX/RX/CTS).
- Not set up for PX4v2 because I don't know which pins are convenient.
- Suitable for vane-type angle of attack sensing.
- Conversion from PWM to angle is not implemented in the PX4 codebase
	(only in APM codebase) but it's a trivial calculation.
PWM input for angle of attack sensing.

- Supports US Digital MA3 4096-step magnetic encoder connected to FMU USART2 RTS pin.
- Tested and working on PX4v1, with modified APM code to translate PWM to angle of attack.
Merge branch 'angle_of_attack_sensor' of https://github.com/Slatye/PX4Firmware into angle_of_attack_sensor