libinput 1.8.1 is now available. This release includes a build fix for the
meson build (together with better meson instructions) and two touchpad
fixes. The palm edge zone is slightly increased from 5% to 8% to avoid
accidental palm touches in the edges. On most modern touchpads that works
out to
In PostmarketOS we have added support for the Asus grouper device
(Google Nexus 7 2012 tablet), which uses ABGR.
This mode seems to be less common and previously it was not correctly
handled by calculate_pixman_format()
For more information, see:
Hi,
On 18 July 2017 at 14:14, Daniel Stone wrote:
> @@ -1607,14 +1635,29 @@ drm_output_repaint(struct weston_output *output_base,
> [...]
> + /* The legacy SetCrtc API doesn't allow us to do scaling, and the
> +* legacy PageFlip API doesn't allow us to do
Currently this doesn't actually really do anything, but will be used in
the future to track the state for both modeset and repaint requests.
Completion of the request gives us a single request-completion path for
both pageflip and vblank events.
Signed-off-by: Daniel Stone
Use a real drm_plane to back the scanout plane, displacing
output->fb_{last,cur,pending} to their plane-tracked equivalents.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 157 ++---
1 file changed, 91 insertions(+),
Rather than a more piecemeal approach at backend creation, explicitly
track connectors and CRTCs we do not intend to use, so we can ensure
they are disabled where appropriate.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 53
From: Pekka Paalanen
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.
Signed-off-by: Daniel Stone
If we have an unused CRTC or connector, explicitly disable it during the
end of the repaint cycle, or when we get VT-switched back in.
Signed-off-by: Daniel Stone
---
libweston/compositor-drm.c | 46 ++
1 file changed, 46
Track dynamic plane state (CRTC, FB, position) in separate structures,
rather than as part of the plane. This will make it easier to handle
state management later, and much more closely tracks what the kernel
does with atomic modesets.
The fb_last pointer previously used in drm_plane now becomes
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
drm_pending_state is currently skeletal, but will be used to retain
data through begin_repaint -> assign_planes -> repaint -> repaint_flush.
The flush and cancel functions are currently identical, only freeing the
state, but they will be used for different purposes in later patches.
Specifically,
Add a cache for DRM property IDs and values, and use it for the two
connector properties we currently update: DPMS and EDID.
As DRM property ID values are not stable, we need to do a name -> ID
lookup each run in order to discover the property IDs and enum values to
use for those properties.
From: Pekka Paalanen
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
Hi,
This is a re-send of a very limited part of the atomic series. This
pulls us through the state rework, up until the point of merging
DPMS tracking into output state tracking. I managed to find two separate
bugs in that today - and only fix one - so am going to hold off on
pushing that for more
All planes being displayed have a framebuffer. What makes 'fb_plane'
special is that it's being displayed as the primary plane by KMS.
Previous patchsets renamed this to 'primary_plane' to match the KMS
terminology, namely the CRTC's base plane, which is controlled by
drmModeSetCrtc in the legacy
On Thu, 6 Jul 2017 16:01:25 +0200
Olivier Fourdan wrote:
> This protocol aims at describing outputs in way which is more in line
> with the concept of an output on desktop oriented systems.
>
> Some information are more specific to the concept of an output for a
> desktop
On Fri, 14 Jul 2017 16:40:32 +0800
Jonas Ådahl wrote:
> This E-mail is quite long, but I tried to reply to some parts.
Hi Jonas, Olivier,
appreciated. :-)
TL;DR, I don't think there is anything in this email that would
actually be an opposition to the xdg-output protocol
> I was thinking more of e.g. Qt (or any other toolkit) that supports
> wl_shell, xdg_shell unstable v5 and v6 (albeit to a wildly differing
> extent sadly) and would now have to drop unstable v5 in order to
> support xdg_wm_base. Also, I think both KWin and Qt did only support
> unstable v5 until
From: Quentin Glidic
Now we keep track of serial->state association and we discard the states
that the client ignored.
Signed-off-by: Quentin Glidic
---
libweston-desktop/xdg-shell-v5.c | 45 +++-
From: Quentin Glidic
We were checking against the pending size, which lead some clients
(simple-egl) to crash because they sent a buffer before acknowledging
the latest configure event.
Signed-off-by: Quentin Glidic
Tested-by: Emmanuel
On 7/12/17 11:09 AM, Jonas Ådahl wrote:
On Wed, Jul 12, 2017 at 09:53:03AM +0200, Quentin Glidic wrote:
From: Quentin Glidic
Signed-off-by: Quentin Glidic
Reviewed-by: Jonas Ådahl
Thanks. Added Emmanuel Tb from
If the kernel sends us a button press for a button that is thought to be down
we have lost track of the state of the button. Ignore the button press event,
in the hope that the next release makes things right again.
A release event may be masked if another process grabs the device for some
period
22 matches
Mail list logo