| Message ID | 1468600403-29471-1-git-send-email-tom.hochstein@nxp.com |
|---|---|
| State | New |
| Headers | show |
diff --git a/meta/recipes-graphics/wayland/weston-init/init b/meta/recipes-graphics/wayland/weston-init/init index 5c925f4..d3e87c6 100644 --- a/meta/recipes-graphics/wayland/weston-init/init +++ b/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) 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
On Fri, Jul 15, 2016 at 1:33 PM, Tom Hochstein <tom.hochstein@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@nxp.com> Acked-by: Otavio Salvador <otavio@ossystems.com.br>
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@ossystems.com.br] Sent: Friday, July 15, 2016 12:01 PM To: Tom Hochstein <tom.hochstein@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.hochstein@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@nxp.com> Acked-by: Otavio Salvador <otavio@ossystems.com.br>
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@nxp.com> --- meta/recipes-graphics/wayland/weston-init/init | 2 +- meta/recipes-graphics/wayland/weston-init/weston-start | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)