weston-init: De-couple framebuffer console from Weston

Submitted by Tom Hochstein on July 11, 2016, 10:06 p.m. | Patch ID: 126863

Details

Message ID 1468274809-10301-1-git-send-email-tom.hochstein@nxp.com
State New
Headers show

Commit Message

Tom Hochstein July 11, 2016, 10:06 p.m.
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@nxp.com>
---
 meta/recipes-graphics/wayland/weston-init/weston-start | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Patch hide | download patch | download mbox

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

Comments

Otavio Salvador July 12, 2016, 10:13 a.m.
On Mon, Jul 11, 2016 at 7:06 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.
>
> Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>

Acked-by: Otavio Salvador <otavio@ossystems.com.br>
Tom Hochstein July 15, 2016, 4:16 p.m.
Sorry, looks like this fix is in the wrong place. The sysvinit solution passes the -s openvt arg to weston-start, and the systemd solution should do the same. Will have a new patch shortly.

Tom

-----Original Message-----
From: Otavio Salvador [mailto:otavio.salvador@ossystems.com.br] 
Sent: Tuesday, July 12, 2016 5:13 AM
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] weston-init: De-couple framebuffer console from Weston

On Mon, Jul 11, 2016 at 7:06 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.
>
> Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>

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