Hello everyone,
As you may have seen, I was chosen to participate in GSOC
and work on your project.
I do need to apologize for not contacting you sooner, but
it was a busy week here (midterms week), so I didn't have
much time to think about anything else. I hope you understand.
I'll skip the int
On Apr 27, 2016, at 3:11 PM, Bryce Harrington wrote:
>
> On Tue, Apr 26, 2016 at 01:44:44PM -0500, Yong Bakos wrote:
>> From: Yong Bakos
>>
>> All event arg elements now have an appropriate summary attribute.
>> This was conducted mostly in response to the undocumented parameter
>> warnings gen
To avoid memory corruption or leak I store a copy of the device file
name in the fbdev-backend structure.
Signed-off-by: Benoit Gschwind
---
src/compositor-fbdev.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/src/compositor-fbdev.c b/src/compositor-fbdev.
Implement a "well" defined API to configure the fbdev backend.
Following and according to discussion about libweston API
Signed-off-by: Benoit Gschwind
---
Makefile.am| 5 -
src/compositor-fbdev.c | 45 +++--
src/compositor-fbdev.h | 49 ++
I hope I covered all remaining issues.
v3:
- update Makefile.am
- fix memory corruption/leak of device variable
- move transform configuration in the weston side
v2:
- add src/compositor-fbdev.h in the Makefile.am
- fix typo
Benoit Gschwind (3):
fbdev-backend: refactor configuration API
The output transform configuration is moved into weston and added to the
fbdev configuration structure.
Signed-off-by: Benoit Gschwind
---
src/compositor-fbdev.c | 17 -
src/compositor-fbdev.h | 2 ++
src/main.c | 8
3 files changed, 14 insertions(+), 13 de
On Tue, Apr 26, 2016 at 01:44:44PM -0500, Yong Bakos wrote:
> From: Yong Bakos
>
> All event arg elements now have an appropriate summary attribute.
> This was conducted mostly in response to the undocumented parameter
> warnings generated during 'make check'.
>
> Signed-off-by: Yong Bakos
I'd
Hello Pekka,
I was too confident when I submitted my patch, while I fixing the memory
corruption that you pointed out I found another issue:
composite-fbdev.c:504
section = weston_config_get_section(backend->compositor->config,
"output", "name"
On Wed, Apr 27, 2016 at 08:44:24AM -0500, Yong Bakos wrote:
> From: Yong Bakos
>
> Using --disable-gallium-egl generates a warning when running autogen.sh,
> because the option has been deprecated. See:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1128372
>
> Signed-off-by: Yong Bakos
Push
On Wed, Apr 27, 2016 at 08:44:24AM -0500, Yong Bakos wrote:
> From: Yong Bakos
>
> Using --disable-gallium-egl generates a warning when running autogen.sh,
> because the option has been deprecated. See:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1128372
>
> Signed-off-by: Yong Bakos
Conf
On Mon, Apr 25, 2016 at 7:22 PM, Peter Hutterer
wrote:
> 25a9f39 changed the range to [-1, 1] but that's incorrect for the distance
> values. Split the normalization up into two functions and make sure our
> distance range is correct.
>
> https://bugs.freedesktop.org/show_bug.cgi?id=95074
>
> And
Hi,
On 27-04-16 14:11, Benjamin Tissoires wrote:
On Wed, Apr 27, 2016 at 12:36 PM, Peter Hutterer
wrote:
Signed-off-by: Peter Hutterer
---
configure.ac | 4
src/libinput-private.h | 8
2 files changed, 12 insertions(+)
diff --git a/configure.ac b/configure.ac
index 5
Dear All,
I have a requirement to start the weston 1.8.0 with non-root user. I
tried it starting weston using following commands in systemd unit file
with "root" user (first to verify if all commands works) .
However with this it shows service status as "dead". Later intension
is to start with som
From: Yong Bakos
Using --disable-gallium-egl generates a warning when running autogen.sh,
because the option has been deprecated. See:
https://bugzilla.redhat.com/show_bug.cgi?id=1128372
Signed-off-by: Yong Bakos
---
building.html | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
On Tue, 17 Nov 2015 18:11:02 +0800
Jonas Ådahl wrote:
> This patch adds support for when the resulting pointer confinement region
> is not a rectangle.
>
> Support for this is implemented by converting the rectangles of the
> region into the regions outer border. Pointer motions are then clamped
On Wed, Apr 27, 2016 at 12:36 PM, Peter Hutterer
wrote:
> If a touch moves by more than 20mm within a single frame, reset the motion
> history, effectively discarding the movement. This is a relatively common bug
> and almost always needs a kernel fix, so add an explanatory page to the docs.
>
> S
On Wed, Apr 27, 2016 at 12:36 PM, Peter Hutterer
wrote:
> Signed-off-by: Peter Hutterer
> ---
> configure.ac | 4
> src/libinput-private.h | 8
> 2 files changed, 12 insertions(+)
>
> diff --git a/configure.ac b/configure.ac
> index 507b8e0..8c5b257 100644
> --- a/configu
On Wed, 27 Apr 2016 15:37:41 +0800
Jonas Ådahl wrote:
> Without this commit, wl_display_roundtrip_queue() is vulnerable to a
> race condition, causing the callback to be dispatched on the wrong
> queue.
>
> The race condition happens if some non-main thread calls
> wl_display_roundtrip_queue() w
On Wed, 27 Apr 2016 15:37:40 +0800
Jonas Ådahl wrote:
> proxy_destroy() is just the implementation of the atomic part of
> wl_proxy_destroy(), so lets make it static.
>
> Signed-off-by: Jonas Ådahl
> ---
> src/wayland-client.c | 5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> di
Signed-off-by: Peter Hutterer
---
configure.ac | 4
src/libinput-private.h | 8
2 files changed, 12 insertions(+)
diff --git a/configure.ac b/configure.ac
index 507b8e0..8c5b257 100644
--- a/configure.ac
+++ b/configure.ac
@@ -17,6 +17,10 @@ AC_SUBST([LIBINPUT_VERSION_MIN
If a touch moves by more than 20mm within a single frame, reset the motion
history, effectively discarding the movement. This is a relatively common bug
and almost always needs a kernel fix, so add an explanatory page to the docs.
Signed-off-by: Peter Hutterer
---
doc/Makefile.am
Don't move across the touchpad in one single event, it looks like a cursor
jump that we're trying to detect in future patches.
Signed-off-by: Peter Hutterer
---
test/gestures.c | 4 ++--
test/touchpad.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/test/gestures.c b/test
On Wed, 27 Apr 2016 15:37:39 +0800
Jonas Ådahl wrote:
> Test that doing wl_display.sync on a wrapped proxy with a special queue
> works as expected.
>
> Test that creating a wrapper on a destroyed but not freed proxy fails.
>
> Signed-off-by: Jonas Ådahl
> ---
>
> Changes since v1:
>
> - Ad
On Wed, 27 Apr 2016 15:37:38 +0800
Jonas Ådahl wrote:
> Using the libwayland-client client API with multiple threads with
> thread local queues are prone to race conditions.
>
> The problem is that one thread can read and dispatch events after
Hi Jonas,
this should say: "The problem is that on
On Tue, 26 Apr 2016 21:10:55 +0200
Benoit Gschwind wrote:
> Implement a "well" defined API to configure the fbdev backend.
> Following and according to discution about libweston API
> ---
> Signed-off-by: Benoit Gschwind
This S-o-b is on the wrong side of the '---'. git-am will drop if it is
be
Without this commit, wl_display_roundtrip_queue() is vulnerable to a
race condition, causing the callback to be dispatched on the wrong
queue.
The race condition happens if some non-main thread calls
wl_display_roundtrip_queue() with its thread local queue, and the main
thread reads and dispatches
proxy_destroy() is just the implementation of the atomic part of
wl_proxy_destroy(), so lets make it static.
Signed-off-by: Jonas Ådahl
---
src/wayland-client.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/src/wayland-client.c b/src/wayland-client.c
index f21b5f7..6de9
Using the libwayland-client client API with multiple threads with
thread local queues are prone to race conditions.
The problem is that one thread can read and dispatch events after
another thread creates the wl_callback object but before it sets the
queue. This could potentially cause the events
Test that doing wl_display.sync on a wrapped proxy with a special queue
works as expected.
Test that creating a wrapper on a destroyed but not freed proxy fails.
Signed-off-by: Jonas Ådahl
---
Changes since v1:
- Adepted to the API changes
- Added a test for ensuring that a wrapper for a des
On Tue, Apr 26, 2016 at 03:27:29PM -0700, Bryce Harrington wrote:
> Here's our schedule[1]:
>
> - 1.11-alpha around May 3rd. Major features done by this point.
>
> - 1.11-beta around May 17th.
>
> - 1.11-rc1 around May 24th.
>
> - 1.11.0 release around May 31st.
>
> Any changes to pro
30 matches
Mail list logo
