Hello Pekka,
Sorry for the delay in response, I was OOO. I had a quick syncup with
Ankit, where he told me about the discussions you guys had, over this
topic.
Please find my comments inline.
On 9/12/2017 2:49 PM, Pekka Paalanen wrote:
On Mon, 11 Sep 2017 14:36:13 +0530
"Sharma, Shashank" w
Previously we only listened for events on the first one to come up, based on
the assumption that there can only be one internal keyboard. The Razer Blade
laptop keyboards come with with multiple event nodes, all looking like a
normal keyboard. The one that comes up first is one for special keys, so
And instead disable it when we do get a proximity out.
Signed-off-by: Peter Hutterer
---
Follow-up to
https://lists.freedesktop.org/archives/wayland-devel/2017-September/035006.html
While writing some more documentation for it, I realised it's easier to just
enable this on all HUION tablets and a
Avoid processing an event with a time later than the earliest timer expiry. If
libinput_dispatch() isn't called frequently enough, we may have e.g. a tap
timeout happening but read a subsequent input event first. In that case we can
erroneously trigger or miss out on taps, see wrong palm detection,
Hi Matt,
On Tue, Sep 19, 2017 at 12:41:52PM -0400, Matt Porter wrote:
> The Chalkboard Electronics HID Touchscreen is classified as
> a tablet device by systemd udev because it has BTN_TOOL_PEN
> support. It also reports a resolution of 0 for both X and Y
> axes in absinfo. This causes libinput to
Signed-off-by: Daniel Stone
---
Makefile.am| 1 +
unstable/linux-explicit-synchronization/README | 5 +
.../linux-explicit-synchronization-unstable-v1.xml | 208 +
3 files changed, 214 insertions(+)
create mode 100644 unstable/l
The Chalkboard Electronics HID Touchscreen is classified as
a tablet device by systemd udev because it has BTN_TOOL_PEN
support. It also reports a resolution of 0 for both X and Y
axes in absinfo. This causes libinput to reject it as an
invalid tablet device.
This quirk reclassifies the device as
Hi Emil,
On Mon, Sep 18, 2017 at 02:18:42PM +0100, Emil Velikov wrote:
> Hi Duncan,
>
> On 17 September 2017 at 09:04, Duncan Roe wrote:
> > On Fri, Sep 15, 2017 at 11:29:19AM +0100, Emil Velikov wrote:
> >> From: Emil Velikov
...
Agree this is orthogonal but just for the record
> >
> > I first
Hi Emil,
On Mon, Sep 18, 2017 at 02:18:42PM +0100, Emil Velikov wrote:
> Hi Duncan,
>
> On 17 September 2017 at 09:04, Duncan Roe wrote:
> > On Fri, Sep 15, 2017 at 11:29:19AM +0100, Emil Velikov wrote:
> >> From: Emil Velikov
...
>
> > I've made the updates locally, and see that it still builds
On Fri, Sep 15, 2017 at 11:29:19AM +0100, Emil Velikov wrote:
> From: Emil Velikov
...
>
> Takanari, Duncan,
> AFAICT the Renesas devices that you're using have an ImgTec IP inside
> them. Please check with Renesas and/or ImgTec, as one can build their
> driver as a Mesa component.
>
> As such you
On Fri, Sep 15, 2017 at 11:29:21AM +0100, Emil Velikov wrote:
> From: Emil Velikov
>
> File will be installed alongside the backend header.
>
> This way Vendor implementations have enough information about the
> interface and they can build their backend/driver library accordingly.
>
> Cc: Miguel
Hi Emil,
On Mon, Sep 18, 2017 at 02:18:42PM +0100, Emil Velikov wrote:
> Hi Duncan,
>
> On 17 September 2017 at 09:04, Duncan Roe wrote:
> > On Fri, Sep 15, 2017 at 11:29:19AM +0100, Emil Velikov wrote:
> >> From: Emil Velikov
...
>
> > From checking header files it does seem to me that the layo
Use EGL fence sync objects to emit timepoints for the beginning and the
end of rendering on the GPU. The timepoints are emitted asynchronously
using the sync file fds associated with the fence sync objects. The sync
file fds are acquired using the facilities provided by the
EGL_ANDROID_native_fence
The sync file functionality is required by the upcoming GPU render
timeline work, but it's only available in relatively new linux kernel
versions (4.7 and above).
This commit provides an in-tree copy of the required sync file
definitions. On systems that don't have the sync file header (due to
ha
Check for the EGL_KHR_fence_sync and EGL_ANDROID_native_fence_sync
extensions and get pointers to required extension functions.
These extensions allow us to acquire GPU timestamp information
asynchronously, and are required by the upcoming work to add
rendering begin/end timepoints to the weston t
This patchset adds support for emitting GPU rendering timepoints in the
weston timeline.
The GPU timestamp data is acquired asynchronously using the functionality
provided by the EGL_KHR_fence_sync and EGL_ANDROID_native_fence_sync
extensions.
I have also updated the wesgr tool to display the GPU
The purpose of this argument is to hold timestamp information about
events that occurred on the GPU. This argument allows us to include GPU
timestamps in timepoints such as the beginning and end of frame
rendering.
Signed-off-by: Alexandros Frantzis
---
Changes in v2:
- Added Signed-off-by.
-
On 19 September 2017 at 06:24, Duncan Roe wrote:
> Hi Emil,
>
> On Mon, Sep 18, 2017 at 02:18:42PM +0100, Emil Velikov wrote:
>> Hi Duncan,
>>
>> On 17 September 2017 at 09:04, Duncan Roe wrote:
>> > On Fri, Sep 15, 2017 at 11:29:19AM +0100, Emil Velikov wrote:
>> >> From: Emil Velikov
> ...
>>
On 19 September 2017 at 05:34, Duncan Roe wrote:
> Hi Emil,
>
> On Mon, Sep 18, 2017 at 02:18:42PM +0100, Emil Velikov wrote:
>> Hi Duncan,
>>
>> On 17 September 2017 at 09:04, Duncan Roe wrote:
>> > On Fri, Sep 15, 2017 at 11:29:19AM +0100, Emil Velikov wrote:
>> >> From: Emil Velikov
> ...
>>
On Thu, Sep 14, 2017 at 3:04 AM, Peter Hutterer
wrote:
> Some devices like the UC Logic WP5540U has BTN_STYLUS but not BTN_TOOL_PEN.
> While a kernel bug, let's just handle these correctly anyway.
>
> https://bugs.freedesktop.org/show_bug.cgi?id=102570
>
> Signed-off-by: Peter Hutterer
> ---
>
20 matches
Mail list logo
