On Mon, 31 Mar 2014 02:48:09 +
Wang, Quanxian quanxian.w...@intel.com wrote:
-Original Message-
From: Pekka Paalanen [mailto:ppaala...@gmail.com]
Sent: Friday, March 28, 2014 11:00 PM
To: Wang, Quanxian
Cc: wayland-devel@lists.freedesktop.org
Subject: Re: [PATCH V2 1/8]
On Sun, 30 Mar 2014 13:36:32 +0200
Niels Ole Salscheider niels_...@salscheider-online.de wrote:
The color correction protocol allows to attach an ICC profile to a
surface. It also tells the client about the blending color space and
the color spaces of all outputs.
Signed-off-by: Niels Ole
On Mon, Mar 31, 2014 at 08:08:32AM +1000, Peter Hutterer wrote:
note that the only binary that needs a C++ compiler is the C++ build test.
the library itself only needs a C compiler.
A good thing, would be to compile the lib with tinycc and/or
open64 to kind of be sure it's not hard dependent
On 31 March 2014 08:46, Pekka Paalanen ppaala...@gmail.com wrote:
how much data can an ICC profile be?
Printer profiles can be several megabytes in size, but display
profiles (what will be seen here) are usually in the 20-30kb size
range.
Also, what if a client has several surfaces all with
Am 31.03.2014 09:46, schrieb Pekka Paalanen:
On Sun, 30 Mar 2014 13:36:32 +0200
Niels Ole Salscheider niels_...@salscheider-online.de wrote:
The color correction protocol allows to attach an ICC profile to a
surface. It also tells the client about the blending color space and
the color
Am 30.03.2014 13:36, schrieb Niels Ole Salscheider:
This implements the functionality to attach a profile to a surface
in weston. An LUT is built from the profile that can be used to
transform colors from the input color space to the blending color
space.
This patch uses the sRGB color space
On Mon, 31 Mar 2014 09:25:34 +0100
Richard Hughes hughsi...@gmail.com wrote:
On 31 March 2014 08:46, Pekka Paalanen ppaala...@gmail.com wrote:
how much data can an ICC profile be?
Printer profiles can be several megabytes in size, but display
profiles (what will be seen here) are usually
Am 31.03.2014 11:43, schrieb Pekka Paalanen:
On Mon, 31 Mar 2014 09:25:34 +0100
Richard Hughes hughsi...@gmail.com wrote:
On 31 March 2014 08:46, Pekka Paalanen ppaala...@gmail.com wrote:
how much data can an ICC profile be?
Printer profiles can be several megabytes in size, but display
On 31 March 2014 12:13, Kai-Uwe Behrmann ku.b-l...@gmx.de wrote:
In many cases a client is not remotely able to compute per output
regions without much information about scaling, positioning, (warping?)
To explain a little here, different outputs need different ICC
profiles (and thus a
On Mon, 31 Mar 2014 11:29:03 +0200
Kai-Uwe Behrmann ku.b-l...@gmx.de wrote:
Am 31.03.2014 09:46, schrieb Pekka Paalanen:
On Sun, 30 Mar 2014 13:36:32 +0200
Niels Ole Salscheider niels_...@salscheider-online.de wrote:
The color correction protocol allows to attach an ICC profile to a
Pekka Paalanen wrote:
On Mon, 31 Mar 2014 09:25:34 +0100
Richard Hughes hughsi...@gmail.com wrote:
On 31 March 2014 08:46, Pekka Paalanen
ppaala...@gmail.com wrote:
how much data can an ICC profile be?
Printer profiles can be several megabytes in size, but display
profiles (what will
Niels Ole Salscheider wrote:
The color correction protocol allows to attach an ICC profile to a
surface. It also tells the client about the blending color space and
the color spaces of all outputs.
As you pointed out, it does look like this has to be done by the
compositor, because a
Hi,
On 27 March 2014 22:41, Ran Benita ran...@gmail.com wrote:
On Thu, Mar 27, 2014 at 09:04:07PM +0100, David Herrmann wrote:
On Thu, Mar 27, 2014 at 8:22 PM, Ran Benita ran...@gmail.com wrote:
- Added two new functions, xkb_state_key_get_utf{8,32}(). They
combine the operations of
Am 31.03.2014 16:10, schrieb Pekka Paalanen:
On Mon, 31 Mar 2014 11:29:03 +0200
Kai-Uwe Behrmann ku.b-l...@gmx.de wrote:
Am 31.03.2014 09:46, schrieb Pekka Paalanen:
On Sun, 30 Mar 2014 13:36:32 +0200
Niels Ole Salscheider niels_...@salscheider-online.de wrote:
The color correction
Reduces the amount of boilerplate code.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
test/litest-bcm5974.c | 2 +-
test/litest-generic-highres-touch.c | 2 +-
test/litest-keyboard.c | 2 +-
test/litest-mouse.c | 2 +-
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
test/litest-bcm5974.c | 147 ++-
test/litest-generic-highres-touch.c | 128
test/litest-keyboard.c | 231 +---
test/litest-mouse.c
Both functions accept a series of event types/codes tuples, terminated by -1.
For the even type INPUT_PROP_MAX (an invalid type otherwise) the code is used
as a property to enable.
The _abs function als takes an array of absinfo, with absinfo.value
determining the axis to change. If none are
For specific tests we need something that e.g. looks like a touchpad, but has
a different name, a different number of slots, etc. In this case, the
following code will do exactly that:
struct input_absinfo overrides[] = {
{ .value = ABS_MT_SLOT, .minimum = 0, .maximum = 100 },
{ .value = -1 },
With 1/5, the descriptions are already pretty much limited to just a static
description of a device. This set pushes this further, truly reducing
each test device to a bunch of arrays with the device-specific data,
everything else that used to be boilerplate is now handled by the litest
Most of the test devices now are static descriptions anyway, make them fully
static now, including for touch events.
Switch the synaptics device now as example, the rest comes later for easier
patch review.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
test/litest-int.h | 47
20 matches
Mail list logo
