This is the beta for the upcoming 3.00 release.
Since the alpha there have been several refactors of libweston's output
interface uncluding unexporting two symbols,
weston_compositor_add_output and weston_output_update_matrix. ivi-shell
received some code cleanup and removal of the layer_set_orie
Here is the beta for the upcoming 1.14 release.
There have been no changes since the alpha.
Bryce Harrington (1):
configure.ac: bump to version 1.13.92 for the beta release
git tag: 1.13.92
https://wayland.freedesktop.org/releases/wayland-1.13.92.tar.xz
MD5: 2dbbaa14d4572b57939af7c3f
On 2017-07-25 04:39 PM, Derek Foreman wrote:
This is easily noticed as a leaked fd on every VC switch.
Signed-off-by: Derek Foreman
---
libweston/libinput-seat.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/libweston/libinput-seat.c b/libweston/libinput-seat.c
inde
This is easily noticed as a leaked fd on every VC switch.
Signed-off-by: Derek Foreman
---
libweston/libinput-seat.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/libweston/libinput-seat.c b/libweston/libinput-seat.c
index 8cf5666b..953f6205 100644
--- a/libweston/libin
We still need to close fds passed to us - or we leak quite a few fds
on VC switch.
Regression, originally fixed in 8f5acc2f3a29c3831af4ddd6bed57f703c98dc77
and re-broken in commit 72dea06d7952e3ce8dd8057f7106186da4fa2678
but only for the logind launcher.
Signed-off-by: Derek Foreman
---
libwest
On Tue, Jul 25, 2017 at 7:34 AM, Peter Hutterer
wrote:
> The lid dispatch interface is a one-trick pony and can only handle SW_LID. It
> ignores other switches but crashes on any event type other than EV_SW and
> EV_SYN. Disable those types so we just ignore the event instead of asserting.
>
> htt
The lid dispatch interface is a one-trick pony and can only handle SW_LID. It
ignores other switches but crashes on any event type other than EV_SW and
EV_SYN. Disable those types so we just ignore the event instead of asserting.
https://bugs.freedesktop.org/show_bug.cgi?id=100057
Signed-off-by:
On Tue, Jul 25, 2017 at 7:26 AM, Jonas Ådahl wrote:
> On Tue, Jul 25, 2017 at 06:42:34AM -0600, Matt Hoosier wrote:
> > I'd find it a little bit inconvenient for the title, class, and app-id to
> > be treated as buffered state. They make a great poor-man's way of
> > identifying surfaces for embe
Hi Pekka, hi Emre,
the test is implemented and also tested.
Best regards
Michael Teyfel
Engineering Software Base (ADITG/ESB)
Tel. +49 5121 49 6932
-Original Message-
From: Ucan, Emre (ADITG/ESB)
Sent: Montag, 24. Juli 2017 16:34
To: Pekka Paalanen
Cc: Eugen Friedrich; wayland-devel@
Two cases are tested: success and fail case of the screen-remove-layer API.
Signed-off-by: Michael Teyfel
---
tests/ivi_layout-internal-test.c | 62
1 file changed, 62 insertions(+)
diff --git a/tests/ivi_layout-internal-test.c b/tests/ivi_layout-interna
On Tue, Jul 25, 2017 at 06:42:34AM -0600, Matt Hoosier wrote:
> I'd find it a little bit inconvenient for the title, class, and app-id to
> be treated as buffered state. They make a great poor-man's way of
> identifying surfaces for embedded systems that implement simple layer
> management policies
On Mon, 24 Jul 2017 18:07:55 +0300
Pekka Paalanen wrote:
> From: Pekka Paalanen
>
>
> Hi,
>
> this is the v2 of the series, only minor changes as listed in each patch plus
> rebase.
>
> While working on Weston core reactoring towards clone mode support:
> https://phabricator.freedesktop.org/
On Mon, 24 Jul 2017 18:09:12 +0200
Armin Krezović wrote:
> On 24.07.2017 17:07, Pekka Paalanen wrote:
> > From: Pekka Paalanen
> >
> > Trying to make it more readable. Things that happen in the same step are
> > kept in the same paragraph.
> >
> > v2: talk about "list of enabled outputs"
> >
I'd find it a little bit inconvenient for the title, class, and app-id to
be treated as buffered state. They make a great poor-man's way of
identifying surfaces for embedded systems that implement simple layer
management policies without wholesale adopting IVI shell (whose lack of
wl_shell makes it
On Tue, 25 Jul 2017 15:13:56 +0300
Pekka Paalanen wrote:
> On Tue, 25 Jul 2017 11:50:58 +0100
> Daniel Stone wrote:
>
> > Hi,
> >
> > On 25 July 2017 at 11:28, Pekka Paalanen wrote:
> > > On Mon, 24 Jul 2017 18:13:39 +0100
> > > Daniel Stone wrote:
> > >> > I believe this should shorte
On Tue, 25 Jul 2017 11:50:58 +0100
Daniel Stone wrote:
> Hi,
>
> On 25 July 2017 at 11:28, Pekka Paalanen wrote:
> > On Mon, 24 Jul 2017 18:13:39 +0100
> > Daniel Stone wrote:
> >> > I believe this should shorten to: "Call this for every DRM object
> >> > individually once."
> >> >
> >> > Th
On Tue, 25 Jul 2017 14:44:29 +0300
Pekka Paalanen wrote:
> On Tue, 25 Jul 2017 18:39:56 +0800
> Jonas Ådahl wrote:
>
> > Add a --visibility flag that enables the user to tweak the visibility
> > of the symbols generated by wayland-scanner. Three alternatives are
> > exposed:
> >
> > 'export':
On Tue, 25 Jul 2017 18:39:57 +0800
Jonas Ådahl wrote:
> Test that it is possible to inline the protocol 'code' file generated
> by wayland-scanner in the source code files using it.
>
> Signed-off-by: Jonas Ådahl
> ---
> .gitignore| 5 ++
> Makefile.am
On Tue, 25 Jul 2017 18:39:56 +0800
Jonas Ådahl wrote:
> Add a --visibility flag that enables the user to tweak the visibility
> of the symbols generated by wayland-scanner. Three alternatives are
> exposed:
>
> 'export': as has always been done up until now, export the symbols
> using WL_EXPORT,
Hi,
On 25 July 2017 at 11:28, Pekka Paalanen wrote:
> On Mon, 24 Jul 2017 18:13:39 +0100
> Daniel Stone wrote:
>> > I believe this should shorten to: "Call this for every DRM object
>> > individually once."
>> >
>> > The language about status changes is probably a remnant of the value
>> > cachi
On Tue, 25 Jul 2017 11:34:33 +0200
Michael Teyfel wrote:
> Signed-off-by: Michael Teyfel
> ---
> ivi-shell/ivi-layout-export.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/ivi-shell/ivi-layout-export.h b/ivi-shell/ivi-layout-export.h
> index afbb110..277ac59 100644
Test that it is possible to inline the protocol 'code' file generated
by wayland-scanner in the source code files using it.
Signed-off-by: Jonas Ådahl
---
.gitignore| 5 ++
Makefile.am | 32 -
tests/data/tiny.xml | 38 ++
Add a --visibility flag that enables the user to tweak the visibility
of the symbols generated by wayland-scanner. Three alternatives are
exposed:
'export': as has always been done up until now, export the symbols
using WL_EXPORT, making making them exposed externally. This is the
default in order
On Mon, 24 Jul 2017 18:13:39 +0100
Daniel Stone wrote:
> Hi Pekka,
> I've made a mental note to make as careful passes over the
> documentation as the code before I send for review ...
>
> On 19 July 2017 at 15:43, Pekka Paalanen wrote:
> > On Tue, 18 Jul 2017 14:14:25 +0100
> > Daniel Stone w
Hi Pekka, hi Emre,
I send the patch to wayland-devel ML.
Best regards
Michael Teyfel
Engineering Software Base (ADITG/ESB)
Tel. +49 5121 49 6932
-Original Message-
From: Ucan, Emre (ADITG/ESB)
Sent: Montag, 24. Juli 2017 16:52
To: Pekka Paalanen
Cc: wayland-devel@lists.freedesktop.or
Signed-off-by: Michael Teyfel
---
ivi-shell/ivi-layout-export.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ivi-shell/ivi-layout-export.h b/ivi-shell/ivi-layout-export.h
index afbb110..277ac59 100644
--- a/ivi-shell/ivi-layout-export.h
+++ b/ivi-shell/ivi-layout-export.h
@
On Tue, 25 Jul 2017 15:25:58 +0800
Jonas Ådahl wrote:
> On Mon, Jul 24, 2017 at 02:16:04PM +0300, Pekka Paalanen wrote:
> > On Mon, 3 Jul 2017 17:16:45 +0800
> > Jonas Ådahl wrote:
> >
> > > Two different protocols may use interfaces with identical names.
> > > Implementing support for both
On Tue, 25 Jul 2017 10:54:41 +0530
saikishore wrote:
> Hi,
> I am trying to enable wayland to arm64 embedded platform and i use
> buildroot to build the rootfs and use kernel 4.1.
>
> I have builded wayland 1.7 & weston 1.7 packages using buildroot and
> enabled in rootfs and no kernel changes.
On Mon, Jul 24, 2017 at 02:16:04PM +0300, Pekka Paalanen wrote:
> On Mon, 3 Jul 2017 17:16:45 +0800
> Jonas Ådahl wrote:
>
> > Two different protocols may use interfaces with identical names.
> > Implementing support for both those protocols would result in symbol
> > clashes, as wayland-scanner
29 matches
Mail list logo
