[OE-core] [PATCH v2] weston-init: De-couple framebuffer console from Weston for systemd startup

[Tom Hochstein]

Sorry again, seems that the weston-start parser is not prepared to take no openvt arguments. Will need to fix that as well.

Tom

-----Original Message-----
From: Otavio Salvador [mailto:otavio.salvador at ossystems.com.br] 
Sent: Friday, July 15, 2016 12:01 PM
To: Tom Hochstein <tom.hochstein at nxp.com>
Cc: Patches and discussions about the oe-core layer <openembedded-core at lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2] weston-init: De-couple framebuffer console from Weston for systemd startup

On Fri, Jul 15, 2016 at 1:33 PM, Tom Hochstein <tom.hochstein at nxp.com> wrote:
> 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.
>
> Signed-off-by: Tom Hochstein <tom.hochstein at nxp.com>

Acked-by: Otavio Salvador <otavio at ossystems.com.br>

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750