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.salva...@ossystems.com.br]
Sent: Friday, July 15, 2016 12:01 PM
To: Tom Hochstein <tom.hochst...@nxp.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@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.hochst...@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.hochst...@nxp.com>
Acked-by: Otavio Salvador <ota...@ossystems.com.br>
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core