Hi,
Does anybody know whether there’s a dedicated mailing list suitable for
asking questions about the hardware acceleration in the remote desktop
use-case for those two?
I did a quick look through both repos’ README and CONTRIBUTING files, but
didn’t find anything.
XWayland gets used in rootless mode, such that each separate X11 window is
exposed as an independent surface to the Wayland compositor.
Does anybody happen to know of a Wayland compositor that acts analogously,
forwarding each client surface to the underlying x11 server as a toplevel
window?
Hi,
For a while now, I’ve been hoping to see some commercial solutions like
https://symless.com/synergy that implement keyboard and mouse sharing
finally add support for running on DEs that use Wayland.
It seems to be forever on their feature roadmaps but never really getting
closer.
I assume th
On Wed, Jun 14, 2023 at 7:13 PM Daniel Stone wrote:
> Hi Joe,
>
> On Wed, 14 Jun 2023 at 21:33, Joe M wrote:
>
>> Thanks Daniel. Do you know if wl_output instances are decoupled from each
>> other, when it comes to display refresh?
>>
>
> Yep, absolutely.
>
>
>> The wl_output geometry info hints
If you’re asking whether it’s possible to migrate a given wl_surface from
being a subsurface (initially) to later being a shell surface, this isn’t
allowed. This has to do with the immutability of a surface’s so-called
“role.” (Surfaces are only ever allowed to be registered with one given
role. )
On Thu, Apr 9, 2020 at 5:51 PM Simon Ser wrote:
> On Friday, April 10, 2020 12:48 AM, Matt Hoosier
> wrote:
>
> > As a compositor author, do I have to account for the possibility that
> the EGL implementation may provide (squat on) the
> “zwp_linux_linux_dmabuf_v1” buffer
+ list
On Thu, Apr 9, 2020 at 5:48 PM Matt Hoosier wrote:
> On Thu, Apr 9, 2020 at 5:42 PM Scott Anderson wrote:
>
>> On 10/04/20 10:34 am, Matt Hoosier wrote:
>> > On Thu, Apr 9, 2020 at 2:51 PM Simon Ser > > <mailto:cont...@emersion.fr>> wrote:
>>
On Thu, Apr 9, 2020 at 2:51 PM Simon Ser wrote:
> On Thursday, April 9, 2020 9:41 PM, Matt Hoosier
> wrote:
>
> > If I remember correctly, I've read various messages on the list here
> saying that eventually it would be preferred for EGL implementations
> would just
Hi,
Historically, many EGL implementations have registered a private wl_drm
buffer factory for use internally by the implementation's Wayland backend,
as part of the setup work done go eglBindWaylandDisplayWl().
Separately, compositors have started to implement explicit support for the
zwp_linux_
On Wed, Apr 1, 2020 at 3:17 PM Simon Ser wrote:
> On Wednesday, April 1, 2020 9:38 PM, Matt Hoosier
> wrote:
>
> > I'm searching for some sort of scheme that will let my DRI master query
> the set of available connectors and select the one carrying a prearranged
> de
I'm searching for some sort of scheme that will let my DRI master query the
set of available connectors and select the one carrying a prearranged
designation. The problem I'm trying to solve is to allow deploying one
standardized userspace component across a fleet of devices that have
varying numbe
On Mon, Jan 20, 2020 at 2:58 AM Pekka Paalanen wrote:
> On Fri, 17 Jan 2020 10:51:45 -0600
> Matt Hoosier wrote:
>
> > Hi all,
> >
> > I'm confronting a situation where the hardware with which I work is
> capable
> > of driving connectors at 4K
Hi all,
I'm confronting a situation where the hardware with which I work is capable
of driving connectors at 4K or 8K, but doing so requires bonding the
scanning of multiple planes together.
The scenario is that you'd have a big primary framebuffer whose size is too
large for an individual hardwa
Hi all,
A while ago, LWN.net ran an article (https://lwn.net/Articles/702075/) that
overviewed the Wayland-based display architecture used by ChromeOS to allow
its containerized Android runtimes to forward graphics surfaces along to
the ChromeOS compositor.
Does anybody know where to find the sou
(Fair warning, I've never used GitLab other than anonymously before.)
I'd like to be able to get email notifications about all the PR's (their
initial posting, subsequent code reviews, acceptance, etc) as a way to
simulate the former bird's eye view that was possible when all patches
passed throug
Hi;
I'm interested in getting an external display to make testing the
touch-centric changes in Weston easier when working from a PC. Does anybody
have recommendations for a good model that attaches over HDMI+USB that
supports a reasonably good resolution and reports a standard slotted
multitouch e
On Mon, Jul 2, 2018 at 4:10 AM Pekka Paalanen wrote:
> On Fri, 29 Jun 2018 10:05:58 -0500
> Matt Hoosier wrote:
>
> > Hi all,
> >
> > Pekka's recent comments about wanting to enable set-top boxes built with
> > libweston to do DRM content got me to wonderi
Hi all,
Pekka's recent comments about wanting to enable set-top boxes built with
libweston to do DRM content got me to wondering:
Who all is using libweston directly (as opposed to running /usr/bin/weston
possibly with custom shells plugins or similar)? For my own purposes, I
just use the full co
On Mon, Jun 18, 2018 at 8:54 AM Pekka Paalanen wrote:
> Hi Matt,
>
> did you intend to reply on list? Please CC if you did.
>
> On Mon, 18 Jun 2018 08:35:56 -0500
> Matt Hoosier wrote:
>
> > On Mon, Jun 18, 2018 at 3:59 AM Pekka Paalanen
> wrote:
> >
>
Any takers to accept this one?
On Fri, May 4, 2018 at 9:26 AM, Matt Hoosier wrote:
> Rather than segfaulting by attempting to traverse an initially
> null log handler pointer, explicitly print a message and abort.
>
> Signed-off-by: Matt Hoosier
> ---
> li
On Fri, May 4, 2018 at 8:46 AM, Pekka Paalanen wrote:
> On Fri, 4 May 2018 07:55:10 -0500
> Matt Hoosier wrote:
>
> > On Fri, May 4, 2018 at 2:13 AM, Pekka Paalanen
> wrote:
> >
> > > The crucial call to make is weston_log_set_handler() with non-NULL
> >
Rather than segfaulting by attempting to traverse an initially
null log handler pointer, explicitly print a message and abort.
Signed-off-by: Matt Hoosier
---
libweston/log.c | 22 --
1 file changed, 20 insertions(+), 2 deletions(-)
diff --git a/libweston/log.c b/libweston
On Fri, May 4, 2018 at 2:13 AM, Pekka Paalanen wrote:
> On Thu, 03 May 2018 23:38:55 +0100
> adlo wrote:
>
> > On Thu, 2018-05-03 at 14:12 +0300, Pekka Paalanen wrote:
> > >
> > > what's the backtrace from gdb for that?
> > >
> >
> > Is this any help?
> >
> > #0 0x in ()
> > #1
(ADITG/ESB)
> >
> > Tel. +49 5121 49 6921
> > > -Original Message-
> > > From: Peter Hutterer [mailto:peter.hutte...@who-t.net]
> > > Sent: Freitag, 6. April 2018 04:29
> > > To: Friedrich, Eugen (ADITG/ESB)
> > > Cc: Matt Hoosier; Pekka Paal
gt; > Tel. +49 5121 49 6921
> >
> > > -Original Message-
> > > From: wayland-devel [mailto:wayland-devel-
> > > boun...@lists.freedesktop.org] On Behalf Of Peter Hutterer
> > > Sent: Donnerstag, 5. April 2018 06:27
> > > To: Matt Hoosier
&
I encounter another "bad" behavior related to multiple firings of the UDev
'add' event for a given input node.
Typically on modest embedded systems, you do not want to run the exhaustive
'udevadm trigger' during the main booting sequence. That causes hundreds or
thousands of UDev nodes to be crawl
On Wed, Apr 4, 2018 at 2:27 AM, Pekka Paalanen wrote:
> On Wed, 04 Apr 2018 00:37:58 +
> Matt Hoosier wrote:
>
> > On Tue, Apr 3, 2018, 08:10 Matt Hoosier wrote:
> >
> > > On Tue, Apr 3, 2018 at 5:35 AM, Philipp Kerling
> > > wrote:
> > >
&g
On Tue, Apr 3, 2018, 08:10 Matt Hoosier wrote:
> On Tue, Apr 3, 2018 at 5:35 AM, Philipp Kerling
> wrote:
>
>> > Do you happen to know of a good readymade program that fakes the
>> > presence of a touch input device with uinput? I'd love to test this
>> >
p so that the touchscreen
got pegged to the correct physical output. I have the feeling that I just
overlooked some aspect of configuration about this.
-Matt
>
>
>
> > On Fri, Mar 23, 2018, 09:38 Matt Hoosier
> > wrote:
> > > On Fri, Mar 23, 2018 at 9:30 AM, Pekka Paalanen
ri, Mar 23, 2018, 09:38 Matt Hoosier wrote:
> On Fri, Mar 23, 2018 at 9:30 AM, Pekka Paalanen
> wrote:
> > On Fri, 23 Mar 2018 08:46:46 -0500
> > Matt Hoosier wrote:
> >
> >> I am very much in favor of the overall approach on this patch series.
> >> I'
On Fri, Mar 23, 2018 at 9:30 AM, Pekka Paalanen wrote:
> On Fri, 23 Mar 2018 08:46:46 -0500
> Matt Hoosier wrote:
>
>> I am very much in favor of the overall approach on this patch series.
>> I've experienced every single one of the problems described in this
>> s
I am very much in favor of the overall approach on this patch series.
I've experienced every single one of the problems described in this
summary, and my company currently resorts to maintaining a hacky
out-of-tree calibration tool to paper over these problems.
On Fri, Mar 23, 2018 at 7:00 AM, Pek
Here's the discussion and patch that addressed the issue I was mentioning:
https://lists.freedesktop.org/archives/wayland-devel/2017-September/035191.html
On Mon, Mar 12, 2018 at 3:51 PM, Matt Hoosier wrote:
> Hi,
>
> Unless you're using an unreleased version of Wes
Hi,
Unless you're using an unreleased version of Weston, I think you're
probably running into a bug that we fixed a few months ago in which
wl_buffer::release() events were prone to sit undispatched in the
server's outgoing queue until some other event happened to need
transmitted.
-Matt
On Mon,
On Mon, Jan 22, 2018 at 7:49 AM, Pekka Paalanen wrote:
> On Fri, 29 Dec 2017 15:09:28 -0600
> Matt Hoosier wrote:
>
>> Hi Lennart,
>>
>> On Mon, Dec 4, 2017 at 9:11 AM, Pekka Paalanen wrote:
>> > On Fri, 1 Dec 2017 18:25:35 +0100
>> > Lennart P
On Dec 29, 2017 15:32, "Mantas Mikulėnas" wrote:
On Fri, Dec 29, 2017 at 11:09 PM, Matt Hoosier
wrote:
>
> The approach that you and Pekka most recently put on record here:
>
> * User=foo
> * PAMName=weston
>
> with a /etc/pam.d/weston that just does minimal stuf
Hi Lennart,
On Mon, Dec 4, 2017 at 9:11 AM, Pekka Paalanen wrote:
> On Fri, 1 Dec 2017 18:25:35 +0100
> Lennart Poettering wrote:
>
>> On Fr, 01.12.17 13:42, Pekka Paalanen (ppaala...@gmail.com) wrote:
>>
>> > > > > This is racy, as the session ID is not really reliably predictable,
>> > > > > a
On Wed, Nov 8, 2017 at 1:30 AM, Pekka Paalanen wrote:
> On Tue, 7 Nov 2017 11:01:09 -0600
> Matt Hoosier wrote:
>
>> Hi Pekka,
>>
>> On Wed, Oct 25, 2017 at 10:09 AM, Ucan, Emre (ADITG/ESB)
>> wrote:
>> > Actually, IMO ivi-shell is not a proper waylan
On Mon, Dec 11, 2017 at 2:03 AM, Pekka Paalanen wrote:
> On Mon, 27 Nov 2017 08:54:54 -0600
> Matt Hoosier wrote:
>
>> From: Matt Hoosier
>>
>> In order to support system compositor instances, it is necessary to
>> allow clients' wl_display_connect() to fin
On Fri, Dec 8, 2017 at 4:26 AM, Quentin Glidic
wrote:
> On 12/8/17 11:22 AM, Quentin Glidic wrote:
>>
>> From: Matt Hoosier
>>
>> As discussed on
>>
>> https://lists.freedesktop.org/archives/wayland-devel/2017-August/034720.html,
>> it's usef
On Thu, Dec 7, 2017 at 2:05 AM, Pekka Paalanen wrote:
> On Tue, 5 Dec 2017 13:57:39 -0600
> Matt Hoosier wrote:
>
>> Hi all,
>>
>> The thing I'd like to arrange is for a device which is otherwise a
>> valid keyboard, not to get automatically vacuumed up int
Hi all,
The thing I'd like to arrange is for a device which is otherwise a
valid keyboard, not to get automatically vacuumed up into the Weston
DRM backend's usage of libinput.
Nowadays, Weston has delegated most of its former firsthand extraction
of UDev properties to libinput. Nothing exists (t
Hi Jonas (and Pekka),
How well does v4 address your requests?
-Matt
On Mon, Nov 27, 2017 at 9:00 AM, Matt Hoosier wrote:
> On Mon, Nov 27, 2017 at 3:16 AM, Pekka Paalanen wrote:
>> On Sat, 25 Nov 2017 08:11:43 -0600
>> Matt Hoosier wrote:
>>
>>> Hi Jonas, Pekk
On Sun, Nov 26, 2017 at 2:23 PM, ferreiradaselva
wrote:
> Hi,
>
> My first time posting here (sorry if I'm posting on the wrong place).
You're in the right place. Welcome!
>
> I'm working on this window creation framework
> (https://github.com/ferreiradaselva/swfw), and for the Wayland backend I
On Mon, Nov 27, 2017 at 3:16 AM, Pekka Paalanen wrote:
> On Sat, 25 Nov 2017 08:11:43 -0600
> Matt Hoosier wrote:
>
>> Hi Jonas, Pekka,
>>
>> I have no objection to making the tweaks that Jonas mentions, but I'm
>> wary of messing with the form of this patc
From: Matt Hoosier
In order to support system compositor instances, it is necessary to
allow clients' wl_display_connect() to find the compositor's listening
socket somewhere outside of XDG_RUNTIME_DIR. For a full account, see
the discussion beginning here:
https://lists.freed
00 PM, Jonas Ådahl wrote:
> On Tue, Nov 14, 2017 at 12:23:55PM -0600, Matt Hoosier wrote:
>> From: Matt Hoosier
>>
>> In order to support system compositor instances, it is necessary to
>> allow clients' wl_display_connect() to find the compositor'
On Fri, Nov 17, 2017 at 2:22 AM, Pekka Paalanen wrote:
> On Tue, 14 Nov 2017 12:23:55 -0600
> Matt Hoosier wrote:
>
>> From: Matt Hoosier
>>
>> In order to support system compositor instances, it is necessary to
>> allow clients' wl_display_connect() to fin
On Tue, Nov 14, 2017 at 8:22 AM, Pekka Paalanen wrote:
> On Fri, 10 Nov 2017 11:20:42 -0600
> Matt Hoosier wrote:
>
>> From: Matt Hoosier
>>
>> In order to support system compositor instances, it is necessary to
>> allow clients' wl_display_connect() to fin
On Tue, Nov 14, 2017 at 8:25 AM, Matt Hoosier wrote:
> On Tue, Nov 14, 2017 at 8:22 AM, Pekka Paalanen wrote:
>> On Fri, 10 Nov 2017 11:20:42 -0600
>> Matt Hoosier wrote:
>>
>>> From: Matt Hoosier
>>>
>>> In order to support system compositor
From: Matt Hoosier
In order to support system compositor instances, it is necessary to
allow clients' wl_display_connect() to find the compositor's listening
socket somewhere outside of XDG_RUNTIME_DIR. For a full account, see
the discussion beginning here:
https://lists.freed
On Tue, Nov 14, 2017 at 8:22 AM, Pekka Paalanen wrote:
> On Fri, 10 Nov 2017 11:20:42 -0600
> Matt Hoosier wrote:
>
>> From: Matt Hoosier
>>
>> In order to support system compositor instances, it is necessary to
>> allow clients' wl_display_connect() to fin
From: Matt Hoosier
In order to support system compositor instances, it is necessary to
allow clients' wl_display_connect() to find the compositor's listening
socket somewhere outside of XDG_RUNTIME_DIR. For a full account, see
the discussion beginning here:
https://lists.freed
Hi,
On Fri, Nov 10, 2017 at 5:37 AM, Pekka Paalanen wrote:
> On Thu, 9 Nov 2017 09:36:29 -0600
> Matt Hoosier wrote:
>
>> From: Matt Hoosier
>>
>> In order to support system compositor instances, it is necessary to
>> allow clients' wl_display_connec
On Thu, Nov 9, 2017 at 8:53 PM, Jonas Ådahl wrote:
> On Thu, Nov 09, 2017 at 09:36:29AM -0600, Matt Hoosier wrote:
>> From: Matt Hoosier
>>
>> In order to support system compositor instances, it is necessary to
>> allow clients' wl_display_connect() to find the
On Wed, Nov 8, 2017 at 2:16 AM, Pekka Paalanen wrote:
> On Tue, 7 Nov 2017 19:42:42 +
> Daniel Stone wrote:
>
>> Hi,
>>
>> On 3 November 2017 at 07:33, Pekka Paalanen wrote:
>
>> > - when the current socket search fails, add one more place to look
>> > in: /run/wayland/$WAYLAND_DISPLAY wit
From: Matt Hoosier
In order to support system compositor instances, it is necessary to
allow clients' wl_display_connect() to find the compositor's listening
socket somewhere outside of XDG_RUNTIME_DIR. For a full account, see
the discussion beginning here:
https://lists.freed
On Tue, Nov 7, 2017 at 11:58 AM, Quentin Glidic
wrote:
> On 11/7/17 6:01 PM, Matt Hoosier wrote:
>>
>> Hi Pekka,
>>
>> On Wed, Oct 25, 2017 at 10:09 AM, Ucan, Emre (ADITG/ESB)
>> wrote:
>>>
>>> Actually, IMO ivi-shell is not a proper wayl
Hi Pekka,
On Wed, Oct 25, 2017 at 10:09 AM, Ucan, Emre (ADITG/ESB)
wrote:
> Actually, IMO ivi-shell is not a proper wayland compositor. Because it is
> violating wayland protocol by not supporting wl_shell interface.
>
> Therefore, we have to at least support wl_shell interface in ivi-shell. Wh
Hi Pekka,
What do you think is a good amount of time to allow for people to
respond to your call for acks/nacks?
On Fri, Nov 3, 2017 at 8:33 AM, Carsten Haitzler wrote:
> On Fri, 3 Nov 2017 12:47:39 +0200 Pekka Paalanen said:
>
>> On Fri, 3 Nov 2017 11:04:27 +0100 (CET)
>> Jan Engelhardt wrote
On Tue, Sep 26, 2017 at 12:16 PM, Daniel Stone wrote:
> Add support for the GBM_BO_IMPORT_FD_MODIFIER path, which allows us to
> import multi-plane dmabufs, as well as format modifiers.
>
> Signed-off-by: Daniel Stone
> ---
> configure.ac | 3 -
> libweston/compositor-drm.c | 181
On Fri, Nov 3, 2017 at 2:46 AM, Pekka Paalanen wrote:
>
> On Thu, 2 Nov 2017 14:13:42 -0500
> Matt Hoosier wrote:
>
> > What sort of testing on this series would be most helpful? I figure that
> > you and pq have most of the code review covered, so the main
contribution
On Fri, Nov 3, 2017 at 2:33 AM, Pekka Paalanen wrote:
> On Thu, 2 Nov 2017 10:07:28 -0500
> Matt Hoosier wrote:
>
> > On Thu, Nov 2, 2017 at 3:36 AM, Pekka Paalanen
> wrote:
> >
> > > On Wed, 1 Nov 2017 13:44:50 -0500
> > > Matt Hoosier wrote
What sort of testing on this series would be most helpful? I figure that
you and pq have most of the code review covered, so the main contribution I
can make with the hardware available to me is to exercise this on
consumer-grade systems like Macbooks with Intel display controllers. Are
there are s
On Thu, Nov 2, 2017 at 3:36 AM, Pekka Paalanen wrote:
> On Wed, 1 Nov 2017 13:44:50 -0500
> Matt Hoosier wrote:
>
> > There has been a surge of recent interest in the details of using Wayland
> > on nontraditional systems that don't have the normal notion of hum
There has been a surge of recent interest in the details of using Wayland
on nontraditional systems that don't have the normal notion of human-user
login sessions. Discussions are ongoing about the details of how to manage
the allocation of TTYs and Weston's vision of the best practices for
assigni
nything else.
>
> > > -Original Message-
> > > From: wayland-devel [mailto:wayland-devel-
> > > boun...@lists.freedesktop.org] On Behalf Of Matt Hoosier
> > > Sent: Montag, 30. Oktober 2017 14:28
> > > To: Pekka Paalanen
> > >
On Mon, Oct 30, 2017 at 10:02 AM, Pekka Paalanen
wrote:
> On Mon, 30 Oct 2017 15:20:42 +0100
> Emre Ucan wrote:
>
> > weston does not need to be root.
> > It requires adjusting ownership on the given tty device.
> >
> > If weston does not have proper rights, it will get
> > an error at startup a
On Mon, Oct 30, 2017 at 5:10 AM, Pekka Paalanen wrote:
> On Fri, 27 Oct 2017 09:10:02 -0500
> Matt Hoosier wrote:
>
> > On Fri, Oct 27, 2017 at 8:05 AM, Pekka Paalanen
> wrote:
> >
> > > On Fri, 27 Oct 2017 07:05:13 -0500
> > > Matt Hoosier wrote:
This question is mainly meant for the input device developers that hang out
here.
Does anybody know of a de facto network protocol that should be used for
relaying input devices across a network? I don't have full remote-desktop
situations in mind -- this is narrowly a question about devices with
On Fri, Oct 27, 2017 at 8:05 AM, Pekka Paalanen wrote:
> On Fri, 27 Oct 2017 07:05:13 -0500
> Matt Hoosier wrote:
>
> > HI Pekka,
> >
> > On Thu, Oct 26, 2017 at 2:06 AM, Pekka Paalanen
> wrote:
> >
> > > On Tue, 24 Oct 2017 08:26:04 -0500
> &g
HI Pekka,
On Thu, Oct 26, 2017 at 2:06 AM, Pekka Paalanen wrote:
> On Tue, 24 Oct 2017 08:26:04 -0500
> Matt Hoosier wrote:
>
> > On Tue, Oct 24, 2017 at 1:33 AM, Pekka Paalanen
> wrote:
> > > On Mon, 23 Oct 2017 14:37:37 -0500
> > > Matt Hoosier wrote:
&
On Wed, Oct 25, 2017 at 2:09 AM, Pekka Paalanen wrote:
> Hi,
>
> the very reason why ivi-shell ever came to be was that the operating
> environment of graphical applications in IVI was so different from a
> normal desktop, that it was simply impossible to have desktop
> applications work in a mea
I'm not at all familiar with the internal implementation of ivi-shell, so I
can't give much meaningful review. But I am very much in favor of this
patch series. Without wl_shell and xdg_shell support, I've never been able
to really give ivi-shell serious consideration on my products. The ability
to
On Tue, Oct 24, 2017 at 1:33 AM, Pekka Paalanen wrote:
> On Mon, 23 Oct 2017 14:37:37 -0500
> Matt Hoosier wrote:
>
>> It would be nice for non-session uses of Weston (embedded systems) if
>> the controlling TTY didn't need to be manually supplied.
>>
>>
It would be nice for non-session uses of Weston (embedded systems) if
the controlling TTY didn't need to be manually supplied.
Has anybody suggested using something like VT_OPENQRY in the
weston-launcher code to pick a TTY if one wasn't manually given? (Or
if that's too auto-magic for taste here,
I'm having some trouble joining the Wayland channel on Freenode. Is
there a specific person to contact about that?
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Ping
On Tue, Sep 5, 2017 at 8:05 AM, Matt Hoosier wrote:
> As discussed on
> https://lists.freedesktop.org/archives/wayland-devel/2017-August/034720.html,
> it's useful for the shell implementation to know when these change,
> for example to relay the information on to ta
Hi Deepak,
On Fri, Oct 20, 2017 at 11:50 AM, Deepak Jois wrote:
> Hi
>
> I have read the Wayland docs and skimmed through the API reference,
> and I am trying to understand some concepts better. The questions
> below are probably a bit naive, but I appreciate any
> suggestions/explanations.
>
> T
On Wed, Oct 18, 2017 at 4:23 AM, Quentin Glidic
wrote:
> + fd = shm_open("/wayland-cursor-shared", O_CREAT | O_RDWR, 0);
> + shm_unlink("/wayland-cursor-shared");
This seems to be a departure from the anonymous behavior that
mkstemp() previously offered. shm_open() says that it will o
On Tue, Oct 10, 2017 at 11:53 AM, Daniel Stone wrote:
> That more or less makes sense at the moment, though there has been
> quite a bit of work on less insane remoting within Weston. And then
> GNOME is using PipeWire for this. But anyway, you probably know this
> and it's not your immediate ques
Hi all,
My organization maintains a small patch against the DRM compositor
that causes it to register another output. This output accepts the
usual compositor scenegraph, does the rendering down to a primary
plane, and then funnels the resulting GBM buffer through a codepath
that does video compre
On Tue, Sep 26, 2017 at 12:15 PM, Daniel Stone wrote:
> Hi,
> Here's a cleaned-up and fully-tested version of the atomic series.
Hi;
Just wondering: do you maintain these in a publicly fetchable repo
somewhere? I didn't turn up anything after some light searching --
there's git://people.freedesk
Done:
https://lists.freedesktop.org/archives/wayland-devel/2017-September/035191.html
On Tue, Sep 26, 2017 at 2:28 AM, Pekka Paalanen wrote:
> On Mon, 25 Sep 2017 10:31:35 -0500
> Matt Hoosier wrote:
>
>> This change replaces a queued emission of buffer-release events (which
.
v2:
More information about the historical reasons why this change hadn't
happened yet, and the consensus to finally move ahead with it can be
found at the discussion terminating in this message:
https://lists.freedesktop.org/archives/wayland-devel/2017-September/035147.html
Signed-off-by:
On Fri, Sep 22, 2017 at 6:18 PM, Matt Hoosier wrote:
> On Fri, Sep 22, 2017 at 10:24 AM, Pekka Paalanen wrote:
>> On Wed, 20 Sep 2017 07:11:57 -0700
>> Daniel Stone wrote:
>>
>>> Hi Matt,
>>>
>>> On 20 September 2017 at 05:48, Matt Hoosi
.
Signed-off-by: Matt Hoosier
---
clients/nested.c | 3 +--
libweston/compositor.c | 3 +--
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/clients/nested.c b/clients/nested.c
index e9070e9b..e2bdf684 100644
--- a/clients/nested.c
+++ b/clients/nested.c
@@ -228,8 +228,7
On Fri, Sep 22, 2017 at 10:24 AM, Pekka Paalanen wrote:
> On Wed, 20 Sep 2017 07:11:57 -0700
> Daniel Stone wrote:
>
>> Hi Matt,
>>
>> On 20 September 2017 at 05:48, Matt Hoosier wrote:
>> > On a related subject, there was discussion back at
>> > h
On Tue, Sep 19, 2017 at 6:46 PM, Daniel Stone wrote:
> Signed-off-by: Daniel Stone
> ---
> Makefile.am| 1 +
> unstable/linux-explicit-synchronization/README | 5 +
> .../linux-explicit-synchronization-unstable-v1.xml | 208
> +
On Tue, Sep 5, 2017 at 9:00 AM, Daniel Stone wrote:
> It can't be correct to raise it to the cursor plane either, since both
> cursor and overlay planes strictly stack above the scanout plane. I
> guess this would read a lot easier with:
> if (picked_scanout)
> next_plane = primary;
> at t
rface
definition public, new functions are introduced for attaching
listeners to these signals.
Signed-off-by: Matt Hoosier
---
libweston-desktop/libweston-desktop.h | 3 +++
libweston-desktop/surface.c | 12
2 files changed, 15 insertions(+)
diff --git a/libweston-de
On Thu, Aug 24, 2017 at 9:24 AM, Matt Hoosier wrote:
> As discussed in the following thread:
>
> https://lists.freedesktop.org/archives/wayland-devel/2017-August/034755.html
>
> the existing plane assignment in the DRM backend is vulnerable to
> accidental masking of the i
On Thu, Aug 24, 2017 at 2:49 AM, Pekka Paalanen wrote:
> Hi,
>
> using connector name to describe the connected monitor doesn't sound
> right to me.
I didn't really like it either. Thanks for the suggestions below.
>
> If you actually need the connector name in clients then let's
> design an ext
On Tue, Aug 15, 2017 at 9:16 AM, Daniel Stone wrote:
>
> No, that's all the way broken. I assume the only way this hasn't yet
> bitten us is that the background in stock desktop-shell is a SHM-only
> client, so won't get promoted to a plane.
>
> That should be fixed in the atomic branch though, AF
As discussed in the following thread:
https://lists.freedesktop.org/archives/wayland-devel/2017-August/034755.html
the existing plane assignment in the DRM backend is vulnerable to
accidental masking of the intended fullscreen surface. This change
adds a simple stateful memory to the plane assign
On embedded systems, EDID is typically unavailble for connectors on buses
such as LVDS or DSI. This change enhances the original opportunistic
naming done in 2b2092adb499d8cdc10390cf19876706bcfe69cb to report the
make and model of an output according to the KMS connector (e.g., "DSI-1")
if no dynam
Currently the DRM backend ends up picking the bottom-most view which meets
all the checks for eligibility, for direct scanout usage. If more than one
such view exists, we get a visual result counter to expectations -- it
should be the highest-sorted such view that the user sees.
The big loop in dr
Okay, this one should be ready to review. Sorry for the noise on the first
attempt.
On Tue, Aug 8, 2017 at 10:56 AM, Matt Hoosier
wrote:
> It's useful for the shell implementation to know when these change,
> for example to relay the information on to taskbars or similar.
>
This revision was broken. Disregard, I'm re-sending.
On Tue, Aug 8, 2017 at 10:45 AM, Matt Hoosier
wrote:
> It's useful for the shell implementation to know when these change,
> for example to relay the information on to taskbars or similar.
>
> To avoid ABI changes o
igned-off-by: Matt Hoosier
---
libweston-desktop/libweston-desktop.h | 3 +++
libweston-desktop/surface.c | 12
2 files changed, 15 insertions(+)
diff --git a/libweston-desktop/libweston-desktop.h
b/libweston-desktop/libweston-desktop.h
index 03b04c7b..c43568ac 100644
1 - 100 of 117 matches
Mail list logo
