- Dec 18, 2015
-
-
Sjoerd Simons authored
Currently the fbdev compositor has its own shadow buffer when rendering with pixman, causing the following copies to occur: [pixman shadow buffer] -> [fbdev shadow buffer] -> [fbdev hardware] As the pixman render already does all output translation when compositing the intermediate shadow buffer really isn't needed, so drop it. As a side-effect this fixes updating the fbdev hardware for outputs not starting at 0x0. Signed-off-by:
Sjoerd Simons <sjoerd.simons@collabora.co.uk> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk> Reviewed-by:
David FORT <contact@hardening-consulting.com> Reviewed-by:
Derek Foreman <derekf@osg.samsung.com> Tested-by:
Derek Foreman <derekf@osg.samsung.com>
-
Fall back to not showing anything as before if we don't have a compositor with wl_output new enough (version 2 or newer). Signed-off-by:
Jonny Lamb <jonny.lamb@collabora.co.uk> Reviewed-by:
Daniel Stone <daniels@collabora.com> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
- Dec 14, 2015
-
-
It shows ivi applications at screensa randomly. Signed-off-by:
Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
It shows ivi applications in fullscreen per screen like, The first screen: Application 1,4,5,6,,,, The seconed screen: Application 2, The third screen: Application 3 Thie mode assigns one application to each screen at first. And remaind applications more than screens will be assigned to the first screen. Signed-off-by:
Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
It shows 2 ivi application in a screen at side-by-side. It moves additinal application more than 2xN to next screen N+1. Signed-off-by:
Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
It shows 8 ivi applications in a screen at tiling. It moves additional application more than 8xN to next screen N+1. Signed-off-by:
Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
To locate surfaces of application on multi screens, multi layers are created baseod on application-layer-id + base-layer-id-offset x N. Signed-off-by:
Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
A surface ID for layer of background/panel image is set by key: background-id or panel-id at weston.ini. To support multi screens, it also support offset, surface-id-offset, to offset the surface ID to next ID for a layer on next screen. According to the above key, hmi-controller and ivi-shell-user-interface who increments the number of screens per notification of wl_output. crate surface and draw background/panel image on multi surface on screens. Signed-off-by:
Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
A layer ID for screen is set by key: base-layer-id at weston.ini. To support multi screens. It also support offset to offset the layer ID to next ID for next screen. For example, base-layer-id=1000 base-layer-id-offset=10000 Layer id for screen 0: 1000 Layer id for screen 1: 11000 Layer id for screen 2: 21000 To support multi screen, create layers for background and panel bar which located in the below per screens. At the moment, it is only layers. Surfaces to be created at next patch in the patch set. Signed-off-by:
Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
- get screens from weston core - provide screens as internel method - the iviscn is stored in array inverse order in index. Signed-off-by:
Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
A weston_surface is transformed to multi screen coordinate, global coordinate by matrix:m now. Additionally, a mask needs to be calucated, taking account into, - multi screen coordination: a destination rectangle of layer in the coordination is easily calcurated by adding weston_output.{x,y} in simple. This is because there is no scaled and rotated transformation. - intersect inside of a screen the layer is assigned to. This is because overlapped region of weston surface in another screen shall not be displayed according to ivi use case. Signed-off-by:
Nobuhiko Tanibata <nobuhiko_tanibata@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
In single screen, the coordinates of layer local coordinates are the same as global coordinates. However, to support multi screens, the layer-local coordinates shall be transformed to multi screen coordinates, which is global coordinates. The abosolute coordinates of a screen in global stored in (x,y) of output of its weston output so it shall be used to transform layer-local to global coordinates. Signed-off-by:
Nobuhiko Tanibata <nobuhiko_tanibata@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
For multi screen support, ivi_layout_screen to be taken account into property change in commitChanges. Property change is now done in update_prop so to consider ivi_screen property for caluculating transform of weston surface, ivi_layout_screen is added as a parameter of update_prop. However, update_prop of weston_view of a ivi_surface can not be done even if it is set on a screen. The propoerty change shall be done only when a visibility of ivi_surface or ivi_layer which contains the ivi_surface is ON. Such a condition shall be checked at commit_changes as well to avoid calling update_prop, which actually updates weston_views. Signed-off-by:
Nobuhiko Tanibata <nobuhiko_tanibata@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
Similar with Desktop shell, set activate to weston surface which is left-clicked by pointer or touched. This is needed to focus it with a seat. Without this, a feature who gets activated weston surface by using weston_surface_get_main_surface doesn't work correctly because it can not get correct focused weston surface. For example, input-panel uses weston_surface_get_main_surface to get a weston surface. With this weston surface, it get a member: output to decide which output shall show a input-panel, software keyboard. Without activation, input-panel-ivi can not find a correct output which shows e.g. weston-editor who uses input-method. Signed-off-by:
Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk> Tested-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
- Dec 08, 2015
-
-
Derek Foreman authored
Adds support for touch devices to the wayland backend. Signed-off-by:
Derek Foreman <derekf@osg.samsung.com> Reviewed-by:
Daniel Stone <daniels@collabora.com>
-
Derek Foreman authored
We already have notify_touch(), notify_touch_frame(). We need notify_touch_cancel() to implement touch in the weston wayland backend properly. Reviewed-by:
Daniel Stone <daniels@collabora.com> Signed-off-by:
Derek Foreman <derekf@osg.samsung.com>
-
Derek Foreman authored
We should use wl_*_release when available instead of destroy, and we should update weston's internal input tracking with weston_seat_releases Reviewed-by:
Daniel Stone <daniels@collabora.com> Signed-off-by:
Derek Foreman <derekf@osg.samsung.com>
-
Derek Foreman authored
I'll be using this in a follow up patch that adds touch input to weston's wayland backend. Reviewed-by:
Daniel Stone <daniels@collabora.com> Signed-off-by:
Derek Foreman <derekf@osg.samsung.com>
-
- Dec 05, 2015
-
-
Jussi Kukkonen authored
This is useful for reproducable builds. Signed-off-by:
Jussi Kukkonen <jussi.kukkonen@intel.com> Reviewed-by:
Bryce Harrington <bryce@osg.samsung.com>
-
- Dec 03, 2015
-
-
Chris Michael authored
Patch updated to remove dead lines as suggested by Daniel Stone Signed-off-by:
Chris Michael <cp.michael@samsung.com> Reviewed-by:
Daniel Stone <daniels@collabora.com>
-
Derek Foreman authored
Signed-off-by:
Derek Foreman <derekf@osg.samsung.com> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
Derek Foreman authored
Add a new flag for testing damage in buffer co-ordinates Signed-off-by:
Derek Foreman <derekf@osg.samsung.com> Acked-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
Derek Foreman authored
Add an implementation of wl_surface.damage_buffer, similar to wl_surface.damage except it uses buffer co-ordinates. Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk> Signed-off-by:
Derek Foreman <derekf@osg.samsung.com>
-
- Dec 02, 2015
-
-
Emmanuel Gil Peyrot authored
This allows renderers to use that struct to create their own dmabufs, in case they can’t import the one provided by the client directly but know how to convert it into a format they can render. Signed-off-by:
Emmanuel Gil Peyrot <emmanuel.peyrot@collabora.com> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk> Reviewed-by:
Daniel Stone <daniels@collabora.com> Differential Revision: https://phabricator.freedesktop.org/D332 Reviewed-by:
Bryce Harrington <bryce@osg.samsung.com> Reviewed-by:
Derek Foreman <derekf@osg.samsung.com>
-
- Dec 01, 2015
-
-
Chris Michael authored
The function 'weston_surface_to_buffer' is unused by compositor and clients inside weston, so it should be safe to remove this function Signed-off-by:
Chris Michael <cp.michael@samsung.com> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
Derek Foreman authored
Rounding both corners of the rectangle down can result in a 0 width/height rectangle before passing to weston_transformed_rect. This showed up as missing damage in weston-simple-damage (the bouncing ball would leave green trails when --use-viewport was used) Reviewed-by:
Daniel Stone <daniels@collabora.co.uk> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk> Signed-off-by:
Derek Foreman <derekf@osg.samsung.com>
-
- Nov 30, 2015
-
-
Chris Michael authored
This function is unused throughout the entire weston source tree, so remove it. It seems that the "load_backend" function is the one currently being used Signed-off-by:
Chris Michael <cp.michael@samsung.com> Reviewed-by:
Derek Foreman <derekf@osg.samsung.com>
-
Derek Foreman authored
We've been setting up the viewport by moving the start pointer of the draw buffer, but later when we want to post damage in buffer co-ordinates we'll need to keep track of the x,y offsets anyway. Signed-off-by:
Derek Foreman <derekf@osg.samsung.com> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
- Nov 27, 2015
-
-
Derek Foreman authored
libwayland-server protects us from invalid serial numbers by posting an error already. MIN() is for clients when selecting interface versions. Signed-off-by:
Derek Foreman <derekf@osg.samsung.com> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
Pekka Paalanen authored
Fix a regression introduced by be428b38 which accidentally removed the global-to-output space conversion. Signed-off-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk> Cc: Derek Foreman <derekf@osg.samsung.com> Cc: Daniel Stone <daniels@collabora.com> Reviewed-by:
Derek Foreman <derekf@osg.samsung.com> Tested-by:
Derek Foreman <derekf@osg.samsung.com>
-
It breaks from wl_list_for_each of screens when the frist screen found. Signed-off-by:
Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
This is potential bug when it supports several screens. If view_list is initilized here, the views, which are set by the previous screen, are cleared. So View list shall be initilized in front of wl_list_for_each of all screens. Signed-off-by:
Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
In just previous wl_list_for_each_safe, list of layer in a screen is cleaned up. And then, the list is re-constructed from pending.layer_list. In this re-construction, if order.link of a layer were inserted into a screen whose number is later one of current screen, the order.link will inserted into layer_list of two screens. This shall be avoided. However, if we want to implement a feature to allow a layer to be added to multiple screens. A layer shall have several order.link per screens. So, I marked here as TODO. Signed-off-by:
Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
It just return the first screen found in screen list. Signed-off-by:
Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
The required version only corresponds to version of mesa implementation. This mesa version requirement causes configure errors, when weston is configured for a different egl implementation than mesa. Because the version of the egl drivers are not alligned to the mesa version. Therefore, I deleted the version controlling for egl, so that weston can be configured for a different egl implementation. Signed-off-by:
Emre Ucan <eucan@de.adit-jv.com> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
- Nov 26, 2015
-
-
Chris Michael authored
commit 57388e44 accidentally changed the comment in compositor.c::subsurface_commit_to_cache Signed-off-by:
Chris Michael <cp.michael@samsung.com> Reviewed-by:
Derek Foreman <derekf@osg.samsung.com>
-
Derek Foreman authored
If we pass negative height or width on to pixman we get error messages in the log. Also, if width or height is 0, there's no damage, so we can early return for that too. Signed-off-by:
Derek Foreman <derekf@osg.samsung.com> Reviewed-by:
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
-
- Nov 25, 2015
-
-
Jonas Ådahl authored
Signed-off-by:
Jonas Ådahl <jadahl@gmail.com>
-
- Nov 24, 2015
-
-
Derek Foreman authored
Make sure a view's transform is viable for a cursor plane and then actually apply it before setting the cursor plane location. Now if a subsurface ends up in the cursor plane, the plane will be properly positioned. Signed-off-by:
Derek Foreman <derekf@osg.samsung.com> Reviewed-by:
Daniel Stone <daniels@collabora.com>
-
Yong-iL Joh authored
when weston is running on qemux86 device, there is an error with following. [08:02:07.897] launching '/usr/lib/weston/weston-ivi-shell-user-interface' [08:02:08.201] /usr/lib/weston/weston-ivi-shell-user-interface died on signal 11 this is caused by type mismatch, and it does occur on qemux86-64 Signed-off-by:
Yong-iL Joh <yong-il.joh@windriver.com> Acked-by:
Daniel Stone <daniel@fooishbar.org> Reviewed-by:
Bryce Harrington <bryce@osg.samsung.com>
-