Tom Hochstein b7a2688ac8 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>

2016-07-26 08:56:26 +01:00

..

init

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

2016-07-26 08:56:26 +01:00

weston-start

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

2016-07-26 08:56:26 +01:00

weston.service

weston-init: Rework init sequence to avoid code duplication

2016-05-21 22:24:55 +01:00