Retain drm_plane tracking objects for all actual DRM planes when using
universal planes, not just overlay planes.
These are currently unused.
v2: Rename sprite_list to plane_list.
Signed-off-by: Daniel Stone dani...@collabora.com
---
src/compositor-drm.c | 37
Add awareness of, rather than support for, universal planes. Activate
the client cap when we start if possible, and if this is activated,
studiously ignore non-overlay planes. For now.
v2: Add asserts to be careful. Bump libdrm dependency version.
Signed-off-by: Daniel Stone
Change the type of cursor_plane from a weston_plane (base tracking
structure) to a drm_plane (wrapper containing additional DRM-specific
details), and make it a dynamically-allocated pointer.
Using the standard drm_plane allows us to reuse code which already deals
with drm_planes, e.g. a common
From: Pekka Paalanen pekka.paala...@collabora.co.uk
This moves the single sprite creation code from create_sprites() into a
new function. The readability clean-up is small, but my intention is to
write an alternate version of create_sprites(), and sharing the single
sprite creation code is
From: Pekka Paalanen pekka.paala...@collabora.co.uk
Makes create_output_for_connector() slightly easier to read.
Signed-off-by: Pekka Paalanen pekka.paala...@collabora.co.uk
Signed-off-by: Daniel Stone dani...@collabora.com
---
src/compositor-drm.c | 41 ++---
We already keep a GBM BO for the cursor plane, but also keep a DRM FB,
so we can reuse it for atomic modesetting.
Signed-off-by: Daniel Stone dani...@collabora.com
---
src/compositor-drm.c | 28 ++--
1 file changed, 26 insertions(+), 2 deletions(-)
diff --git
Dear Wayland developers:
I’m a soft engineer from MStar. I’m now considering the possibility of
integrating wayland into our software. Before doing that, I need to make sure
that wayland compositor could serve both 32bit client and 64bit client at the
same time. That’s to say -- wayland
Hi Tommy,
On 22 June 2015 at 15:17, tommy.sun (孫明勇) tommy@mstarsemi.com wrote:
I’m a soft engineer from MStar. I’m now considering the possibility of
integrating wayland into our software. Before doing that, I need to make
sure that wayland compositor could serve both 32bit client and
Building on the drm_plane work from earlier, use the new atomic
modesetting interface where available, including enabling overlay planes
by default.
It is still highly experimental, but manages to at least prove the
overall atomic modesetting and blob property interfaces.
This patch was jointly
If a plane is currently active on another output, don't steal it away.
Signed-off-by: Daniel Stone dani...@collabora.com
---
src/compositor-drm.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/compositor-drm.c b/src/compositor-drm.c
index c9071d2..fa520bc 100644
---
We make the differentiation where planes are an abstract framebuffer
with a position within a CRTC/output, and sprites are special cases of
planes that are neither the primary (base/framebuffer) nor cursor plane.
drm_sprite, OTOH, contains nothing that's actually specific to sprites,
and we end
Use a real drm_plane to back the primary plane, displacing
output-current and output-next to their plane-tracked equivalents.
v2: Remove extra output-{current,next} members. Add primary plane to
plane_list so it gets cleaned up.
Signed-off-by: Daniel Stone dani...@collabora.com
---
Track the view a plane is currently displaying, so we can avoid
needlessly recreating buffers.
Signed-off-by: Daniel Stone dani...@collabora.com
---
src/compositor-drm.c | 123 +++
1 file changed, 104 insertions(+), 19 deletions(-)
diff --git
From: Pekka Paalanen pekka.paala...@collabora.co.uk
Cut a chunk of code out from drm_output_set_cursor() and form a new
function for writing a cursor bo data from a weston_view with a wl_shm
buffer.
Add more asserts to verify the assumptions in there.
v2: Use
Instead of testing against a hardcoded 64x64 pixel size to see if a view
is suitable for promotion to a cursor plane, use our cursor_width and
cursor_height variables.
Signed-off-by: Daniel Stone dani...@collabora.com
---
src/compositor-drm.c | 7 ---
1 file changed, 4 insertions(+), 3
From: Pekka Paalanen pekka.paala...@collabora.co.uk
Refactor the code for choosing the initial mode for an output from
create_output_for_connector() to drm_output_choose_initial_mode().
This makes create_output_for_connector() slightly easier to read.
v2: Document everything.
Signed-off-by:
Reviewed-By: Derek Foreman der...@osg.samsung.com
On 21/06/15 02:25 PM, Mario Kleiner wrote:
Initialize output-native_mode with the initially chosen
mode for an output, so weston_output_mode_switch_to_native()
has something to work with and can switch back from temporary
selected modes to the
On Mon, Jun 22, 2015 at 12:37:43PM +0200, Andreas Pokorny wrote:
Hi,
On Mon, Jun 22, 2015 at 3:37 AM, Peter Hutterer peter.hutte...@who-t.net
wrote:
On Fri, Jun 19, 2015 at 03:24:38PM +0200, Andreas Pokorny wrote:
+ * */
+ if (orientation_info) {
+ if
On 06/21/2015 11:33 PM, Nobuhiko Tanibata wrote:
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
These tests are implemented on test suite framework, which provides
helper client.
Following features are tested for ivi-surface
- orientation
- dimension
- position
- destination
Dear Daniel：
Appreciate for your great help!
-邮件原件-
发件人: Daniel Stone [mailto:dan...@fooishbar.org]
发送时间: 2015年6月23日 0:46
收件人: tommy.sun (孫明勇)
抄送: wayland-devel@lists.freedesktop.org; security
主题: Re: question about wayland protocal compatibility between 32bit client and
64bit
It seems like prev
On Mon, Jun 22, 2015 at 1:02 PM, Giulio Camuffo giuliocamu...@gmail.com
wrote:
The backends used to have lots of code dealing with weston specific
configs.
To allow them to be used by other compositors with their own configurations
remove all the usage of weston_config
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
These tests are implemented on test suite framework, which provides
internal method validation.
Following features are tested for ivi-surface,
- destination_rectangle with bad parameter
- orientation with bad parameter
- dimension with
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
These tests are implemented on test suite framework, which provides
helper client.
Following features are tested for ivi-surface
- orientation
- dimension
- position
- destination rectangle
- source rectangle
Signed-off-by: Nobuhiko
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
These tests are implemented on test suite framework, which provides
helper client.
Following features are tested,
- ivi_layout_runner with basic_test_names[]
- surface with bad opacity
- destroy ivi/wl_surface and call get_surface
-
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
In previous code, it sends notification whenever setter calls. This
patch fixs that notification will not happens if there is no change of
properties by setter.
Signed-off-by: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
This interface is required for user to manage screens per IDs.
Signed-off-by: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
Acked-by: Pekka Paalanen pekka.paala...@collabora.co.uk
---
ivi-shell/ivi-layout-export.h | 7 +++
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
remove is not proper name beacause it destorys a layer. The name of
the api is changed from layer_remove to layer_destroy.
Signed-off-by: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
Reviewed-by: Pekka Paalanen
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
To get property changes of ivi_layer, callbacks can be registered.
However there was no API to remove a callback rather than removing all
callbacks by using layer_remove_notification.
layer_remove_notification_by_callback can do it.
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
ivi_shell_surface lifetime shall follow the ivi_surface protocol object
lifetime, and frees the ivi-id by destroying the ivi_layout_surface
from both wl_surface and ivi_surface destruction as the protocol specifies.
Signed-off-by:
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
Signed-off-by: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
Acked-by: Pekka Paalanen pekka.paala...@collabora.co.uk
---
ivi-shell/ivi-layout.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
Signed-off-by: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
Reviewed-by: Pekka Paalanen pekka.paala...@collabora.co.uk
---
ivi-shell/ivi-layout-private.h | 3 ++-
ivi-shell/ivi-layout.c | 54
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
Signed-off-by: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
Acked-by: Pekka Paalanen pekka.paala...@collabora.co.uk
---
ivi-shell/ivi-layout.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
To get property changes of ivi_surface, callbacks can be registered.
However there was no API to remove a callback rather than remove all
callbacks by using surface_remove_notification.
surface_remove_notification_by_callback can do it.
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
if a controller calls ivi_layout_layer_create_with_demenstion with a ID
which is already created before, the API returns exist ivi_layer.
However addtionally, it shall count up ref count to destroy ivi_layer
when ref count is 0. The
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
Previous code sends notification without event mask. So the notification
Signed-off-by: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
Reviewed-by: Pekka Paalanen pekka.paala...@collabora.co.uk
---
ivi-shell/ivi-layout.c | 6
Hi,
I am proposing a set of patches; ivi-shell test suite and bug fixes
found
by these test cases. This test suite is implemented based on following
test
framework.
http://lists.freedesktop.org/archives/wayland-devel/2015-March/020932.html
This test suite consists of four parts to verify
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
Signed-off-by: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
Acked-by: Pekka Paalanen pekka.paala...@collabora.co.uk
---
ivi-shell/ivi-layout.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
These tests are implemented on test suite framework, which provides
helper client.
Following features are tested,
- notification of adding ivi-surface
- notification of ivi-surface configure
- notification of creating ivi-surface
From: Nobuhiko Tanibata nobuhiko_tanib...@xddp.denso.co.jp
The TESTs in ivi_layout-test.c may have several server-side parts
(RUNNER_TEST in ivi_layout-test-plugin.c) each. Sometimes we need to
carry state from one RUNNER_TEST to another within one TEST, but not
across multiple TESTs. The correct
Hi I have been away for a while and quite busy so I did not get a
chance to response.
On Tue, Apr 28, 2015 at 3:46 AM, Bill Spitzak spit...@gmail.com wrote:
No, I absolutely 100% disagree.
Synchronized updating so things don't vibrate or shift is more important
than FPS. It is even stated as
On Mon, 15 Jun 2015 12:36:29 +0300
Pekka Paalanen ppaala...@gmail.com wrote:
On Fri, 12 Jun 2015 16:44:16 -0700
Bryce Harrington br...@osg.samsung.com wrote:
The code generates a cursor-data.h file, with licensing information.
Change this from the MIT X11 license to MIT Expat license for
On Fri, 12 Jun 2015 18:26:02 +0900
JoonCheol Park joonch...@gmail.com wrote:
The headless-backend.so was missing in available backend list
Signed-off-by: JoonCheol Park joonch...@gmail.com
---
src/compositor.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/compositor.c
On Wed, 10 Jun 2015 16:57:09 -0500
Derek Foreman der...@osg.samsung.com wrote:
Help messages were missing for some command line options.
Signed-off-by: Derek Foreman der...@osg.samsung.com
---
src/compositor.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
This change adds four new properties to touch events.
major: diameter of the touch ellipse along the major axis
minor: diameter perpendicular to major axis
pressure: a pressure value mapped into the range [0,1]
orientation: the angle between major and the x axis
Those values are optionally
Adds a device with various touch related axes and respective device features
to litest.
Signed-off-by: Andreas Pokorny andreas.poko...@canonical.com
---
test/Makefile.am | 1 +
test/litest-touch-screen.c | 135 +
test/litest.c
This change adds strict axis_replacemnt and litest_touch_move_extended
and litest_touch_down_extended to simulate changes to other axes during
touch down and move events.
Signed-off-by: Andreas Pokorny andreas.poko...@canonical.com
---
test/litest.c | 95
Hi,
On Mon, Jun 22, 2015 at 3:37 AM, Peter Hutterer peter.hutte...@who-t.net
wrote:
On Fri, Jun 19, 2015 at 03:24:38PM +0200, Andreas Pokorny wrote:
+ * */
+ if (orientation_info) {
+ if (orientation_info-maximum == 1
+ orientation_info-maximum ==
Hi,
On 22-06-15 06:54, Peter Hutterer wrote:
No functional change, other than that we check for status codes now too.
In tests that don't specifically check the interface itself, a short
enable_tap() or disable_tap() is a lot more obvious to parse for the reader.
Signed-off-by: Peter Hutterer
Hi,
On 22-06-15 04:03, Peter Hutterer wrote:
Multiple devices plugged into the same USB hub have the same
PHYS path and are assigned to the same group.
Prepend the content of the PRODUCT env to the phys path, this at least ensures
that different devices are never grouped together.
This commits starts to separate the libweston code from the weston
specific code. As such, the main() is moved, together with signals
handling and configuration handling.
---
Makefile.am | 1 +
src/compositor.c | 801 +---
src/weston.c |
Hi,
This is the new revision of libweston, with quite many changes
after Pekka's comments:
- no more weston_compositor_init/fini, but weston_compositor_create/destroy.
in a far future we may manage to make weston_compositor an opaque struct.
- all the backends are now loaded through a common
This commit adds three new exported functions:
- weston_compositor_create() returns a new weston_compositor instance,
initializing it as the now removed weston_compositor_init() did.
- weston_compositor_exit(compositor) asks the compositor to tear
down by calling the compositor's exit vfunc which
The backends used to have lots of code dealing with weston specific configs.
To allow them to be used by other compositors with their own configurations
remove all the usage of weston_config from the backends code and move it
in weston.c. The backends are now initialized with the new
the --enable/disable-weston-binaries enables or disables the creation
of 'weston', 'weston-launch' and all the binaries that are
installed in $prefix/lib/libexec. This allows, together with
--enable-clients, to only build the libraries, making possible to
build and install different libweston
Instead of the central weston_config pointer we now store it in some
module-specific pointers. This way we can remove them one by one.
---
desktop-shell/shell.c | 10 +---
desktop-shell/shell.h | 1 +
fullscreen-shell/fullscreen-shell.c | 3 ++-
---
Makefile.am | 2 +-
src/compositor.h | 5 ++--
src/log.c| 69 ++---
src/weston.c | 78
4 files changed, 89 insertions(+), 65 deletions(-)
diff --git a/Makefile.am
Move the code launching the screenshooter client and implementing
the screenshot protocol out of libweston, and make screenshooter.c
a generic way to hook screenshoot protocols into weston.
A new header weston.h is added, with an entry point for the shells
to init the screenshooter.
---
It uses the weston_client_launch API, which is not available in
libweston.
---
Makefile.am | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/Makefile.am b/Makefile.am
index b1d1044..2d24bcc 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -79,7 +79,6 @@
The library is versioned, so a -N is appended to its name, e.g. libweston-1.so.
The same is done for the pc file, the include and lib/weston dirs.
This allows multiple libweston versions to be installed together.
---
Makefile.am | 59 ++-
libweston still used those functions internally, so it was not linkable
yet by other compositors.
---
src/compositor.c | 144 --
src/weston.c | 145 +++
2 files changed, 145 insertions(+),
When edge scrolling is triggered by exceeding the motion threshold (5mm) we
sent the whole delta as the first scroll event, causing a big jump.
Instead, send only the current delta. This effectively introduces a 5mm dead
zone when edge scrolling, still better than the jump.
Reduce the dead zone/initial jump
https://bugs.freedesktop.org/show_bug.cgi?id=90990
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/evdev-mt-touchpad-edge-scroll.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/evdev-mt-touchpad-edge-scroll.c
2015-06-23 3:52 GMT+03:00 Bill Spitzak spit...@gmail.com:
It seems like prev
On Mon, Jun 22, 2015 at 1:02 PM, Giulio Camuffo giuliocamu...@gmail.com
wrote:
The backends used to have lots of code dealing with weston specific
configs.
To allow them to be used by other compositors with their
On Tue, 16 Jun 2015 14:07:32 +0300
Pekka Paalanen ppaala...@gmail.com wrote:
From: Pekka Paalanen pekka.paala...@collabora.co.uk
This is a follow-up for the patch that removed weston-screensaver. The
aim is to clean up shell.c a little by removing non-essential
components. Vanilla Weston
64 matches
Mail list logo
