From f6175605cdaf19dd639ac7cb2b35caaf1e83c5f2 Mon Sep 17 00:00:00 2001
From: Jacob Dahl <37091262+dakejahl@users.noreply.github.com>
Date: Fri, 11 Jan 2019 08:21:51 -0700
Subject: [PATCH] px4_fmu-v4 init: Do not start mavlink stream on ttyS0 for the
 TealOne airframe

 * We have RAM problems and can't afford 4 mavlink instances. This only adds logic the rc.board for the fmu-v4 that only has an effect for SYS_AUTOSTART = 4250 (TealOne airframe).
---
 boards/px4/fmu-v4/init/rc.board | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/boards/px4/fmu-v4/init/rc.board b/boards/px4/fmu-v4/init/rc.board
index afd52906bb..a6cf649995 100644
--- a/boards/px4/fmu-v4/init/rc.board
+++ b/boards/px4/fmu-v4/init/rc.board
@@ -89,8 +89,13 @@ then
 fi
 
 
-# Pixracer: start MAVLink on Wifi (ESP8266 port)
-mavlink start -r 20000 -b 921600 -d /dev/ttyS0
+# Pixracer: start MAVLink on Wifi (ESP8266 port). Except for the TealOne airframe.
+if param compare SYS_AUTOSTART 4250
+then
+else
+	mavlink start -r 20000 -b 921600 -d /dev/ttyS0
+fi
+
 
 # Run FrSky Telemetry on Pixracer on the FrSky port if not enabled already
 if param compare TEL_FRSKY_CONFIG 0