Acked-by: Jason Ekstrand
On Thu, Jun 28, 2018 at 6:26 AM, Johan Klokkhammer Helsing <
johan.hels...@qt.io> wrote:
> Although it would probably default to the license at the root of the
> repository anyway, it's best to be explicit about it, and also be
> consistent with the other extensions.
>
>
Hi Pekka,
Thanks a lot for making time for reviewing this proposal.
On Friday 29 June 2018 06:08 PM, Pekka Paalanen wrote:
On Sat, 16 Jun 2018 16:03:20 +0530
Ramalingam C wrote:
Hello all,
I am trying to call out the complete sequence that we are aiming to
achieve. Please correct me if some
Pekka,
Thanks a lot for the responses.
On Friday 29 June 2018 04:28 PM, Pekka Paalanen wrote:
On Mon, 18 Jun 2018 15:56:40 +0530
Ramalingam C wrote:
On Monday 18 June 2018 03:52 PM, Pekka Paalanen wrote:
On Mon, 18 Jun 2018 14:32:32 +0530
Ramalingam C wrote:
On Monday 18 June 2018 02:
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 Thu, 24 May 2018 06:20:05 +
"Ray, Ian (GE Healthcare)" wrote:
> > On 23 May 2018, at 15.47, Pekka Paalanen wrote:
> >
> > From: Pekka Paalanen
> >
> > Hi,
> >
> > this patch depends on the last patch of the clone mode series:
> > https://patchwork.freedesktop.org/patch/217906/
> >
>
On Fri, 29 Jun 2018 10:08:17 +
"Ray, Ian (GE Healthcare)" wrote:
> > On 6 Jun 2018, at 14.30, Pekka Paalanen wrote:
> >
> > 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 iden
On Sat, 16 Jun 2018 16:03:20 +0530
Ramalingam C wrote:
> Hello all,
>
> I am trying to call out the complete sequence that we are aiming to
> achieve. Please correct me if something is missed out. I am hoping
> that with this sequence and interface we could get the
> functionalities of HDCP what
This adds a function to detect the first framebuffer device in the
current seat. Instead of hardcoding /dev/fb0, detect the device
with udev, favoring the boot_vga device, and falling back to the
first framebuffer device in the seat if there is none. This is very
similar to what compositor-drm does
As only seat0 supports TTYs, this changes the logind launcher where
it detects a TTY, only if the seat is seat0. This has only been
tested for logind
---
libweston/launcher-logind.c | 23 +--
libweston/launcher-util.c | 4
2 files changed, 17 insertions(+), 10 deletions
This will allow the seat to be set by the environment as pam_systemd typically
sets the XDG_SEAT variable
---
compositor/main.c | 2 +-
libweston/compositor-drm.c | 11 ---
libweston/compositor-drm.h | 3 ++-
man/weston-drm.man | 7 +--
4 files changed, 16 insertion
These patches make Weston handle multiple seats. Fixes from the last
attempt include updating fbdev_set_screen_info , updating some fuzz,
and making the selection of the framebuffer device similar to
compositor-drm.c by favoring the boot_vga device, and making
requested changes. These now address
This attempts to wake up secondary framebuffer devices
(/dev/fb1 and up) as usually these devices start powered off, and
the FBIOPUT_VSCREENINFO ioctl turns it on. This was tested on a
qemu system with the options:
-vga none -device VGA,id=video0 -device secondary-vga,id=video1 \
-device secondary
The framebuffer backend now detects the framebuffer device
dynamically. Don't assume that the framebuffer device is /dev/fb0
---
compositor/main.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/compositor/main.c b/compositor/main.c
index 068cdd8f..f1ee02b4 100644
--- a/compositor/main.c
+++
This allows the fbdev backend to run on, and use devices from the
specified seat, similar to the drm backend.
---
compositor/main.c| 2 ++
libweston/compositor-fbdev.c | 10 +-
libweston/compositor-fbdev.h | 9 +
3 files changed, 20 insertions(+), 1 deletion(-)
diff
> On 6 Jun 2018, at 14.30, Pekka Paalanen wrote:
>
> 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
On Mon, 18 Jun 2018 15:56:40 +0530
Ramalingam C wrote:
> On Monday 18 June 2018 03:52 PM, Pekka Paalanen wrote:
> > On Mon, 18 Jun 2018 14:32:32 +0530
> > Ramalingam C wrote:
> >
> >> On Monday 18 June 2018 02:23 PM, Pekka Paalanen wrote:
> >>> On Mon, 18 Jun 2018 13:38:09 +0530
> >>> Ramali
> On 25 Jun 2018, at 15.00, Pekka Paalanen wrote:
>
> Ping?
>
> Would be really nice to get this final patch of a series of around 130+
> patches merged. It only needs an objective technical review, the
> Acked-by's already cover the subjective review.
>
>
> Thanks,
> pq
>
> On Wed, 6 Jun
> From: Markus Ongyerth
This should maybe be a Signed-off-by at the end of the commit message?
> The wording in xdg-shell's `set_*` requests implies the compositor
> *will* honour the client's request.
> This would give clients the control over their actual state, while the
> general expectation
On Fri, 29 Jun 2018 10:46:16 +0200
Markus Ongyerth wrote:
> Urgh, of course I forget to mention something when I write mails.
>
> This is current RFC quality, not actual patch. Should this be something
> people
> are interested in, I think it should live mostly in connection.c and be
> suppor
> From: Markus Ongyerth
>
> The xdg-shell documentation had part of the maximized state render
> implications in the `set_maximized` request documentation, not the
> actual state.
> This moves the relevant lines into the state description.
>
> Signed-off-by: Markus Ongyerth
> Reviewed-By: Mike Bl
From: Markus Ongyerth
The `[un]set_(fullscreen/maximized)` requests text requires compositors
to respon to the request with a configure event.
with the asynchronous nature of wayland protocols, this provides
essentially no benefit and might entice consumers to rely on details
that are not guaran
From: Markus Ongyerth
The xdg-shell documentation had part of the maximized state render
implications in the `set_maximized` request documentation, not the
actual state.
This moves the relevant lines into the state description.
Signed-off-by: Markus Ongyerth
Reviewed-By: Mike Blumenkrantz
---
From: Markus Ongyerth
The wording in xdg-shell's `set_*` requests implies the compositor
*will* honour the client's request.
This would give clients the control over their actual state, while the
general expectation is that clients kindly ask for state changes which
the compositor may follow.
Thi
From: Markus Ongyerth
Hi,
This is a v2 of a rather old patch series I more or less forgot about [1].
The previous version of patch 1 is [2]
The patch 2 and 3 are based on are: [3]
Patch 1 should still be quite straight forward.
Patch 2 is the well received part of the previous Patch 2.
Patch
On Wed, 27 Jun 2018 20:44:22 -0400
nerdopolis wrote:
> The framebuffer backend now detects the framebuffer device
> dynamically. Don't assume that the framebuffer device is /dev/fb0
> ---
> compositor/main.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/compositor/main.c b/composit
On Wed, 27 Jun 2018 20:44:19 -0400
nerdopolis wrote:
> As only seat0 supports TTYs, this changes the logind launcher where
> it detects a TTY, only if the seat is seat0. This has only been
> tested for logind
> ---
> libweston/launcher-logind.c | 23 +--
> libweston/launcher-
On Wed, 27 Jun 2018 20:44:18 -0400
nerdopolis wrote:
> This allows the fbdev backend to run on, and use devices from the
> specified seat, similar to the drm backend.
> ---
> compositor/main.c| 2 ++
> libweston/compositor-fbdev.c | 10 +-
> libweston/compositor-fbdev.h | 9
On Wed, 27 Jun 2018 20:44:21 -0400
nerdopolis wrote:
> This adds a function to detect the first framebuffer device in the
> current seat. Instead of hardcoding /dev/fb0, detect the device
> with udev, favoring the boot_vga device, and falling back to the
> first framebuffer device in the seat if
On Wed, 27 Jun 2018 20:44:20 -0400
nerdopolis wrote:
> This attempts to wake up secondary framebuffer devices
> (/dev/fb1 and up) as usually these devices start powered off, and
> the FBIOPUT_VSCREENINFO ioctl turns it on. This was tested on a
> qemu system with the options:
>
> -vga none -devic
On Wed, 27 Jun 2018 20:44:17 -0400
nerdopolis wrote:
> This will allow the seat to be set by the environment as pam_systemd typically
> sets the XDG_SEAT variable
> ---
> compositor/main.c | 2 +-
> libweston/compositor-drm.c | 11 ---
> libweston/compositor-drm.h | 3 ++-
> m
Urgh, of course I forget to mention something when I write mails.
This is current RFC quality, not actual patch. Should this be something people
are interested in, I think it should live mostly in connection.c and be
supported by both -server and -client libraries.
I'm also not sure whether the
From: Markus Ongyerth
Add environment variable WAYLAND_DEBUG_INTERFACES for filtering the
output of WAYLAND_DEBUG logs.
While WAYLAND_DEBUG is a pretty powerful and useful debug tool, printing
everything has a few downsides.
1) It's a full keylogger (getting debug-logs from users)
2) It can be o
On Tue, 26 Jun 2018 14:20:53 -0300
Matheus Santana wrote:
> button-test was moved to pointer-test.
>
> Signed-off-by: Matheus Santana
Pushed:
8119f6f..6aff88a master -> master
The website will autoupdate in a moment.
Thanks,
pq
> ---
> testing.html | 24
> 1
On Thu, 28 Jun 2018 18:59:01 +0100
Emil Velikov wrote:
> On 28 June 2018 at 10:58, Quentin Glidic
> wrote:
> > On 6/27/18 3:04 PM, Emil Velikov wrote:
> >>
> >> From: Emil Velikov
> >>
> >> Adding those to configure.ac ensures that:
> >> - the weston.ini files are {re,}generated only when n
34 matches
Mail list logo
