On 16 February 2018 at 20:22, Derek Foreman wrote:
> On 2018-02-16 12:58 PM, Emil Velikov wrote:
>>
>> On 16 February 2018 at 18:24, Derek Foreman
>> wrote:
>>>
>>> On 2018-02-16 11:18 AM, Emil Velikov wrote:
On 16 February 2018 at 16:54, Derek Foreman
wrote:
>
>
On 2018-02-16 12:58 PM, Emil Velikov wrote:
On 16 February 2018 at 18:24, Derek Foreman wrote:
On 2018-02-16 11:18 AM, Emil Velikov wrote:
On 16 February 2018 at 16:54, Derek Foreman
wrote:
commit d94a8722cb29d8b897672be66ff3c9ff79eab6fe
warned this was coming, back in 2013.
I've seen lib
On 16 February 2018 at 18:24, Derek Foreman wrote:
> On 2018-02-16 11:18 AM, Emil Velikov wrote:
>>
>> On 16 February 2018 at 16:54, Derek Foreman
>> wrote:
>>>
>>> commit d94a8722cb29d8b897672be66ff3c9ff79eab6fe
>>> warned this was coming, back in 2013.
>>>
>>> I've seen libraries that have wayl
On 2018-02-16 11:18 AM, Emil Velikov wrote:
On 16 February 2018 at 16:54, Derek Foreman wrote:
commit d94a8722cb29d8b897672be66ff3c9ff79eab6fe
warned this was coming, back in 2013.
I've seen libraries that have wayland client and server using functions
in the same file. Since struct wl_buffer
On 16 February 2018 at 16:54, Derek Foreman wrote:
> commit d94a8722cb29d8b897672be66ff3c9ff79eab6fe
> warned this was coming, back in 2013.
>
> I've seen libraries that have wayland client and server using functions
> in the same file. Since struct wl_buffer still exists as an opaque
> entity in
On 16 February 2018 at 14:22, Arnaud Vrac wrote:
> On Fri, Feb 16, 2018 at 2:53 PM, Emil Velikov
> wrote:
>> On 16 February 2018 at 10:49, Daniel Stone wrote:
>>> Hi Emil,
>>>
>>> On 16 February 2018 at 10:40, Emil Velikov wrote:
On 15 February 2018 at 23:12, Derek Foreman wrote:
> M
commit d94a8722cb29d8b897672be66ff3c9ff79eab6fe
warned this was coming, back in 2013.
I've seen libraries that have wayland client and server using functions
in the same file. Since struct wl_buffer still exists as an opaque
entity in client code, the vestigial deprecated wl_buffer from the
serve
On Fri, Feb 16, 2018 at 06:44:19PM +0200, Alexandros Frantzis wrote:
> Implement the zwp_input_timestamps_manager_v1.get_touch_timestamps
> request to subscribe to timestamp events for wl_touch resources. Ensure
> that the request handling code can gracefully handle inert touch
> resources.
>
> Si
Implement the zwp_input_timestamps_manager_v1.get_touch_timestamps
request to subscribe to timestamp events for wl_touch resources. Ensure
that the request handling code can gracefully handle inert touch
resources.
Signed-off-by: Alexandros Frantzis
---
Changes in v2:
- Remove the head of timest
Implement the zwp_input_timestamps_manager_v1.get_pointer_timestamps
request to subscribe to timestamp events for wl_pointer resources.
Ensure that the request handling code can gracefully handle inert
pointer resources.
Signed-off-by: Alexandros Frantzis
---
Changes in v2:
- Remove the head of
Introduce code to support the implementation of the
input_timestamps_unstable_v1 protocol in libweston. This commit does not
implement the actual timestamp subscriptions, but sets up the
zwp_input_timestamps_manager_v1 object and introduces dummy request
handling functions for it, laying the founda
Implement the zwp_input_timestamps_manager_v1.get_keyboard_timestamps
request to subscribe to timestamp events for wl_keyboard resources.
Ensure that the request handling code can gracefully handle inert
keyboard resources.
This commit introduces a few internal helper functions which will also
be
Add a helper function to check if two struct timespec values are equal.
This helper function will be used in upcoming commits that implement the
input_timestamps_unstable_v1 protocol.
Signed-off-by: Alexandros Frantzis
Reviewed-by: Pekka Paalanen
---
Changes in v2:
- No changes.
shared/timesp
The input_timestamps_unstable_v1 protocol allows clients to subscribe to
high-resolution timestamp events for input events (see [1]).
This patchset implements the input_timestamps_unstable_v1 protocol in libweston
and also adds tests for the implementation in the weston test suite.
Patches (1) an
Introduce helper test code to implement the client side of the
input_timestamps_unstable_v1 protocol. This helper will be used in
upcoming commits to test the server side implementation of the protocol
in libweston.
The input_timestamps_unstable_v1 protocol was introduced in version 1.13
of waylan
From: Emil Velikov
First one is deprecated in favour of the second option.
The latter is newly introduced and annotates the generated symbols
accordingly.
Signed-off-by: Emil Velikov
---
Makefile.am | 4 ++-
tests/data/small-private-code.c | 71 +++
From: Emil Velikov
The core wayland interfaces are public, via the libwayland-server and
libwayland-client DSOs. Hence use "public-code" cmdline option, instead
of the deprecated code".
As the host wayland-scanner may not know about the new option, use the
legacy "code".
Signed-off-by: Emil Vel
From: Emil Velikov
The options are used to indicate how the code will be used - will it be
public, as part of a DSO or private.
In nearly every instance, people want to use the latter. One noticeable
exception is the wayland libraries. They provide the base marshalling
protocol that everyone use
From: Emil Velikov
A more generic way to evaluating various attributes, __has_attribute is
available with gcc, clang, even the Oracle/Sun compiler.
Signed-off-by: Emil Velikov
---
src/scanner.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/src/scanner.c b/src/scanner
From: Pekka Paalanen
If we are processing a connector that does not have an existing routing,
it is possible we pick a CRTC that was previously routed to a connector
we have not enabled yet. If that happens, the latter connector cannot
preserve its routing.
Check that no other connector we might
From: Pekka Paalanen
This makes it easier to just pass wet_compositor around and take the
weston_compositor from it.
It feels weird to go from weston_compositor to wet_compositor all the
time in internal functions. It's necessary in callbacks that cannot
carry wet_compositor, but otherwise it is
From: Pekka Paalanen
Add a new output section key "same-as" for configuring clone mode. An
output marked "same-as" another output will be configured identically to
the other output.
The current implementation supports only CRTC sharing for clone mode.
Independent CRTC clone mode cannot be suppor
From: Pekka Paalanen
Allow cloning up to 4 connectors from the same CRTC. All the
implementation bits support more than one head per output already.
Four is just an arbitary number, small but unlikely to ever be the
limiting factor in cloning since hardware is usually very restricted.
Signed-of
From: Pekka Paalanen
Rename user_data to wet, because it is called wet everywhere else.
Drop the local variable ec, because that is available as wet.compositor.
This models a little better that wet_compositor owns weston_compositor,
and not the other way around.
Signed-off-by: Pekka Paalanen
From: Pekka Paalanen
For the attach on an enabled output to have an effect, we need to go
through drmModeSetCrtc or ATOMIC_ALLOW_MODESET.
Signed-off-by: Pekka Paalanen
---
libweston/compositor-drm.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/libweston/compositor-drm.c
From: Pekka Paalanen
Rename connector_get_current_mode() because it will be useful for
storing not just the current mode on creating a head.
Signed-off-by: Pekka Paalanen
---
libweston/compositor-drm.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/libweston/com
From: Pekka Paalanen
To support shared-CRTC clone mode, the chosen CRTC needs to support
driving all the attached connectors. Replace the old algorithm with a
new one that takes into account all associated connectors.
Ideally it should use possible_clones mask to check which encoders (and
theref
From: Pekka Paalanen
When a head is detached from an enabled output, that output needs to go
through a modeset (drmModeSetCrtc() / ATOMIC_ALLOW_MODESET) so that the
connector is actually removed from the CRTC.
This has not yet been a problem, because an output could only have one
head at a time,
From: Pekka Paalanen
Stop using a head for printing the mode list, because there could be
multiple heads. We already gather the mode list from all heads.
No need to print the connector id here, because it is logged with DRM
heads, and core prints the head names on output enable.
The "built-in"
From: Pekka Paalanen
The head was just zalloc()'d, there is no need to memset it to zero.
If a function fails, it is preferable it leaves the output arguments
untouched.
Signed-off-by: Pekka Paalanen
---
libweston/compositor-drm.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
d
From: Pekka Paalanen
Fix this function to support more than one head per output.
Signed-off-by: Pekka Paalanen
---
libweston/compositor-drm.c | 19 +++
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/libweston/compositor-drm.c b/libweston/compositor-drm.c
index 9
From: Pekka Paalanen
Previously the log contained one line for EDID data and another line for
the head, and you just had to know they belong together. Make it more
obvious to read by putting both head and EDID info on the same line.
We no longer print EDID data every time it is parsed (on every
From: Pekka Paalanen
If an output has multiple (cloned) heads, it should be enough for any
head to support backlight control for DRM-backend to expose it.
Inspect all attached heads for backlight control and improve the
logging.
Pick the initial backlight level from whatever happens to be the "
From: Pekka Paalanen
A single list of modes needs to be combined from the mode lists in each
attached head. We could just concatenate the lists, but that might
introduce duplicates. Try to avoid duplicates instead by using partially
fuzzy matching.
When a duplicate is found, try to figure out wh
From: Pekka Paalanen
Fix this function to support more than one head per output.
Signed-off-by: Pekka Paalanen
---
libweston/compositor-drm.c | 38 +-
1 file changed, 25 insertions(+), 13 deletions(-)
diff --git a/libweston/compositor-drm.c b/libweston/comp
From: Pekka Paalanen
Fix this function to support more than one head per output.
Signed-off-by: Pekka Paalanen
---
libweston/compositor-drm.c | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/libweston/compositor-drm.c b/libweston/compositor-drm.c
index e1feeab4
From: Pekka Paalanen
Replace the unused_connectors array by iterating through the head list
instead. A head that is not enabled (attached to an enabled output) is
basically an unused connector.
All connectors regardless of their status have a drm_head. This has the
nice effect that drm_pending_s
From: Pekka Paalanen
In previous patches, all the appropriate fields from drm_output have
been moved into drm_head, and resource allocation has been moved away
from drm_output creation. It is time to throw the switch: this patch
disconnects the drm_output and drm_head lifetimes.
Previously a drm
From: Pekka Paalanen
Move the initialization of the drm_output mode list to
drm_output_set_mode() time.
Once we stop creating the drm_head with the drm_output, there will not
be a head to get the mode list from at drm_output creation time.
Furthermore, once DRM-backend starts supporting more th
From: Pekka Paalanen
The inherited mode is the video mode on the connector when we have not
yet reconfigured the connector, if set.
Get the inherited mode the moment we create a drm_head, not when we
determine the mode for a drm_output. This way we are sure to read all
inherited modes before we
From: Pekka Paalanen
A drm_output needs a CRTC only when it is in use. Allocating a CRTC on
creation of drm_output will reserve the CRTC regardless of whether the
output is actually used or not. This may cause creating other
drm_outputs to fail if there are not enough CRTCs.
Instead, allocate th
From: Pekka Paalanen
Backlight is driven per connector, hence it belongs in struct drm_head.
weston_output::set_backlight() API is remains per output so far. There
is no UI to control backlights per head and adding one would be
difficult for an output that has multiple cloned heads.
Signed-off-
From: Pekka Paalanen
As these planes are allocated on output enable and freed on output
disable, there cannot be a match in the pending_output_list.
Signed-off-by: Pekka Paalanen
---
libweston/compositor-drm.c | 8
1 file changed, 8 deletions(-)
diff --git a/libweston/compositor-drm.
From: Pekka Paalanen
As CRTC is allocated on output enable and deallocated on output disable,
there cannot be any matches in find-by-crtc from the
pending_output_list.
Remove the loop over pending_output_list as never finding anything by
definition.
Signed-off-by: Pekka Paalanen
---
libweston
From: Pekka Paalanen
Move the connector related fields from drm_output to the drm_head. A
drm_head represents a connector for now.
The code in drm_head_create() to update connector data, monitor
information, etc. is moved into a new function. This will be useful when
DRM-backend starts creating
From: Pekka Paalanen
Instead of iterating output_list and pending_output_list, iterate
head_list to find outputs whose connectors have been disconnected.
This helps a following patch to move connector fields from drm_output to
drm_head.
Signed-off-by: Pekka Paalanen
---
libweston/compositor-d
From: Pekka Paalanen
Making this function not depend on drm_head::output field through
drm_output_find_by_connector() will later allow to remove the
drm_head::output field before removing the unused_connectors array. This
helps keeping the commit more fine-grained.
drm_backend_update_unused_outp
From: Pekka Paalanen
Switch drm_output_find_by_connector() to search for the output by
iterating the compositor's head_list. drm_head_find_by_connector() will
be useful later on its own.
As of "compositor-drm: start migration to head-based output API" the
head list is guaranteed to contain all c
From: Pekka Paalanen
Move the responsibility of ensuring the head will work in the enabled
output to the backends.
A compositor cannot enable an output without heads, and removing the
last head from an output automatically disables the output, so attaching
a new head to an enabled output is only
From: Pekka Paalanen
Helps debugging.
Signed-off-by: Pekka Paalanen
---
libweston/compositor.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/libweston/compositor.c b/libweston/compositor.c
index 0d2af676..362074b6 100644
--- a/libweston/compositor.c
+++ b/libw
From: Pekka Paalanen
Add safeguards to make it painfully obvious if we ever get the pairing
of wayland_backend_create_output_surface() and
wayland_backend_destroy_output_surface() wrong. Helps catching bugs.
Signed-off-by: Pekka Paalanen
---
libweston/compositor-wayland.c | 17 ++--
From: Pekka Paalanen
To let users pick an arbitrary name for an output, to be used as e.g. a
configuration key, add API to create an output with a given name. For
the same configuration purpose, add a search function as well.
For the search function to be predictable, forbid creating multiple
ou
From: Pekka Paalanen
Support attaching custom data to a weston_output by the traditional
destroy listener / wl_signal_get approach.
Needs a new destroy signal, because user data lifetime should be the
lifetime of the weston_output regradless of its enabled status. The old
destroy signal is for o
From: Pekka Paalanen
Remove the scaffolding that allowed backends to be converted one by one
to the head-based API. Nothing is using these members anymore.
Signed-off-by: Pekka Paalanen
---
libweston/compositor.c | 36 +++-
libweston/compositor.h | 3 ---
2 fil
From: Pekka Paalanen
Hook up the libweston facing head-based output API by introducing struct
drm_head, but leave it as a fake so that members can be migrated in
pieces in follow-up patches.
The DRM backend continues to create an output for each connected
connector only, and during output creati
From: Pekka Paalanen
This will be interesting to see when testing clone mode.
Signed-off-by: Pekka Paalanen
---
libweston/compositor.c | 32
1 file changed, 32 insertions(+)
diff --git a/libweston/compositor.c b/libweston/compositor.c
index 9a8b90f5..c41c7233
From: Pekka Paalanen
Follow the standard pattern set by the headless backend which also uses
the the window output API.
Stops relying on the implicit weston_output::head.
Signed-off-by: Pekka Paalanen
---
libweston/compositor-x11.c | 68 --
1 file c
From: Pekka Paalanen
Follow the standard pattern used in the headless and x11 backend
migration, but also cater for the two other backend modes: --sprawl or
fullscreen-shell, and --fullscreen.
Stops relying on the implicit weston_output::head.
Unlike other backends, this uses the attach_head ho
From: Pekka Paalanen
Implement the head-based output API in this backend, and stop relying on
the implicit weston_output::head.
The split between fbdev_head and fbdev_output is somewhat arbitrary.
There is no hotplug or unplug, and there is always 1:1 relationship.
Struct fbdev_screeninfo could
From: Pekka Paalanen
If the idle_repaint() callback has been scheduled when a weston_output
gets destroyed, the callback will hit use-after-free. I have encountered
this when migrating the wayland backend to the head-based API, using
--sprawl, and closing/disconnecting one of the parent composito
From: Pekka Paalanen
All frontends have been converted to the new head-based output
management API, which means that
weston_compositor_create_output_with_head() is calling
weston_output_attach_head(). We will never hit the implicit attach
anymore.
Therefore we can now require that an output has
From: Pekka Paalanen
The functions called here, particularly
weston_output_transform_scale_init(), rely on current mode being set.
The current mode must also be found in the mode list, though we don't
explicitly check it here.
current_mode not being set is a programmer error. It could be a backe
From: Pekka Paalanen
Follow the starndard patttern as the other backends, headless and x11 in
particular, to stop relying on the implicit weston_output::head.
Signed-off-by: Pekka Paalanen
---
libweston/compositor-rdp.c | 64 ++
1 file changed, 53 in
From: Pekka Paalanen
Destroying the whole output in reenable would cause list walk
corruption: the loop over output_list in session_notify() is not using
wl_list_for_each_safe so output removal would break it.
Creating a new output is also problematic as it needs the compositor to
configure it,
From: Pekka Paalanen
Implement the head-based output API in this backend, and stop relying on
the implicit weston_output::head.
Signed-off-by: Pekka Paalanen
---
libweston/compositor-headless.c | 75 ++---
1 file changed, 63 insertions(+), 12 deletions(-)
d
From: Pekka Paalanen
Migrate the RDP frontend to use the new head-based output configuration
API: listen for heads_changed, and process all heads.
Signed-off-by: Pekka Paalanen
---
compositor/main.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/compositor/
From: Pekka Paalanen
Output make and model are not allowed to be NULL in the protocol, so
ensure they are not forgotten when enabling an output.
Signed-off-by: Pekka Paalanen
---
libweston/compositor.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libweston/compositor.c b/libweston
From: Pekka Paalanen
Migrate the Wayland frontend to use the new head-based output
configuration API: listen for heads_changed, and process all heads.
Signed-off-by: Pekka Paalanen
---
compositor/main.c | 27 ---
1 file changed, 8 insertions(+), 19 deletions(-)
diff --
From: Pekka Paalanen
Migrate the x11 frontend to use the new head-based output configuration
API: listen for heads_changed, and process all heads.
Signed-off-by: Pekka Paalanen
---
compositor/main.c | 14 +-
1 file changed, 5 insertions(+), 9 deletions(-)
diff --git a/compositor/m
From: Pekka Paalanen
Rename the function pointer to create_head() because that is what it
does on backends that are converted to the head-based API. Update the
documentation to match.
Surprisingly this is not an ABI break, as the function behaviour and
signature remain intact. Hence API_NAME is
From: Pekka Paalanen
Add support for subscribing to weston_head destruction.
The primary use case for heads being destroyed arbitrarily is the
DRM-backend with MST connectors, which may disappear on unplug. It is
not just the connector becoming disconnected, it is the connector
actually disappea
From: Pekka Paalanen
Migrate the headless frontend to use the new head-based output
configuration API: listen for heads_changed, and process all heads.
The simple_heads_changed() function is written to be able to cater for
all backends. The rest will be migrated individually.
The head destroy l
From: Pekka Paalanen
The signal has been replaced with the heads_changed hook and is no
longer useful.
weston_pending_output_coldplug() is renamed to
weston_compositor_flush_heads_changed() for two reasons: it better
describes what it does now, and it serves as an obvious flag that
libweston ABI
From: Pekka Paalanen
Migrate the fbdev frontend to use the new head-based output
configuration API: listen for heads_changed, and process all heads.
Signed-off-by: Pekka Paalanen
---
compositor/main.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/compositor/ma
From: Pekka Paalanen
Heads need to be named, so they can be referenced in logs and
configuration sources.
When clone mode is implemented, output and head names may differ.
Signed-off-by: Pekka Paalanen
Reviewed-by: Derek Foreman
---
libweston/compositor.c | 10 --
libweston/composito
From: Pekka Paalanen
Introduce the API for users (compositors) to create an output from a
head, attach and detach heads, and destroy outputs created this way.
This also adds the backend-facing API to libweston.
In the new API design, a backend creates heads, and the compositor
chooses one or mor
From: Pekka Paalanen
Migrate the DRM frontend to use the simple head-based output
configurator, maintaining the exact same features and semantics as
before.
This is an intermediate step. It is unoptimal to create a weston_output
just to turn it off, but the libweston implementation and the DRM
b
From: Pekka Paalanen
weston_compositor needs to maintain a list of all available heads, so
that a compositor can pick and choose which heads to take into or out of
use at arbitrary times. The heads may be on or off, and connected or
disconnected.
Signed-off-by: Pekka Paalanen
Reviewed-by: Derek
From: Pekka Paalanen
The intention is that in the future backends will dynamically allocate
weston_heads based on the resources they have. The lifetime of a
weston_head will be independent of the lifetime of a weston_output it
may be attached to. Backends allocate objects derived from weston_head
From: Pekka Paalanen
The 'head' member of 'struct weston_output' is going to go unused and
then disappear, so stop using it and find a head from the proper list.
However, this leaves a problem in cms-colord: if you have multiple
monitors driver with the same CRTC, what do you say to the color
ma
From: Pekka Paalanen
Reacting to DRM hotplug events is racy. It is theoretically possible to
get hotplug events for a quick swap from one monitor to another and
process both only after the new monitor is connected. Hence it is
possible for display device information to change without going throug
From: Pekka Paalanen
Move the call out of wet_configure_windowed_output_from_config() and
into its callers.
This allows to migrate each frontend one by one.
Signed-off-by: Pekka Paalanen
---
compositor/main.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/composit
From: Pekka Paalanen
Enabled is orthogonal from connected. A connected head could be
disabled, or a disconnected head could in the future be enabled.
Compositors quite likely want to check if a head is already enabled
before starting to take it into use.
Signed-off-by: Pekka Paalanen
Reviewed-
From: Pekka Paalanen
Add a hook for compositors to get a callback when heads are added or
their connection status changes, to which compositors likely want to
react to by enabling or disabling outputs (API for that to be added
later).
As many head changes as possible should be coalesced into a s
From: Pekka Paalanen
Remove the wl_resource in the head's resource list when we are
removing the wl_output global. We sent global removal events to clients,
the resources should become dummies until clients reap them. Reset user
data so that clients triying to use dummy objects don't hit e.g. a f
From: Pekka Paalanen
Heads may be disconnected or connected and the compositor needs to be
able to know the state to know which heads to take into use.
Currently a single head is automatically created with an output, and
outputs are only ever created as connected and destroyed on
disconnection,
From: Pekka Paalanen
Split out a new function. This is a pure refactoring, no change in
behaviour.
This helps a following patch that adds a loop over output->head_list.
Signed-off-by: Pekka Paalanen
v5 Reviewed-by: Derek Foreman
---
libweston/compositor.c | 57 +++
From: Pekka Paalanen
Duplicate these strings to decouple their lifetime from whatever the
backends used. This should prevent hard to catch use after frees and
such problems in the future.
Signed-off-by: Pekka Paalanen
v5 Reviewed-by: Derek Foreman
---
libweston/compositor.c | 14 +++--
From: Pekka Paalanen
As a wl_output represents weston_head, use a weston_head pointer as the
wl_output global's user data.
Signed-off-by: Pekka Paalanen
v5 Reviewed-by: Derek Foreman
---
libweston/compositor.c | 11 +++
libweston/compositor.h | 2 ++
2 files changed, 9 insertions(+),
From: Pekka Paalanen
The wl_output protocol interface exposes things like monitor make,
model, sub-pixel layout and physical dimensions. Obviously wl_output is
meant to represent a monitor.
The abstraction of a monitor is weston_head. Therefore move the wl_output
global and the bound resources l
From: Pekka Paalanen
The user data of a wl_resource representing a wl_output protocol object
used to be a pointer to weston_output. Now that weston_output is being
split, wl_output more accurately refers to weston_head which is a single
monitor.
Change the wl_output user data to point to weston_
From: Pekka Paalanen
In order to support clone modes, libweston needs the concept of a head
that is separate from weston_output. While weston_output manages buffers
and the repaint state machine, weston_head will represent a single
monitor. In the future it will be possible to have a single
westo
From: Pekka Paalanen
Hi all,
here is the v6 of the shared-CRTC clone mode series. Since v5, quite
many patches have been extracted from this series, sent out and merged
upstream. However, now the series is bigger than ever, because here I am
posting the complete series, including the full DRM-ba
On 16 February 2018 at 14:36, Emil Velikov wrote:
> On 21 February 2017 at 16:14, Emil Velikov wrote:
>> Signed-off-by: Emil Velikov
>> Reviewed-by: Derek Foreman (v1)
>
> Doesn't seems like this patch has landed. Can anyone do the honours?
Done now, thanks!
___
On 21 February 2017 at 16:14, Emil Velikov wrote:
> From: Emil Velikov
>
> v2: Rebase, address wayland-client-uninstalled
>
> Signed-off-by: Emil Velikov
> Reviewed-by: Derek Foreman (v1)
Doesn't seems like this patch has landed. Can anyone do the honours?
https://patchwork.freedesktop.org/pa
On Fri, Feb 16, 2018 at 2:53 PM, Emil Velikov wrote:
> On 16 February 2018 at 10:49, Daniel Stone wrote:
>> Hi Emil,
>>
>> On 16 February 2018 at 10:40, Emil Velikov wrote:
>>> On 15 February 2018 at 23:12, Derek Foreman wrote:
Maybe it's just me, but having different names for the same va
On 16 February 2018 at 10:49, Daniel Stone wrote:
> Hi Emil,
>
> On 16 February 2018 at 10:40, Emil Velikov wrote:
>> On 15 February 2018 at 23:12, Derek Foreman wrote:
>>> Maybe it's just me, but having different names for the same variable for C
>>> vs C++ compilation seems really nasty and po
Hi Emil,
On 16 February 2018 at 10:40, Emil Velikov wrote:
> On 15 February 2018 at 23:12, Derek Foreman wrote:
>> Maybe it's just me, but having different names for the same variable for C
>> vs C++ compilation seems really nasty and potentially surprising.
>>
> Indeed it is surprising. In prac
On 15 February 2018 at 23:12, Derek Foreman wrote:
> On 2018-02-15 12:50 PM, Emil Velikov wrote:
>>
>> From: Emil Velikov
>>
>> private is a reserved keyworkd in C++. Thus to make things work, we
>> should use something else - wl_egl_window::driver_private.
>>
>> Make sure to do so only for C++ c
On Fri, 16 Feb 2018 08:23:28 +
"Keskinarkaus, Teemu" wrote:
> Hi,
>
> I have custom i.MX6 based HW that is running Linux 4.1.x with Weston
> 1.11.0. I recently updated it to Weston 2.0.0 and the panel-location
> option in Weston.ini - file doesn't work anymore.
>
> I have this in Weston.in
1 - 100 of 102 matches
Mail list logo