Configuring weston with yocto on i.MX6

[davidwretman]

Hi,

I'm trying to enable wayland-weston on my i.MX6 SABRE board. I'm building an image modelled from the core-image-weston.bb with the addition of gpu-viv-bin-mx6q. When trying to start weston I get the following output:

[02:53:58.403] weston 1.1.0                                                    
               http://wayland.freedesktop.org/                                 
               Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?produ0
               Build: 1.0.90-5-gc08bc36-dirty configure.ac: Bump version to 1.1)
[02:53:58.403] OS: Linux, 3.0.35-4.1.0+yocto+gbdde708, #1 SMP PREEMPT Wed Jan 2l
couldn't open //.config/weston.ini                                             
[02:53:58.405] Loading module '/usr/lib/weston/drm-backend.so'                 
couldn't open //.config/weston.ini                                             
[02:53:58.444] initializing drm backend                                        
couldn't open //.config/weston.ini                                             
couldn't open //.config/weston.ini                                             
[02:53:58.448] compositor: using new vt /dev/tty2                              
[02:53:58.453] no drm device found                                             
[02:53:58.453] failed to drop master: Invalid argument                         
[02:53:58.527] fatal: failed to create compositor

How do I need to configure weston to make it run?

Regards,

David

[aurelienbouin]

Using the master repo from Freescale/fsl-community-bsp-platform · GitHub : repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b master

Adding DISTRO_FEATURES_remove = "x11" to my conf file

I finally get bitbake core-image-weston successfully built !!

But at startup weston do not start ...

I don't get any conf file..

I manually start weston with weston --log=weston.log --use-gl=0 --tty=2 &

gtk3-demo work ...

But a lot of weston examples do not work ... I do not have touchscreen also ...

Where can i find any information to make everything working ?

Is there something specific in the kernel that I should enable ?(I am using linux 3.0.35)

Thank you

Here is a log of weston-calibrator start with WAYLAND_DEBUG=1

root@platform:~# export WAYLAND_DEBUG=1 && weston-calibrator

[520349.463]  -> wl_display@1.get_registry(new id wl_registry@2)

[520349.925] wl_registry@2.global(1, "wl_display", 1)

[520350.065] wl_registry@2.global(2, "wl_compositor", 3)

[520350.130]  -> wl_registry@2.bind(2, "wl_compositor", 3, new id [unknown]@3)

[520350.204] wl_registry@2.global(3, "wl_subcompositor", 1)

[520350.264]  -> wl_registry@2.bind(3, "wl_subcompositor", 1, new id [unknown]@4)

[520350.328] wl_registry@2.global(4, "wl_scaler", 1)

[520350.377] wl_registry@2.global(5, "screenshooter", 1)

[520350.426] wl_registry@2.global(6, "wl_text_input_manager", 1)

[520350.475] wl_registry@2.global(7, "wl_data_device_manager", 1)

[520350.524]  -> wl_registry@2.bind(7, "wl_data_device_manager", 1, new id [unknown]@5)

[520350.586] wl_registry@2.global(8, "wl_shm", 1)

[520350.634]  -> wl_registry@2.bind(8, "wl_shm", 1, new id [unknown]@6)

[520350.695] wl_registry@2.global(9, "wl_output", 2)

[520350.745]  -> wl_registry@2.bind(9, "wl_output", 2, new id [unknown]@7)

[520350.806] wl_registry@2.global(10, "wl_seat", 3)

[520350.856]  -> wl_registry@2.bind(10, "wl_seat", 3, new id [unknown]@8)

[520350.923]  -> wl_data_device_manager@5.get_data_device(new id wl_data_device@9, wl_seat@8)

[520350.971]  -> wl_compositor@3.create_surface(new id wl_surface@10)

[520351.028] wl_registry@2.global(11, "wl_input_method", 1)

[520351.080] wl_registry@2.global(12, "wl_input_panel", 1)

[520351.128] wl_registry@2.global(13, "wl_shell", 1)

[520351.179]  -> wl_registry@2.bind(13, "wl_shell", 1, new id [unknown]@11)

[520351.242] wl_registry@2.global(14, "xdg_shell", 1)

[520351.288] wl_registry@2.global(15, "desktop_shell", 2)

[520351.336] wl_registry@2.global(16, "screensaver", 1)

[520351.383] wl_registry@2.global(17, "workspace_manager", 1)

[520351.432]  -> wl_registry@2.bind(17, "workspace_manager", 1, new id [unknown]@12)

[10:14:57.747] libwayland: disconnect from client 0x1bf0f0

Segmentation fault

[daiane_angolini]

Only remove X11 from DISTRO_FEATURES is not enough.

You should:

DISTRO_FEATURES_remove = "x11 wayland"

DISTRO_FEATURES += "directfb"

And start a new build folder

I tested DFB for imx6qsabresd 2 days ago using this pre-built image from master: http://ci.ossystems.com.br/public/fsl-community-bsp/master/122

If you have this board, you may have a taste....

[aurelienbouin]

I have just downloaded the wayland for sabresd http://ci.ossystems.com.br/public/fsl-community-bsp/master/122/wayland/imx6qsabresd/fsl-image-machin...

I mounted with NFS... with my own MX6 platform

It actually does exactly the same thing than it does with my own compile ... crash with a segfault

Are you sure thta is was for weston/wayland compilation ? I have tested also http://ci.ossystems.com.br/public/fsl-community-bsp/master/122/directfb/imx6qsabresd/fsl-image-machi...

There is no weston on it ...

[daiane_angolini]

What do you mean by "there is no weston on it"?

What are you expecting to find?

When I loaded the image I saw a grey big window, it's not cute, but it's there.

And I run several weston-* demos

And I got confused at some point in my last reply and pointed "directfb" and you're willing wayland. I'm sorry.

Please, let me know how can I see your seg-fault over here

[daiane_angolini]

And, only to make sure

are you:

export XDG_RUNTIME_DIR=/var/run/user/root

??

Take a look here, how I've been testing weston

https://github.com/Freescale/Documentation/commit/4419758640f2b4c1b8c249de1fc7fc84aa1672ab

(I'm sorry I don't have a better way to share this content yet)

[aurelienbouin]

Thank you for trying to help ...

After several test ... I finally decided to use the latest kernel from freescale 3.10.17 with my own device tree ...

And now everything is working ...

So there was something wrong with kernel 3.0.35 ...

[aurelienbouin]

I still do not have touchscreen ...

I am using ts2046 as touchscreen, it is well detected : input device ADS7846 Touchscreen, /dev/input/event0 is a touch device and with evtest coordinates are ok

But nothing happen when I touch the screen

When I connect a USB mouse a pointer appear on weston desktop...

Thank you for your help again ...

[daiane_angolini]

If evtest got the event. So the kernel is OK.

Do you have any weston log error message?

[aurelienbouin]

No log ...

Still not able to get any event from touchscreen ...

But it is working when I connect a USB mouse

And the touchscreen is working with ts_test ...

Thank you for your help

[YixingKong]

David, how is the progress on your issue? If it has been resolved, we are going to close the discussion in 3 days. If you still need help, please feel free to reply with an update to this discussion.

Thanks,

Yixing

[daiane_angolini]

Well

When I tested it for daisy it was working.

However, I tested it with my "standard" imx6qsabresd board.

[YixingKong]

David

Had your issue got resolved? If yes, we are going to close the discussion in 3 days. If you still need help, please feel free to reply with an update to this discussion.

Thanks,

Yixing

[daiane_angolini]

Hi davidwretman, I just tested core-image-weston in imx6qsabresd and it worked ok

Was you able to solve your problem already?

[jimmychan]

I am thinking you may need to config the weston.ini file. You may find an example from here:

https://github.com/search?q=weston&type=Repositories&ref=searchresults