[OE-core] [PATCH] weston-init: De-couple framebuffer console from Weston

Tom Hochstein tom.hochstein at nxp.com
Mon Jul 11 22:06:49 UTC 2016


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.

Signed-off-by: Tom Hochstein <tom.hochstein at nxp.com>
---
 meta/recipes-graphics/wayland/weston-init/weston-start | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/wayland/weston-init/weston-start b/meta/recipes-graphics/wayland/weston-init/weston-start
index 5b7604f..1ede12e 100755
--- a/meta/recipes-graphics/wayland/weston-init/weston-start
+++ b/meta/recipes-graphics/wayland/weston-init/weston-start
@@ -37,7 +37,7 @@ else
 	launcher="weston-launch --"
 fi
 
-openvt_args=""
+openvt_args="-s"
 while [ -n "$1" ]; do
 	openvt_args="$openvt_args $1"
 	shift
-- 
1.9.1




More information about the Openembedded-core mailing list