Testing VC4 on rpi2 with wayland and weston, weston fail to start with drm

Hi, I want try VC4 on rpi2 with wayland on debian (I used Sid).
Following this howto:
http://dri.freedesktop.org/wiki/VC4/
I rebuild the kernel from 
https://github.com/anholt/linux/tree/vc4-kms-v3d-rpi2
Base config modified with: CONFIG_DRM_VC4=y and 
CONFIG_CMA_SIZE_MBYTES=128, full .config in attachment.
I did the 2 additions to rpi2 config.txt (full in attachment).
New kernel is working, in kern.log about drm I saw only this about drm:
Oct  1 11:11:16 jessie-rpi kernel: [    1.577017] [drm] Initialized drm 
1.1.0 20060810
I suppose that compiling with CONFIG_DRM_VC4=y should be present but I 
not saw line about.
I recompiled mesa 11.0.2-1 (from experimental with vc4 driver), full 
build log in attachment.

When I tried to start weston with drm it fails, I also tried to build it 
after rebuild mesa but nothing changes.
> Date: 2015-10-02 CEST
> [19:12:33.394] weston 1.9.0
>                http://wayland.freedesktop.org
>                Bug reports to: 
> https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.9.0
>                Build: 1.8.93-2-gb05cdb8 configure.ac: bump to version 
> 1.9.0 for the official release (2015-09-21 18:11:26 -0700)
> [19:12:33.395] OS: Linux, 4.1.0-v7, #1 SMP PREEMPT Wed Sep 30 18:13:42 
> CEST 2015, armv7l
> [19:12:33.395] Using config file '/home/pi/.config/weston.ini'
> [19:12:33.395] Loading module 
> '/usr/lib/arm-linux-gnueabihf/weston/drm-backend.so'
> [19:12:33.405] Output repaint window is 7 ms maximum.
> [19:12:33.405] initializing drm backend
> [19:12:33.405] no drm device found
> [19:12:33.406] fatal: failed to create compositor backend
I missed something or do something wrong?

The howto (http://dri.freedesktop.org/wiki/VC4/) can be improved also 
for wayland use please?



Thanks for any reply and sorry for my bad english.

_______________________________________________
mesa-users mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/mesa-users

# For more options and information see 
# http://www.raspberrypi.org/documentation/configuration/config-txt.md
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# VPU shouldn't handle V3D interrupts
mask_gpu_interrupt0=0x400
# VPU shouldn't smash our display setup.
avoid_warnings=2

gpu_mem=256