weston-init: De-couple framebuffer console from Weston for systemd startup

The framebuffer console was using the same I/O as Weston. We fix this
by having openvt switch to the new VT when starting weston-launch, same
as is already done for the sysvinit case.

(From OE-Core rev: fba47b9d881af40eb2462aefd19040dc08314365)

Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

meta/recipes-graphics/wayland/weston-init/init

@@ -31,7 +31,7 @@ case "$1" in
   start)
         . /etc/profile
 
-        weston-start -s -- $OPTARGS
+        weston-start -- $OPTARGS
   ;;
 
   stop)

meta/recipes-graphics/wayland/weston-init/weston-start

@@ -1,5 +1,6 @@
 #!/bin/sh
 # Copyright (C) 2016 O.S. Systems Software LTDA.
+# Copyright (C) 2016 Freescale Semiconductor
 
 export PATH="/sbin:/usr/sbin:/bin:/usr/bin"
 
@@ -32,7 +33,7 @@ else
 	launcher="weston-launch --"
 fi
 
-openvt_args=""
+openvt_args="-s"
 while [ -n "$1" ]; do
 	if [ "$1" = "--" ]; then
 		shift