All of lore.kernel.org
 help / color / mirror / Atom feed
* Compiling weston
@ 2015-04-22 10:34 Keskinarkaus, Teemu
  2015-04-22 11:38 ` Heikki Sarkanen
  2015-04-22 11:40 ` Otavio Salvador
  0 siblings, 2 replies; 8+ messages in thread
From: Keskinarkaus, Teemu @ 2015-04-22 10:34 UTC (permalink / raw)
  To: meta-freescale

[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]

Hi,

This probably has been discussed before, but I couldn't find anything from archives or from google other than it seems some have gotten this working.

I'm compiling Weston/wayland based system for imx6q-sdb - develboard.

In local.conf I have:
DISTRO_FEATURES_append = " wayland opengl"

In image-recipe I have:

REQUIRED_DISTRO_FEATURES = "wayland"

CORE_IMAGE_BASE_INSTALL += "weston weston-init weston-examples gtk+3-demo clutter-1.0-examples libwayland-egl libwayland-egl-dev"

The built is stopped at error:

| configure: error: Package requirements (egl >= 7.10 glesv2 wayland-client wayland-egl) were not met:
|
| No package 'wayland-egl' found

The  libwayland-egl and libwayland-egl-dev were added later, but the same error still stays.

Should Weston compile without any modifications after checking out meta-fsl-arm?

I tried also checking out the meta-fsl-bsp-release which has newer Weston version and other packages. That worked even worse since the patches provided wouldn't apply to that version.

So how have anyone gotten Weston/wayland compiled?

Teemu Keskinarkaus
Software system engineer
Cell: +358 400 330047
Fax: +358 207 669199
www.maximatecc.com<http://www.maximatecc.com/>

maximatecc
making machines smart, safe and productive


________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

[-- Attachment #2: Type: text/html, Size: 6704 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Compiling weston
  2015-04-22 10:34 Compiling weston Keskinarkaus, Teemu
@ 2015-04-22 11:38 ` Heikki Sarkanen
  2015-04-23 10:02   ` Keskinarkaus, Teemu
  2015-04-22 11:40 ` Otavio Salvador
  1 sibling, 1 reply; 8+ messages in thread
From: Heikki Sarkanen @ 2015-04-22 11:38 UTC (permalink / raw)
  To: Keskinarkaus, Teemu, meta-freescale

[-- Attachment #1: Type: text/plain, Size: 2696 bytes --]

Hi Teemu,

Adding Wayland isn't enough. You should also explicitly remove X11 and Framebuffer so the right Vivante GPU driver gets included for Wayland/Weston.

Try again in new build folder and add this line to your local.conf:
DISTRO_FEATURES_remove = "x11 directfb"

These slides are for fsl-release-bsp, but most parts applies also for fsl-community-bsp, so check slide 49:
https://community.freescale.com/docs/DOC-104266

BR,
Heikki Sarkanen


________________________________
From: meta-freescale-bounces@yoctoproject.org <meta-freescale-bounces@yoctoproject.org> on behalf of Keskinarkaus, Teemu <Teemu.Keskinarkaus@Maximatecc.com>
Sent: 22 April 2015 13:34
To: meta-freescale@yoctoproject.org
Subject: [meta-freescale] Compiling weston

Hi,

This probably has been discussed before, but I couldn't find anything from archives or from google other than it seems some have gotten this working.

I'm compiling Weston/wayland based system for imx6q-sdb - develboard.

In local.conf I have:
DISTRO_FEATURES_append = " wayland opengl"

In image-recipe I have:

REQUIRED_DISTRO_FEATURES = "wayland"

CORE_IMAGE_BASE_INSTALL += "weston weston-init weston-examples gtk+3-demo clutter-1.0-examples libwayland-egl libwayland-egl-dev"

The built is stopped at error:

| configure: error: Package requirements (egl >= 7.10 glesv2 wayland-client wayland-egl) were not met:
|
| No package 'wayland-egl' found

The  libwayland-egl and libwayland-egl-dev were added later, but the same error still stays.

Should Weston compile without any modifications after checking out meta-fsl-arm?

I tried also checking out the meta-fsl-bsp-release which has newer Weston version and other packages. That worked even worse since the patches provided wouldn't apply to that version.

So how have anyone gotten Weston/wayland compiled?

Teemu Keskinarkaus
Software system engineer
Cell: +358 400 330047
Fax: +358 207 669199
www.maximatecc.com<http://www.maximatecc.com/>

maximatecc
making machines smart, safe and productive


________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

[-- Attachment #2: Type: text/html, Size: 9205 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Compiling weston
  2015-04-22 10:34 Compiling weston Keskinarkaus, Teemu
  2015-04-22 11:38 ` Heikki Sarkanen
@ 2015-04-22 11:40 ` Otavio Salvador
  1 sibling, 0 replies; 8+ messages in thread
From: Otavio Salvador @ 2015-04-22 11:40 UTC (permalink / raw)
  To: Keskinarkaus, Teemu; +Cc: meta-freescale

Hello Teemu,

On Wed, Apr 22, 2015 at 7:34 AM, Keskinarkaus, Teemu
<Teemu.Keskinarkaus@maximatecc.com> wrote:
...
> I’m compiling Weston/wayland based system for imx6q-sdb – develboard.
>
> In local.conf I have:
>
> DISTRO_FEATURES_append = " wayland opengl"

Add:

DISTRO_FEATURES_remove = "x11"

and it should work.


-- 
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


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Compiling weston
  2015-04-22 11:38 ` Heikki Sarkanen
@ 2015-04-23 10:02   ` Keskinarkaus, Teemu
  2015-04-23 11:36     ` Heikki Sarkanen
  0 siblings, 1 reply; 8+ messages in thread
From: Keskinarkaus, Teemu @ 2015-04-23 10:02 UTC (permalink / raw)
  To: Heikki Sarkanen, meta-freescale

[-- Attachment #1: Type: text/plain, Size: 4592 bytes --]

Hi,

Thanks. I got the wayland/Weston compiled with that! Thanks.

This next piece is bit of off-topic, but I'm sure someone doing this maybe end up having same problem.

I have display connected to connector marked LVDS0. I got the picture to it with X11 when I configured the screen being at /dev/fb4. Problem is that I'm not sure how to configure that in Weston. I created /.config/weston.ini (I checked that $HOME is set to / when Weston is being started) with output configured to LVDS0 and resolution being correct, but that didn't help. Debugging is also bit hard because Weston does not output anything. I can see that it's running (Weston-processes), but that's about it.

So couple questions. Where should I put the Weston.ini and how do I turn on the debug/info from Weston?

Teemu Keskinarkaus
Software system engineer

maximatecc
making machines smart, safe and productive

From: Heikki Sarkanen [mailto:heikki.sarkanen@tamtron.fi]
Sent: 22. huhtikuuta 2015 14:39
To: Keskinarkaus, Teemu; meta-freescale@yoctoproject.org
Subject: Re: Compiling weston

Hi Teemu,

Adding Wayland isn't enough. You should also explicitly remove X11 and Framebuffer so the right Vivante GPU driver gets included for Wayland/Weston.

Try again in new build folder and add this line to your local.conf:
DISTRO_FEATURES_remove = "x11 directfb"

These slides are for fsl-release-bsp, but most parts applies also for fsl-community-bsp, so check slide 49:
https://community.freescale.com/docs/DOC-104266

BR,
Heikki Sarkanen



________________________________
From: meta-freescale-bounces@yoctoproject.org<mailto:meta-freescale-bounces@yoctoproject.org> <meta-freescale-bounces@yoctoproject.org<mailto:meta-freescale-bounces@yoctoproject.org>> on behalf of Keskinarkaus, Teemu <Teemu.Keskinarkaus@Maximatecc.com<mailto:Teemu.Keskinarkaus@Maximatecc.com>>
Sent: 22 April 2015 13:34
To: meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: [meta-freescale] Compiling weston

Hi,

This probably has been discussed before, but I couldn't find anything from archives or from google other than it seems some have gotten this working.

I'm compiling Weston/wayland based system for imx6q-sdb - develboard.

In local.conf I have:
DISTRO_FEATURES_append = " wayland opengl"

In image-recipe I have:

REQUIRED_DISTRO_FEATURES = "wayland"

CORE_IMAGE_BASE_INSTALL += "weston weston-init weston-examples gtk+3-demo clutter-1.0-examples libwayland-egl libwayland-egl-dev"

The built is stopped at error:

| configure: error: Package requirements (egl >= 7.10 glesv2 wayland-client wayland-egl) were not met:
|
| No package 'wayland-egl' found

The  libwayland-egl and libwayland-egl-dev were added later, but the same error still stays.

Should Weston compile without any modifications after checking out meta-fsl-arm?

I tried also checking out the meta-fsl-bsp-release which has newer Weston version and other packages. That worked even worse since the patches provided wouldn't apply to that version.

So how have anyone gotten Weston/wayland compiled?

Teemu Keskinarkaus
Software system engineer
Cell: +358 400 330047
Fax: +358 207 669199
www.maximatecc.com<http://www.maximatecc.com/>
maximatecc
making machines smart, safe and productive


________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

[-- Attachment #2: Type: text/html, Size: 21085 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Compiling weston
  2015-04-23 10:02   ` Keskinarkaus, Teemu
@ 2015-04-23 11:36     ` Heikki Sarkanen
  2015-04-24  5:03       ` Keskinarkaus, Teemu
  0 siblings, 1 reply; 8+ messages in thread
From: Heikki Sarkanen @ 2015-04-23 11:36 UTC (permalink / raw)
  To: Keskinarkaus, Teemu, meta-freescale

[-- Attachment #1: Type: text/plain, Size: 6573 bytes --]

Hi,

As I have understood on current iMX6/Yocto you are forced to use fbdev-backend, which doesn't really use weston.ini until lately (possibly included in coming Weston 1.8) http://cgit.freedesktop.org/wayland/weston/commit/?id=44ed70b469beb97b6438d07a8048418f6302a0e2 when transform was added. Drm-backend supports many configs but currently iMX6 doesn't support it. Of course you can change desktop-shell behavior etc if you wish using ~/.config/weston.ini but that's another topic. But things you're trying to do should be possible.

You can check command line options supported by fbdev-backend from Weston sources: http://cgit.freedesktop.org/wayland/weston/tree/src/compositor-fbdev.c?id=1.6.0#n971 Fsl-patch adds option for gal2d-renderer which I found having some graphics glithces which default gl-renderer doesn't have: https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-graphics/wayland/weston/0002-ENGR00314805-2-Add-Vivante-GAL2D-support.patch#L256-L257

So changing the device should be easy:
# Kill the already running Weston
killall weston
# Weston wants this environment variable to be set (http://wayland.freedesktop.org/building.html)<http://wayland.freedesktop.org/building.html>
export XDG_RUNTIME_DIR=/run/user/root && mkdir --parents $XDG_RUNTIME_DIR && chmod 0700 $XDG_RUNTIME_DIR
# Launch Weston on fb4, you should now see some debug info as well
weston --tty=1 --use-gal2d=0 --use-gl=1 --device=/dev/fb4

If you want to change the behavior on boot you should look Weston init file: https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-graphics/wayland/weston-init/init You could try to change line "openvt -s weston" to something like "openvt -s -- weston --device=/dev/fb4".

BR,
Heikki Sarkanen


________________________________
From: Keskinarkaus, Teemu <Teemu.Keskinarkaus@Maximatecc.com>
Sent: 23 April 2015 13:02
To: Heikki Sarkanen; meta-freescale@yoctoproject.org
Subject: RE: Compiling weston

Hi,

Thanks. I got the wayland/Weston compiled with that! Thanks.

This next piece is bit of off-topic, but I’m sure someone doing this maybe end up having same problem.

I have display connected to connector marked LVDS0. I got the picture to it with X11 when I configured the screen being at /dev/fb4. Problem is that I’m not sure how to configure that in Weston. I created /.config/weston.ini (I checked that $HOME is set to / when Weston is being started) with output configured to LVDS0 and resolution being correct, but that didn’t help. Debugging is also bit hard because Weston does not output anything. I can see that it’s running (Weston-processes), but that’s about it.

So couple questions. Where should I put the Weston.ini and how do I turn on the debug/info from Weston?

Teemu Keskinarkaus
Software system engineer

maximatecc
making machines smart, safe and productive

From: Heikki Sarkanen [mailto:heikki.sarkanen@tamtron.fi]
Sent: 22. huhtikuuta 2015 14:39
To: Keskinarkaus, Teemu; meta-freescale@yoctoproject.org
Subject: Re: Compiling weston

Hi Teemu,

Adding Wayland isn't enough. You should also explicitly remove X11 and Framebuffer so the right Vivante GPU driver gets included for Wayland/Weston.

Try again in new build folder and add this line to your local.conf:
DISTRO_FEATURES_remove = "x11 directfb"

These slides are for fsl-release-bsp, but most parts applies also for fsl-community-bsp, so check slide 49:
https://community.freescale.com/docs/DOC-104266

BR,
Heikki Sarkanen



________________________________
From: meta-freescale-bounces@yoctoproject.org<mailto:meta-freescale-bounces@yoctoproject.org> <meta-freescale-bounces@yoctoproject.org<mailto:meta-freescale-bounces@yoctoproject.org>> on behalf of Keskinarkaus, Teemu <Teemu.Keskinarkaus@Maximatecc.com<mailto:Teemu.Keskinarkaus@Maximatecc.com>>
Sent: 22 April 2015 13:34
To: meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: [meta-freescale] Compiling weston

Hi,

This probably has been discussed before, but I couldn’t find anything from archives or from google other than it seems some have gotten this working.

I’m compiling Weston/wayland based system for imx6q-sdb – develboard.

In local.conf I have:
DISTRO_FEATURES_append = " wayland opengl"

In image-recipe I have:

REQUIRED_DISTRO_FEATURES = "wayland"

CORE_IMAGE_BASE_INSTALL += "weston weston-init weston-examples gtk+3-demo clutter-1.0-examples libwayland-egl libwayland-egl-dev"

The built is stopped at error:

| configure: error: Package requirements (egl >= 7.10 glesv2 wayland-client wayland-egl) were not met:
|
| No package 'wayland-egl' found

The  libwayland-egl and libwayland-egl-dev were added later, but the same error still stays.

Should Weston compile without any modifications after checking out meta-fsl-arm?

I tried also checking out the meta-fsl-bsp-release which has newer Weston version and other packages. That worked even worse since the patches provided wouldn’t apply to that version.

So how have anyone gotten Weston/wayland compiled?

Teemu Keskinarkaus
Software system engineer
Cell: +358 400 330047
Fax: +358 207 669199
www.maximatecc.com<http://www.maximatecc.com/>
maximatecc
making machines smart, safe and productive


________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

[-- Attachment #2: Type: text/html, Size: 27701 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Compiling weston
  2015-04-23 11:36     ` Heikki Sarkanen
@ 2015-04-24  5:03       ` Keskinarkaus, Teemu
  2015-04-24  6:58         ` Heikki Sarkanen
  0 siblings, 1 reply; 8+ messages in thread
From: Keskinarkaus, Teemu @ 2015-04-24  5:03 UTC (permalink / raw)
  To: Heikki Sarkanen, meta-freescale

[-- Attachment #1: Type: text/plain, Size: 8358 bytes --]

Hi,

I got the debug-output. It seems that the Weston init-script opens virtual terminal and I think that's where all the outputs are but they are not just shown now.

One more problem. It seems that the Weston always defaults to 1024x768 resolution. I looked at the compositor-fbdev.c code you pointed out and it seems that there is no option for configuring the resolution or screen settings. I tried to set the parameters with fbset and they seemed to be right before I started the Weston, but still the Weston defaults to 1024x768 resolution.  I'm guessing there has to be a way to configure the resolution/color depth etc.?

Although looking at the code I get feeling that they are calculated runtime from framebuffer metadata.

Teemu Keskinarkaus
Software system engineer

maximatecc
making machines smart, safe and productive

From: Heikki Sarkanen [mailto:heikki.sarkanen@tamtron.fi]
Sent: 23. huhtikuuta 2015 14:36
To: Keskinarkaus, Teemu; meta-freescale@yoctoproject.org
Subject: Re: Compiling weston

Hi,

As I have understood on current iMX6/Yocto you are forced to use fbdev-backend, which doesn't really use weston.ini until lately (possibly included in coming Weston 1.8) http://cgit.freedesktop.org/wayland/weston/commit/?id=44ed70b469beb97b6438d07a8048418f6302a0e2 when transform was added. Drm-backend supports many configs but currently iMX6 doesn't support it. Of course you can change desktop-shell behavior etc if you wish using ~/.config/weston.ini but that's another topic. But things you're trying to do should be possible.

You can check command line options supported by fbdev-backend from Weston sources: http://cgit.freedesktop.org/wayland/weston/tree/src/compositor-fbdev.c?id=1.6.0#n971 Fsl-patch adds option for gal2d-renderer which I found having some graphics glithces which default gl-renderer doesn't have: https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-graphics/wayland/weston/0002-ENGR00314805-2-Add-Vivante-GAL2D-support.patch#L256-L257

So changing the device should be easy:
# Kill the already running Weston
killall weston
# Weston wants this environment variable to be set (http://wayland.freedesktop.org/building.html)<http://wayland.freedesktop.org/building.html>
export XDG_RUNTIME_DIR=/run/user/root && mkdir --parents $XDG_RUNTIME_DIR && chmod 0700 $XDG_RUNTIME_DIR
# Launch Weston on fb4, you should now see some debug info as well
weston --tty=1 --use-gal2d=0 --use-gl=1 --device=/dev/fb4

If you want to change the behavior on boot you should look Weston init file: https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-graphics/wayland/weston-init/init You could try to change line "openvt -s weston" to something like "openvt -s -- weston --device=/dev/fb4".

BR,
Heikki Sarkanen



________________________________
From: Keskinarkaus, Teemu <Teemu.Keskinarkaus@Maximatecc.com<mailto:Teemu.Keskinarkaus@Maximatecc.com>>
Sent: 23 April 2015 13:02
To: Heikki Sarkanen; meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: RE: Compiling weston

Hi,

Thanks. I got the wayland/Weston compiled with that! Thanks.

This next piece is bit of off-topic, but I'm sure someone doing this maybe end up having same problem.

I have display connected to connector marked LVDS0. I got the picture to it with X11 when I configured the screen being at /dev/fb4. Problem is that I'm not sure how to configure that in Weston. I created /.config/weston.ini (I checked that $HOME is set to / when Weston is being started) with output configured to LVDS0 and resolution being correct, but that didn't help. Debugging is also bit hard because Weston does not output anything. I can see that it's running (Weston-processes), but that's about it.

So couple questions. Where should I put the Weston.ini and how do I turn on the debug/info from Weston?

Teemu Keskinarkaus
Software system engineer
maximatecc
making machines smart, safe and productive

From: Heikki Sarkanen [mailto:heikki.sarkanen@tamtron.fi]
Sent: 22. huhtikuuta 2015 14:39
To: Keskinarkaus, Teemu; meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: Re: Compiling weston

Hi Teemu,

Adding Wayland isn't enough. You should also explicitly remove X11 and Framebuffer so the right Vivante GPU driver gets included for Wayland/Weston.

Try again in new build folder and add this line to your local.conf:
DISTRO_FEATURES_remove = "x11 directfb"

These slides are for fsl-release-bsp, but most parts applies also for fsl-community-bsp, so check slide 49:
https://community.freescale.com/docs/DOC-104266

BR,
Heikki Sarkanen



________________________________
From: meta-freescale-bounces@yoctoproject.org<mailto:meta-freescale-bounces@yoctoproject.org> <meta-freescale-bounces@yoctoproject.org<mailto:meta-freescale-bounces@yoctoproject.org>> on behalf of Keskinarkaus, Teemu <Teemu.Keskinarkaus@Maximatecc.com<mailto:Teemu.Keskinarkaus@Maximatecc.com>>
Sent: 22 April 2015 13:34
To: meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: [meta-freescale] Compiling weston

Hi,

This probably has been discussed before, but I couldn't find anything from archives or from google other than it seems some have gotten this working.

I'm compiling Weston/wayland based system for imx6q-sdb - develboard.

In local.conf I have:
DISTRO_FEATURES_append = " wayland opengl"

In image-recipe I have:

REQUIRED_DISTRO_FEATURES = "wayland"

CORE_IMAGE_BASE_INSTALL += "weston weston-init weston-examples gtk+3-demo clutter-1.0-examples libwayland-egl libwayland-egl-dev"

The built is stopped at error:

| configure: error: Package requirements (egl >= 7.10 glesv2 wayland-client wayland-egl) were not met:
|
| No package 'wayland-egl' found

The  libwayland-egl and libwayland-egl-dev were added later, but the same error still stays.

Should Weston compile without any modifications after checking out meta-fsl-arm?

I tried also checking out the meta-fsl-bsp-release which has newer Weston version and other packages. That worked even worse since the patches provided wouldn't apply to that version.

So how have anyone gotten Weston/wayland compiled?

Teemu Keskinarkaus
Software system engineer
Cell: +358 400 330047
Fax: +358 207 669199
www.maximatecc.com<http://www.maximatecc.com/>
maximatecc
making machines smart, safe and productive


________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

[-- Attachment #2: Type: text/html, Size: 35348 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Compiling weston
  2015-04-24  5:03       ` Keskinarkaus, Teemu
@ 2015-04-24  6:58         ` Heikki Sarkanen
  2015-04-24  7:41           ` Keskinarkaus, Teemu
  0 siblings, 1 reply; 8+ messages in thread
From: Heikki Sarkanen @ 2015-04-24  6:58 UTC (permalink / raw)
  To: Keskinarkaus, Teemu, meta-freescale

[-- Attachment #1: Type: text/plain, Size: 9350 bytes --]

Hi,

In my experience the screen should be configured properly for the kernel after that I haven't had any problems in Weston to recognize the resolution.

First you could try to pass it as kernel command line option, for example: "video=mxcfb0:dev=ldb,1280x800M@60,if=RGB24 ldb=sin0". More info: http://boundarydevices.com/configuring-i-mx6-machines-different-screens-nitrogen6x-sabre-lite/​

For more permanent configuration you could try modifying device tree, format and device tree support may vary depending on your kernel version. Here is one example: https://github.com/Freescale/meta-fsl-arm-extra/blob/master/recipes-kernel/linux/linux-compulab-3.14.28/0054-ARM-i.MX6-dts-add-ldb-support-for-SBC-FX6-boards.patch

BR,
Heikki Sarkanen


________________________________
From: Keskinarkaus, Teemu <Teemu.Keskinarkaus@Maximatecc.com>
Sent: 24 April 2015 8:03
To: Heikki Sarkanen; meta-freescale@yoctoproject.org
Subject: RE: Compiling weston

Hi,

I got the debug-output. It seems that the Weston init-script opens virtual terminal and I think that’s where all the outputs are but they are not just shown now.

One more problem. It seems that the Weston always defaults to 1024x768 resolution. I looked at the compositor-fbdev.c code you pointed out and it seems that there is no option for configuring the resolution or screen settings. I tried to set the parameters with fbset and they seemed to be right before I started the Weston, but still the Weston defaults to 1024x768 resolution.  I’m guessing there has to be a way to configure the resolution/color depth etc.?

Although looking at the code I get feeling that they are calculated runtime from framebuffer metadata.

Teemu Keskinarkaus
Software system engineer

maximatecc
making machines smart, safe and productive

From: Heikki Sarkanen [mailto:heikki.sarkanen@tamtron.fi]
Sent: 23. huhtikuuta 2015 14:36
To: Keskinarkaus, Teemu; meta-freescale@yoctoproject.org
Subject: Re: Compiling weston

Hi,

As I have understood on current iMX6/Yocto you are forced to use fbdev-backend, which doesn't really use weston.ini until lately (possibly included in coming Weston 1.8) http://cgit.freedesktop.org/wayland/weston/commit/?id=44ed70b469beb97b6438d07a8048418f6302a0e2 when transform was added. Drm-backend supports many configs but currently iMX6 doesn't support it. Of course you can change desktop-shell behavior etc if you wish using ~/.config/weston.ini but that's another topic. But things you're trying to do should be possible.

You can check command line options supported by fbdev-backend from Weston sources: http://cgit.freedesktop.org/wayland/weston/tree/src/compositor-fbdev.c?id=1.6.0#n971 Fsl-patch adds option for gal2d-renderer which I found having some graphics glithces which default gl-renderer doesn't have: https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-graphics/wayland/weston/0002-ENGR00314805-2-Add-Vivante-GAL2D-support.patch#L256-L257

So changing the device should be easy:
# Kill the already running Weston
killall weston
# Weston wants this environment variable to be set (http://wayland.freedesktop.org/building.html)<http://wayland.freedesktop.org/building.html>
export XDG_RUNTIME_DIR=/run/user/root && mkdir --parents $XDG_RUNTIME_DIR && chmod 0700 $XDG_RUNTIME_DIR
# Launch Weston on fb4, you should now see some debug info as well
weston --tty=1 --use-gal2d=0 --use-gl=1 --device=/dev/fb4

If you want to change the behavior on boot you should look Weston init file: https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-graphics/wayland/weston-init/init You could try to change line "openvt -s weston" to something like "openvt -s -- weston --device=/dev/fb4".

BR,
Heikki Sarkanen



________________________________
From: Keskinarkaus, Teemu <Teemu.Keskinarkaus@Maximatecc.com<mailto:Teemu.Keskinarkaus@Maximatecc.com>>
Sent: 23 April 2015 13:02
To: Heikki Sarkanen; meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: RE: Compiling weston

Hi,

Thanks. I got the wayland/Weston compiled with that! Thanks.

This next piece is bit of off-topic, but I’m sure someone doing this maybe end up having same problem.

I have display connected to connector marked LVDS0. I got the picture to it with X11 when I configured the screen being at /dev/fb4. Problem is that I’m not sure how to configure that in Weston. I created /.config/weston.ini (I checked that $HOME is set to / when Weston is being started) with output configured to LVDS0 and resolution being correct, but that didn’t help. Debugging is also bit hard because Weston does not output anything. I can see that it’s running (Weston-processes), but that’s about it.

So couple questions. Where should I put the Weston.ini and how do I turn on the debug/info from Weston?

Teemu Keskinarkaus
Software system engineer
maximatecc
making machines smart, safe and productive

From: Heikki Sarkanen [mailto:heikki.sarkanen@tamtron.fi]
Sent: 22. huhtikuuta 2015 14:39
To: Keskinarkaus, Teemu; meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: Re: Compiling weston

Hi Teemu,

Adding Wayland isn't enough. You should also explicitly remove X11 and Framebuffer so the right Vivante GPU driver gets included for Wayland/Weston.

Try again in new build folder and add this line to your local.conf:
DISTRO_FEATURES_remove = "x11 directfb"

These slides are for fsl-release-bsp, but most parts applies also for fsl-community-bsp, so check slide 49:
https://community.freescale.com/docs/DOC-104266

BR,
Heikki Sarkanen



________________________________
From: meta-freescale-bounces@yoctoproject.org<mailto:meta-freescale-bounces@yoctoproject.org> <meta-freescale-bounces@yoctoproject.org<mailto:meta-freescale-bounces@yoctoproject.org>> on behalf of Keskinarkaus, Teemu <Teemu.Keskinarkaus@Maximatecc.com<mailto:Teemu.Keskinarkaus@Maximatecc.com>>
Sent: 22 April 2015 13:34
To: meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: [meta-freescale] Compiling weston

Hi,

This probably has been discussed before, but I couldn’t find anything from archives or from google other than it seems some have gotten this working.

I’m compiling Weston/wayland based system for imx6q-sdb – develboard.

In local.conf I have:
DISTRO_FEATURES_append = " wayland opengl"

In image-recipe I have:

REQUIRED_DISTRO_FEATURES = "wayland"

CORE_IMAGE_BASE_INSTALL += "weston weston-init weston-examples gtk+3-demo clutter-1.0-examples libwayland-egl libwayland-egl-dev"

The built is stopped at error:

| configure: error: Package requirements (egl >= 7.10 glesv2 wayland-client wayland-egl) were not met:
|
| No package 'wayland-egl' found

The  libwayland-egl and libwayland-egl-dev were added later, but the same error still stays.

Should Weston compile without any modifications after checking out meta-fsl-arm?

I tried also checking out the meta-fsl-bsp-release which has newer Weston version and other packages. That worked even worse since the patches provided wouldn’t apply to that version.

So how have anyone gotten Weston/wayland compiled?

Teemu Keskinarkaus
Software system engineer
Cell: +358 400 330047
Fax: +358 207 669199
www.maximatecc.com<http://www.maximatecc.com/>
maximatecc
making machines smart, safe and productive


________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

[-- Attachment #2: Type: text/html, Size: 43895 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Compiling weston
  2015-04-24  6:58         ` Heikki Sarkanen
@ 2015-04-24  7:41           ` Keskinarkaus, Teemu
  0 siblings, 0 replies; 8+ messages in thread
From: Keskinarkaus, Teemu @ 2015-04-24  7:41 UTC (permalink / raw)
  To: Heikki Sarkanen, meta-freescale

[-- Attachment #1: Type: text/plain, Size: 10534 bytes --]

Hi,

Ah, forgot the whole command line options. Now I have picture! Thanks. Now I just need to make that patch for the display settings.

Teemu Keskinarkaus
Software system engineer

maximatecc
making machines smart, safe and productive

From: Heikki Sarkanen [mailto:heikki.sarkanen@tamtron.fi]
Sent: 24. huhtikuuta 2015 9:59
To: Keskinarkaus, Teemu; meta-freescale@yoctoproject.org
Subject: Re: Compiling weston

Hi,

In my experience the screen should be configured properly for the kernel after that I haven't had any problems in Weston to recognize the resolution.

First you could try to pass it as kernel command line option, for example: "video=mxcfb0:dev=ldb,1280x800M@60,if=RGB24 ldb=sin0". More info: http://boundarydevices.com/configuring-i-mx6-machines-different-screens-nitrogen6x-sabre-lite/​

For more permanent configuration you could try modifying device tree, format and device tree support may vary depending on your kernel version. Here is one example: https://github.com/Freescale/meta-fsl-arm-extra/blob/master/recipes-kernel/linux/linux-compulab-3.14.28/0054-ARM-i.MX6-dts-add-ldb-support-for-SBC-FX6-boards.patch

BR,
Heikki Sarkanen



________________________________
From: Keskinarkaus, Teemu <Teemu.Keskinarkaus@Maximatecc.com<mailto:Teemu.Keskinarkaus@Maximatecc.com>>
Sent: 24 April 2015 8:03
To: Heikki Sarkanen; meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: RE: Compiling weston

Hi,

I got the debug-output. It seems that the Weston init-script opens virtual terminal and I think that’s where all the outputs are but they are not just shown now.

One more problem. It seems that the Weston always defaults to 1024x768 resolution. I looked at the compositor-fbdev.c code you pointed out and it seems that there is no option for configuring the resolution or screen settings. I tried to set the parameters with fbset and they seemed to be right before I started the Weston, but still the Weston defaults to 1024x768 resolution.  I’m guessing there has to be a way to configure the resolution/color depth etc.?

Although looking at the code I get feeling that they are calculated runtime from framebuffer metadata.

Teemu Keskinarkaus
Software system engineer
maximatecc
making machines smart, safe and productive

From: Heikki Sarkanen [mailto:heikki.sarkanen@tamtron.fi]
Sent: 23. huhtikuuta 2015 14:36
To: Keskinarkaus, Teemu; meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: Re: Compiling weston

Hi,

As I have understood on current iMX6/Yocto you are forced to use fbdev-backend, which doesn't really use weston.ini until lately (possibly included in coming Weston 1.8) http://cgit.freedesktop.org/wayland/weston/commit/?id=44ed70b469beb97b6438d07a8048418f6302a0e2 when transform was added. Drm-backend supports many configs but currently iMX6 doesn't support it. Of course you can change desktop-shell behavior etc if you wish using ~/.config/weston.ini but that's another topic. But things you're trying to do should be possible.

You can check command line options supported by fbdev-backend from Weston sources: http://cgit.freedesktop.org/wayland/weston/tree/src/compositor-fbdev.c?id=1.6.0#n971 Fsl-patch adds option for gal2d-renderer which I found having some graphics glithces which default gl-renderer doesn't have: https://github.com/Freescale/meta-fsl-arm/blob/master/recipes-graphics/wayland/weston/0002-ENGR00314805-2-Add-Vivante-GAL2D-support.patch#L256-L257

So changing the device should be easy:
# Kill the already running Weston
killall weston
# Weston wants this environment variable to be set (http://wayland.freedesktop.org/building.html)<http://wayland.freedesktop.org/building.html>
export XDG_RUNTIME_DIR=/run/user/root && mkdir --parents $XDG_RUNTIME_DIR && chmod 0700 $XDG_RUNTIME_DIR
# Launch Weston on fb4, you should now see some debug info as well
weston --tty=1 --use-gal2d=0 --use-gl=1 --device=/dev/fb4

If you want to change the behavior on boot you should look Weston init file: https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-graphics/wayland/weston-init/init You could try to change line "openvt -s weston" to something like "openvt -s -- weston --device=/dev/fb4".

BR,
Heikki Sarkanen



________________________________
From: Keskinarkaus, Teemu <Teemu.Keskinarkaus@Maximatecc.com<mailto:Teemu.Keskinarkaus@Maximatecc.com>>
Sent: 23 April 2015 13:02
To: Heikki Sarkanen; meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: RE: Compiling weston

Hi,

Thanks. I got the wayland/Weston compiled with that! Thanks.

This next piece is bit of off-topic, but I’m sure someone doing this maybe end up having same problem.

I have display connected to connector marked LVDS0. I got the picture to it with X11 when I configured the screen being at /dev/fb4. Problem is that I’m not sure how to configure that in Weston. I created /.config/weston.ini (I checked that $HOME is set to / when Weston is being started) with output configured to LVDS0 and resolution being correct, but that didn’t help. Debugging is also bit hard because Weston does not output anything. I can see that it’s running (Weston-processes), but that’s about it.

So couple questions. Where should I put the Weston.ini and how do I turn on the debug/info from Weston?

Teemu Keskinarkaus
Software system engineer
maximatecc
making machines smart, safe and productive

From: Heikki Sarkanen [mailto:heikki.sarkanen@tamtron.fi]
Sent: 22. huhtikuuta 2015 14:39
To: Keskinarkaus, Teemu; meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: Re: Compiling weston

Hi Teemu,

Adding Wayland isn't enough. You should also explicitly remove X11 and Framebuffer so the right Vivante GPU driver gets included for Wayland/Weston.

Try again in new build folder and add this line to your local.conf:
DISTRO_FEATURES_remove = "x11 directfb"

These slides are for fsl-release-bsp, but most parts applies also for fsl-community-bsp, so check slide 49:
https://community.freescale.com/docs/DOC-104266

BR,
Heikki Sarkanen



________________________________
From: meta-freescale-bounces@yoctoproject.org<mailto:meta-freescale-bounces@yoctoproject.org> <meta-freescale-bounces@yoctoproject.org<mailto:meta-freescale-bounces@yoctoproject.org>> on behalf of Keskinarkaus, Teemu <Teemu.Keskinarkaus@Maximatecc.com<mailto:Teemu.Keskinarkaus@Maximatecc.com>>
Sent: 22 April 2015 13:34
To: meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: [meta-freescale] Compiling weston

Hi,

This probably has been discussed before, but I couldn’t find anything from archives or from google other than it seems some have gotten this working.

I’m compiling Weston/wayland based system for imx6q-sdb – develboard.

In local.conf I have:
DISTRO_FEATURES_append = " wayland opengl"

In image-recipe I have:

REQUIRED_DISTRO_FEATURES = "wayland"

CORE_IMAGE_BASE_INSTALL += "weston weston-init weston-examples gtk+3-demo clutter-1.0-examples libwayland-egl libwayland-egl-dev"

The built is stopped at error:

| configure: error: Package requirements (egl >= 7.10 glesv2 wayland-client wayland-egl) were not met:
|
| No package 'wayland-egl' found

The  libwayland-egl and libwayland-egl-dev were added later, but the same error still stays.

Should Weston compile without any modifications after checking out meta-fsl-arm?

I tried also checking out the meta-fsl-bsp-release which has newer Weston version and other packages. That worked even worse since the patches provided wouldn’t apply to that version.

So how have anyone gotten Weston/wayland compiled?

Teemu Keskinarkaus
Software system engineer
Cell: +358 400 330047
Fax: +358 207 669199
www.maximatecc.com<http://www.maximatecc.com/>
maximatecc
making machines smart, safe and productive


________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

[-- Attachment #2: Type: text/html, Size: 45042 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2015-04-24  7:41 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-04-22 10:34 Compiling weston Keskinarkaus, Teemu
2015-04-22 11:38 ` Heikki Sarkanen
2015-04-23 10:02   ` Keskinarkaus, Teemu
2015-04-23 11:36     ` Heikki Sarkanen
2015-04-24  5:03       ` Keskinarkaus, Teemu
2015-04-24  6:58         ` Heikki Sarkanen
2015-04-24  7:41           ` Keskinarkaus, Teemu
2015-04-22 11:40 ` Otavio Salvador

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.