What kind of video card hardware do you have? (intel/nvidia/amd), or are you
using a VM?
Did you try with a framebuffer option?
What part does it actually hang at?
On Tuesday, October 18, 2016 11:37:29 AM EDT you wrote:
> Bug don't response
>
> DanielTorres
> On Oct 16, 2016 12:18 AM, "nerdopoli
---
compositor/main.c | 13 +
weston.ini.in | 1 +
2 files changed, 14 insertions(+)
diff --git a/compositor/main.c b/compositor/main.c
index 8028ec3..6cd2a25 100644
--- a/compositor/main.c
+++ b/compositor/main.c
@@ -1095,6 +1095,8 @@ configure_input_device(struct weston_composi
This adds support for enabling/disabling natural scrolling
via a boolean in weston.ini:
[libinput]
natural_scroll=true
Signed-off-by: Jiayi Zhao
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/l
On Oct 18, 2016, at 7:23 AM, Olivier Fourdan wrote:
>
> When using a wl_global, a server may need to retrieve the associated
> wl_interface and user data.
>
> Add a couple of convenient functions wl_global_get_interface() and
> wl_global_get_user_data() for this purpose.
>
> Signed-off-by: Oliv
On Oct 18, 2016, at 7:23 AM, Olivier Fourdan wrote:
>
> Test if the global filter is effectively filtering out the global when
> the filter returns false.
>
> Signed-off-by: Olivier Fourdan
> Reviewed-by: Yong Bakos
> ---
This v remains
Reviewed-by: Yong Bakos
yong
> v3: split out as its
On Oct 18, 2016, at 7:23 AM, Olivier Fourdan wrote:
>
> Add a new API to let compositor decide whether or not a wl_global
> should be advertised to the clients via wl_registry_bind() or
> display_get_registry()
>
> By using its own filter, the compositor can decide which wl_global would
> be lis
On Oct 18, 2016, at 2:05 AM, Pekka Paalanen wrote:
>
> On Tue, 27 Sep 2016 23:27:00 +0200
> Dima Ryazanov wrote:
>
>> I think I actually know the point of the test.
>>
>> It tries to verify that size, alloc, and data were initialized to 0, rather
>> than left uninitialized - but the difficulty
Test if the global filter is effectively filtering out the global when
the filter returns false.
Signed-off-by: Olivier Fourdan
Reviewed-by: Yong Bakos
---
v3: split out as its own commit
v4: Follow up on Jonas' comments:
assert(hi.has_data_offer == false) instead of assert(hi.has_data_of
Add a new API to let compositor decide whether or not a wl_global
should be advertised to the clients via wl_registry_bind() or
display_get_registry()
By using its own filter, the compositor can decide which wl_global would
be listed to clients.
Compositors can use this mechanism to hide their ow
When using a wl_global, a server may need to retrieve the associated
wl_interface and user data.
Add a couple of convenient functions wl_global_get_interface() and
wl_global_get_user_data() for this purpose.
Signed-off-by: Olivier Fourdan
---
v3: split out as its own commit
v4: Rebase against
On Tue, 18 Oct 2016 08:37:56 -0400 (EDT)
Olivier Fourdan wrote:
> Hi Pekka,
>
> > sorry for taking so long to reply.
>
> Now it's my turn to apologize, I saw your email and then forgot about it!
>
> > A recap from earlier emails as I understood them:
> >
> > - This patch adds a callback in
Hi Pekka,
> sorry for taking so long to reply.
Now it's my turn to apologize, I saw your email and then forgot about it!
> A recap from earlier emails as I understood them:
>
> - This patch adds a callback in libwayland-server's wl_registry
> implementation, that will be called every time a)
On Sat, 17 Sep 2016 15:04:32 -0700
Yong Bakos wrote:
> From: Yong Bakos
>
> Add doxygen comment blocks so these annotations are documented in the html
> documentation.
>
> Signed-off-by: Yong Bakos
> ---
> src/wayland-util.h | 13 ++---
> 1 file changed, 10 insertions(+), 3 deletions
On Tue, 27 Sep 2016 13:03:46 -0500
Yong Bakos wrote:
> From: Yong Bakos
>
> This series adds documentation to wl_array and its methods.
>
> There is one implementation change: defining an invalid pointer address, and
> setting the `data` pointer to the invalid pointer address after free, in
>
On Tue, 27 Sep 2016 23:27:00 +0200
Dima Ryazanov wrote:
> I think I actually know the point of the test.
>
> It tries to verify that size, alloc, and data were initialized to 0, rather
> than left uninitialized - but the difficulty is that uninitialized memory
> is often already filled with 0s.
15 matches
Mail list logo