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

Eric Anholt <[email protected]> Tue, 06 Oct 2015 15:01:54 -0700
Newsgroups	gmane.comp.video.mesa3d.user
Message-ID	<[email protected]>
Fabio Fantoni <[email protected]> writes:

> Il 03/10/2015 00:50, Eric Anholt ha scritto:
>> Fabio Fantoni <[email protected]> writes:
>>
>>> 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.
>> You should also have various lines in dmesg about:
>>
>> [    3.185410] vc4-drm soc:vc4@7e4c0000: bound 20902000.hdmi (ops vc4_hdmi_ops)
>> [    3.200606] vc4-drm soc:vc4@7e4c0000: bound 20206000.pixelvalve (ops vc4_crtc_ops)
>> [    3.220583] vc4-drm soc:vc4@7e4c0000: bound 20207000.pixelvalve (ops vc4_crtc_ops)
>> [    3.232884] vc4-drm soc:vc4@7e4c0000: bound 20807000.pixelvalve (ops vc4_crtc_ops)
>> [    3.250938] vc4-drm soc:vc4@7e4c0000: bound 20400000.hvs (ops vc4_hvs_ops)
>> [    3.263385] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>> [    3.270162] [drm] No driver support for vblank timestamp query.
>> [    3.470743] Console: switching to colour frame buffer device 240x67
>> [    3.540179] vc4-drm soc:vc4@7e4c0000: fb0:  frame buffer device
>>
>> so something is going wrong and keeping you from probing.  There's at
>> least one problem in your config -- you can't have
>>
>> CONFIG_FB_BCM2708=y
>>
>> since you're trying to run a proper graphics driver, instead.  I don't
>> think that would keep vc4 from probing, though.  Maybe you wouldn't have
>> hit any of those "bound" messages because HDMI fails first due to your
>> config being missing:
>>
>> CONFIG_I2C_BCM2835=y
>>
>> I've added that to the wiki page.
>
> Thanks for your reply and all your work.
> I recompiled the kernel and retried, now screen show only and always 
> "initial image" but system with ssh is working.
> Strange thing is that I not found vc4-drm lines also in this case.
> Actual kernel .config and kern.log in attachment.
> I did something missed or wrong or there is problem or an unexpected case?
> I suppose is probable that also kernel parameters may change something 
> but I don't know if I must change something, actual cmdline.txt.
> config.txt already attached in previous mail is ok or other changes not 
> present in wiki are present?
> I also saw the strange thing that kernel is launched with addition 
> parameters (from kern.log) but I not know how and if can be a problem:
>> Oct  3 17:22:02 jessie-rpi kernel: [ 0.000000] Kernel command line: 
>> dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1360 bcm2708_fb.fbheight=768 
>> bcm2708.boardrev=0x2000010 bcm2708.serial=0x968d5adc 
>> smsc95xx.macaddr=B8:27:EB:8D:5A:DC bcm2708_fb.fbswap=1 
>> bcm2708.disk_led_gpio=47 bcm2708.disk_led_active_low=0 
>> sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000 
>> vc_mem.mem_size=0x3f000000  dwc_otg.lpm_enable=0 
>> console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootwait 
>> net.ifnames=1
>
> If you need more informations or tests tell me and I'll post them.

Looking through the logs again, I'm not sure what's going on.  At this
point I think I'd start adding DRM_INFO()s in vc4_drm_register(),
vc4_platform_drm_probe() and vc4_drm_bind() to start bisecting where
things are going wrong.

_______________________________________________
mesa-users mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/mesa-users
signature.asc (application/pgp-signature, 818 B)