on my test device, the wayland connection runs smoothly before create a
wl_buffer (in weston simple-dmabuf-drm.c
zwp_linux_buffer_params_v1_create()).
I do get the response from wayland server and
bind zwp_linux_dmabuf_v1_interface, and received dmabuf_listener callback
in dmabuf_format() for the
additonal information
1. on my x86 pc, it is Ubuntu18.04, the software version is lower than that
on device with fc30
2. with WAYLAND_DEBUG=1, some log as below
(create_window,826)#1
(create_dmabuf_buffer,686)dmabuf_fd: 8, stride: 1024, modifier: 0
Hi experts:
I want to debug somthing in mutter, the question is how to add log in
mutter?
the background is:
1.
on my platform(fc30), weston-simple-dmabuf-drm fail to run, it fails after
call zwp_linux_buffer_params_v1_create().
after export WAYLAND_DEBUG=1, I don't get clue.
"
I gave some try;
log shows on my desktop pc, but not on my test device.
I'm curious why dma_buf_bind () isn't triggered on my device; from client
side, I do see wayland server( mutter ) reports the supported color format.
is there any other place to handle dmabuf interface bind?
Jonas Ådahl
On Fri, Oct 11, 2019 at 06:55:42PM +0800, Halley Zhao via gnome-shell-list
wrote:
> Hi experts:
> I want to debug somthing in mutter, the question is how to add log in
> mutter?
>
> the background is:
> 1.
> on my platform(fc30), weston-simple-dmabuf-drm fail to run, it fails after
> call
On Fri, Oct 11, 2019 at 08:33:03PM +0800, Halley Zhao wrote:
> I gave some try;
> log shows on my desktop pc, but not on my test device.
> I'm curious why dma_buf_bind () isn't triggered on my device; from client
> side, I do see wayland server( mutter ) reports the supported color format.
> is
