Re: Fbdev-backend removal from Weston (Re: Upcoming release)

On Wednesday, January 23, 2019 4:09:44 AM EST Pekka Paalanen wrote: > On Tue, 22 Jan 2019 22:46:02 -0500 > nerdopolis wrote: > > > On Tuesday, January 22, 2019 9:55:15 AM EST Pekka Paalanen wrote: > > > > > > > On Tue, 22 Jan 2019 10:17:32 +0200 > > &g

Re: Fbdev-backend removal from Weston (Re: Upcoming release)

On Tuesday, January 22, 2019 9:55:15 AM EST Pekka Paalanen wrote: > Let's make the title more catchy, so that people who care about fbdev > would notice. > > > On Tue, 22 Jan 2019 10:17:32 +0200 > Pekka Paalanen wrote: > > > On Mon, 21 Jan 2019 20:3

Re: Upcoming release

On Friday, January 18, 2019 5:20:40 PM EST Derek Foreman wrote: > Hi all, > > It's been quite some time since our last weston release, and there's > been some discussion of getting the next one out in the January to March > timeframe (this would be the last release to have an autotools build, btw)

[PATCH v9 5/6] compositor-fbdev: detect the first fb device in the seat

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

[PATCH v9 3/6] launcher-logind: only get a VT on seat0, as only seat0 supports VTs

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

[PATCH v9 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

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

[PATCH v9 0/6] Make Weston multiseat aware

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

[PATCH v9 4/6] compositor-fbdev: set fb device info upon the first run.

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

[PATCH v9 6/6] main: don't configure /dev/fb0 by default

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 +++

[PATCH v9 2/6] compositor-fbdev: support the --seat option, (and XDG_SEAT variable)

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

[PATCH v7 0/6] Make Weston multiseat aware

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 addre

[PATCH v8 6/6] main: don't configure /dev/fb0 by default

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 +++

[PATCH v8 3/6] launcher-logind: only get a VT on seat0, as only seat0 supports VTs

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

[PATCH v8 5/6] compositor-fbdev: detect the first fb device in the seat

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

[PATCH v8 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

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

[PATCH v8 4/6] compositor-fbdev: set fb device info upon the first run.

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

[PATCH v8 2/6] compositor-fbdev: support the --seat option, (and XDG_SEAT variable)

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

[PATCH v7 4/6] compositor-fbdev: set fb device info upon the first run.

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

[PATCH v7 2/6] compositor-fbdev: support the --seat option, (and XDG_SEAT variable)

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

[PATCH v7 5/6] compositor-fbdev: detect the first fb device in the seat

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

[PATCH v7 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

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

[PATCH v7 6/6] main: don't configure /dev/fb0 by default

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 +++

[PATCH v7 3/6] launcher-logind: only get a VT on seat0, as only seat0 supports VTs

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 | 22 -- libweston/launcher-util.c | 4 2 files changed, 16 insertions(+), 10 deletions(

[PATCH v7 0/6] Make Weston multiseat aware

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

Re: [PATCH v6 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

On Tuesday, June 12, 2018 7:23:19 AM EDT Pekka Paalanen wrote: > On Tue, 23 Jan 2018 22:15:43 -0500 > nerdopolis wrote: > > > This will allow the seat to be set by the environment as pam_systemd > > typically > > sets the XDG_SEAT variable > > --- &g

Re: [PATCH v6 0/6] Make Weston multiseat aware

On Friday, June 8, 2018 9:40:47 AM EDT Pekka Paalanen wrote: > On Fri, 08 Jun 2018 08:23:02 -0400 > nerdopolis wrote: > > > On Tuesday, January 23, 2018 10:15:42 PM EDT you wrote: > > > These patches make Weston handle multiple seats. Fixes from the last > &

Re: [PATCH v6 0/6] Make Weston multiseat aware

favoring the boot_vga device, and making > requested changes > > nerdopolis (6): > libweston: set the seat automatically based on the XDG_SEAT > environment variable > libweston: fbdev: support the --seat option, (and XDG_SEAT variable) > launcher-logind: only

Re: [PATCH v6 0/6] Make Weston multiseat aware

On Tuesday, January 23, 2018 10:15:42 PM EDT nerdopolis wrote: > 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 > composi

[PATCH v6 2/6] libweston: fbdev: support the --seat option, (and XDG_SEAT variable)

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 | 1 + 3 files changed, 12 insertions(+), 1 deletion(-) diff --git a/

[PATCH v6 3/6] launcher-logind: only get a VT on seat0, as only seat0 supports VTs

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 | 22 -- libweston/launcher-util.c | 4 2 files changed, 16 insertions(+), 10 deletions(

[PATCH v6 6/6] main: don't configure /dev/fb0 by default

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 ecd034b9..02de108b 100644 --- a/compositor/main.c +++

[PATCH v6 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

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 | 5 + man/weston-drm.man | 7 +-- 3 files changed, 11 insertions(+), 3 deletions(-) diff --git a/compositor/

[PATCH v6 4/6] libweston: fbdev: set fb device info upon the first run.

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

[PATCH v6 0/6] Make Weston multiseat aware

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 nerdopolis (6

[PATCH v6 5/6] libweston: fbdev: Attempt to detect the first framebuffer device in the seat. instead of defaulting to /dev/fb0

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

Re: [PATCH v5 5/7] libweston: fbdev: Attempt to detect the first framebuffer device in the seat. instead of defaulting to /dev/fb0

On Monday, January 22, 2018 4:50:35 AM EST Pekka Paalanen wrote: > On Fri, 29 Dec 2017 13:31:51 -0500 > nerdopolis wrote: > > > This adds a function to detect the first framebuffer device in the > > current seat. Instead of hardcoding /dev/fb0, use udev to find the > &g

[PATCH v5 1/7] libweston: set the seat automatically based on the XDG_SEAT environment variable

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 | 5 + man/weston-drm.man | 7 +-- 3 files changed, 11 insertions(+), 3 deletions(-) diff --git a/compositor/

[PATCH v5 5/7] libweston: fbdev: Attempt to detect the first framebuffer device in the seat. instead of defaulting to /dev/fb0

This adds a function to detect the first framebuffer device in the current seat. Instead of hardcoding /dev/fb0, use udev to find the first framebuffer device in the seat. --- libweston/compositor-fbdev.c | 45 +--- 1 file changed, 42 insertions(+), 3 deleti

[PATCH v5 4/7] libweston: fbdev: set fb device info upon the first run.

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

[PATCH v5 3/7] launcher-logind: only get a VT on seat0, as only seat0 supports VTs

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 | 22 -- libweston/launcher-util.c | 4 2 files changed, 16 insertions(+), 10 deletions(

[PATCH v5 7/7] libweston: fbdev: Follow the same logic as compositor-drm, and favor the boot_vga device

virtual framebuffer devices that are created by a modesetting driver have the same parent as the drm card devices. --- libweston/compositor-fbdev.c | 40 ++-- 1 file changed, 34 insertions(+), 6 deletions(-) diff --git a/libweston/compositor-fbdev.c b/libwesto

[PATCH v5 6/7] main: don't configure /dev/fb0 by default

--- compositor/main.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/compositor/main.c b/compositor/main.c index ecd034b9..02de108b 100644 --- a/compositor/main.c +++ b/compositor/main.c @@ -1454,9 +1454,6 @@ load_fbdev_backend(struct weston_compositor *c, parse_options(fbdev_opti

[PATCH v5 0/7] Make Weston multiseat aware

nerdopolis (7): libweston: set the seat automatically based on the XDG_SEAT environment variable libweston: fbdev: support the --seat option, (and XDG_SEAT variable) launcher-logind: only get a VT on seat0, as only seat0 supports VTs libweston: fbdev: set fb device info upon the first run

[PATCH v5 2/7] libweston: fbdev: support the --seat option, (and XDG_SEAT variable)

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 | 1 + 3 files changed, 12 insertions(+), 1 deletion(-) diff --git a/

[PATCH v4 5/6] libweston: fbdev: Attempt to detect the first framebuffer device in the seat. instead of defaulting to /dev/fb0

This adds a function to detect the first framebuffer device in the current seat. Instead of hardcoding /dev/fb0, use udev to find the first framebuffer device in the seat. --- libweston/compositor-fbdev.c | 45 +--- 1 file changed, 42 insertions(+), 3 deleti

[PATCH v4 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

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 | 5 + man/weston-drm.man | 7 +-- 3 files changed, 11 insertions(+), 3 deletions(-) diff --git a/compositor/

[PATCH v4 6/6] main: don't configure /dev/fb0 by default

--- compositor/main.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/compositor/main.c b/compositor/main.c index f88608cd..cd07a6bb 100644 --- a/compositor/main.c +++ b/compositor/main.c @@ -1450,9 +1450,6 @@ load_fbdev_backend(struct weston_compositor *c, parse_options(fbdev_opti

[PATCH v4 2/6] libweston: fbdev: support the --seat option, (and XDG_SEAT variable)

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 | 1 + 3 files changed, 12 insertions(+), 1 deletion(-) diff --git a/

[PATCH v4 3/6] launcher-logind: only get a VT on seat0, as only seat0 supports VTs

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 | 22 -- libweston/launcher-util.c | 4 2 files changed, 16 insertions(+), 10 deletions(

[PATCH v4 4/6] libweston: fbdev: set fb device info upon the first run.

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

Re: [PATCH 4/6] libweston: fbdev: set fb device info upon the first run.

On Tuesday, October 3, 2017 2:44:47 AM EDT Pekka Paalanen wrote: > On Mon, 02 Oct 2017 23:14:26 -0400 > nerdopolis wrote: > > > On Tuesday, September 26, 2017 9:45:43 AM EDT Pekka Paalanen wrote: > > > On Thu, 14 Sep 2017 23:08:51 -0400 > > > nerdopolis wro

[PATCH v3 3/6] launcher-logind: only get a VT on seat0, as only seat0 supports VTs

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 | 24 ++-- libweston/launcher-util.c | 4 2 files changed, 18 insertions(+), 10 deletion

[PATCH v3 4/6] libweston: fbdev: set fb device info upon the first run.

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

[PATCH v3 2/6] libweston: fbdev: support the --seat option, (and XDG_SEAT variable)

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 | 1 + 3 files changed, 12 insertions(+), 1 deletion(-) diff --git a/

[PATCH v3 5/6] libweston: fbdev: Attempt to detect the first framebuffer device in the seat. instead of defaulting to /dev/fb0

This adds a function to detect the first framebuffer device in the current seat. Instead of hardcoding /dev/fb0, use udev to find the first framebuffer device in the seat. --- libweston/compositor-fbdev.c | 45 +--- 1 file changed, 42 insertions(+), 3 deleti

[PATCH v3 6/6] main: don't configure /dev/fb0 by default

--- compositor/main.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/compositor/main.c b/compositor/main.c index f88608cd..cd07a6bb 100644 --- a/compositor/main.c +++ b/compositor/main.c @@ -1450,9 +1450,6 @@ load_fbdev_backend(struct weston_compositor *c, parse_options(fbdev_opti

[PATCH v3 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

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 | 5 + man/weston-drm.man | 7 +-- 3 files changed, 11 insertions(+), 3 deletions(-) diff --git a/compositor/

[PATCH v2 4/6] libweston: fbdev: set fb device info upon the first run.

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

[PATCH v2 2/6] libweston: fbdev: support the --seat option, (and XDG_SEAT variable)

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 | 1 + 3 files changed, 12 insertions(+), 1 deletion(-) diff --git a/

[PATCH v2 3/6] launcher-logind: only get a VT on seat0, as only seat0 supports VTs

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 | 22 -- libweston/launcher-util.c | 4 2 files changed, 16 insertions(+), 10 deletions(

[PATCH v2 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

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 | 5 + man/weston-drm.man | 7 +-- 3 files changed, 11 insertions(+), 3 deletions(-) diff --git a/compositor/

[PATCH v2 6/6] main: don't configure /dev/fb0 by default

--- compositor/main.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/compositor/main.c b/compositor/main.c index f88608cd..cd07a6bb 100644 --- a/compositor/main.c +++ b/compositor/main.c @@ -1450,9 +1450,6 @@ load_fbdev_backend(struct weston_compositor *c, parse_options(fbdev_opti

[PATCH v2 5/6] libweston: fbdev: Attempt to detect the first framebuffer device in the seat. instead of defaulting to /dev/fb0

This adds a function to detect the first framebuffer device in the current seat. Instead of hardcoding /dev/fb0, use udev to find the first framebuffer device in the seat. --- libweston/compositor-fbdev.c | 45 +--- 1 file changed, 42 insertions(+), 3 deleti

Re: [PATCH 4/6] libweston: fbdev: set fb device info upon the first run.

On Tuesday, September 26, 2017 9:45:43 AM EDT Pekka Paalanen wrote: > On Thu, 14 Sep 2017 23:08:51 -0400 > nerdopolis wrote: > > > On Wednesday, September 6, 2017 8:17:21 AM EDT nerdopolis wrote: > > > This attempts to wake up secondary framebuffer devices > >

Re: [PATCH 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

On Tuesday, September 26, 2017 9:17:37 AM EDT you wrote: > On Wed, 6 Sep 2017 08:17:18 -0400 > nerdopolis wrote: > > > --- > > Hi, > > the commit message should contain at least briefly why we want this. I > have a feeling this is the right thing to do, but I can

Re: [PATCH 5/6] libweston: fbdev: Attempt to detect the first framebuffer device in the seat. instead of defaulting to /dev/fb0

On Tuesday, September 26, 2017 10:00:47 AM EDT Pekka Paalanen wrote: > On Wed, 6 Sep 2017 08:17:22 -0400 > nerdopolis wrote: > > > --- > > libweston/compositor-fbdev.c | 35 +-- > > 1 file changed, 33 insertions(+), 2 deletions(-) >

Re: [PATCH 4/6] libweston: fbdev: set fb device info upon the first run.

On Wednesday, September 6, 2017 8:17:21 AM EDT 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 option

[PATCH 6/6] main: don't configure /dev/fb0 by default

--- compositor/main.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/compositor/main.c b/compositor/main.c index f88608cd..cd07a6bb 100644 --- a/compositor/main.c +++ b/compositor/main.c @@ -1450,9 +1450,6 @@ load_fbdev_backend(struct weston_compositor *c, parse_options(fbdev_opti

[PATCH 2/6] libweston: fbdev: support the --seat option, (and XDG_SEAT variable)

--- compositor/main.c| 2 ++ libweston/compositor-fbdev.c | 5 - libweston/compositor-fbdev.h | 1 + 3 files changed, 7 insertions(+), 1 deletion(-) diff --git a/compositor/main.c b/compositor/main.c index 61bda282..f88608cd 100644 --- a/compositor/main.c +++ b/compositor/main.c @

[PATCH 4/6] libweston: fbdev: set fb device info upon the first run.

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

[PATCH 5/6] libweston: fbdev: Attempt to detect the first framebuffer device in the seat. instead of defaulting to /dev/fb0

--- libweston/compositor-fbdev.c | 35 +-- 1 file changed, 33 insertions(+), 2 deletions(-) diff --git a/libweston/compositor-fbdev.c b/libweston/compositor-fbdev.c index a9cc08be..99362b8a 100644 --- a/libweston/compositor-fbdev.c +++ b/libweston/compositor-fbdev.

[PATCH 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

--- compositor/main.c| 2 +- libweston/compositor-drm.c | 5 + libweston/compositor-fbdev.c | 5 + man/weston-drm.man | 7 +-- 4 files changed, 16 insertions(+), 3 deletions(-) diff --git a/compositor/main.c b/compositor/main.c index 0615d87e..61bda282 100644 -

[PATCH 3/6] launcher-logind: only get a VT on seat0, as only seat0 supports VTs

--- libweston/launcher-logind.c | 22 -- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/libweston/launcher-logind.c b/libweston/launcher-logind.c index a069bd4f..11627590 100644 --- a/libweston/launcher-logind.c +++ b/libweston/launcher-logind.c @@ -762,18 +762

[PATCH 0/6] libweston: Support multiple seats better

I am resending as I messed up one of the commit messages, which resulted in a very long subject by mistake. These patches fix issues with Weston where it supports multiple seats better. Firstly supporting automatically detecting the seat to use, by using the XDG_SEAT variable set by logind if the

[PATCH 3/6] launcher-logind: only get a VT on seat0, as only seat0 supports VTs

--- libweston/launcher-logind.c | 22 -- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/libweston/launcher-logind.c b/libweston/launcher-logind.c index a069bd4f..11627590 100644 --- a/libweston/launcher-logind.c +++ b/libweston/launcher-logind.c @@ -762,18 +762

[PATCH 5/6] libweston: fbdev: Attempt to detect the first framebuffer device in the seat, instead of defaulting to /dev/fb0

--- libweston/compositor-fbdev.c | 35 +-- 1 file changed, 33 insertions(+), 2 deletions(-) diff --git a/libweston/compositor-fbdev.c b/libweston/compositor-fbdev.c index a9cc08be..99362b8a 100644 --- a/libweston/compositor-fbdev.c +++ b/libweston/compositor-fbdev.

[PATCH 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

--- compositor/main.c| 2 +- libweston/compositor-drm.c | 5 + libweston/compositor-fbdev.c | 5 + man/weston-drm.man | 7 +-- 4 files changed, 16 insertions(+), 3 deletions(-) diff --git a/compositor/main.c b/compositor/main.c index 0615d87e..61bda282 100644 -

[PATCH 4/6] libweston: fbdev: set fb device info upon the first run. This attempts to wake up secondary framebuffer devices (/dev/fb1 and up) as usually these devices start powered off, and the FBIOPU

-vga none -device VGA,id=video0 -device secondary-vga,id=video1 \ -device secondary-vga,id=video2 --- libweston/compositor-fbdev.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/libweston/compositor-fbdev.c b/libweston/compositor-fbdev.c index b4f0685c..a9cc08be 100644 --- a/libweston/

[PATCH 2/6] libweston: fbdev: support the --seat option, (and XDG_SEAT variable)

--- compositor/main.c| 2 ++ libweston/compositor-fbdev.c | 5 - libweston/compositor-fbdev.h | 1 + 3 files changed, 7 insertions(+), 1 deletion(-) diff --git a/compositor/main.c b/compositor/main.c index 61bda282..f88608cd 100644 --- a/compositor/main.c +++ b/compositor/main.c @

[PATCH 6/6] main: don't configure /dev/fb0 by default

--- compositor/main.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/compositor/main.c b/compositor/main.c index f88608cd..cd07a6bb 100644 --- a/compositor/main.c +++ b/compositor/main.c @@ -1450,9 +1450,6 @@ load_fbdev_backend(struct weston_compositor *c, parse_options(fbdev_opti

[PATCH] libweston: Only check for a VT on seat0, as only seat0 has VTs

--- libweston/launcher-logind.c | 22 -- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/libweston/launcher-logind.c b/libweston/launcher-logind.c index a069bd4f..11627590 100644 --- a/libweston/launcher-logind.c +++ b/libweston/launcher-logind.c @@ -762,18 +762

[PATCH] libweston: Only check for a VT on seat0, as only seat0 has VTs

--- libweston/launcher-logind.c | 22 -- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/libweston/launcher-logind.c b/libweston/launcher-logind.c index a069bd4f..7cc6f963 100644 --- a/libweston/launcher-logind.c +++ b/libweston/launcher-logind.c @@ -762,18 +762

[PATCH 1/2] libweston: Support autodetection of the current XDG_SEAT

--- libweston/compositor-drm.c | 5 + libweston/compositor-fbdev.c | 5 + 2 files changed, 10 insertions(+) diff --git a/libweston/compositor-drm.c b/libweston/compositor-drm.c index 10adb463..44b2e448 100644 --- a/libweston/compositor-drm.c +++ b/libweston/compositor-drm.c @@ -3502,8 +

[PATCH 2/2] Document the new handling of XDG_SEAT

--- compositor/main.c | 2 +- man/weston-drm.man | 7 +-- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/compositor/main.c b/compositor/main.c index f8a60e97..f632fc0e 100644 --- a/compositor/main.c +++ b/compositor/main.c @@ -563,7 +563,7 @@ usage(int error_code) fpri

Re: [PATCH] libweston: Support autodetection of the current XDG_SEAT

On Wednesday, August 16, 2017 4:50:15 AM EDT Pekka Paalanen wrote: > On Tue, 15 Aug 2017 18:03:10 -0400 > nerdopolis wrote: > > > On Tuesday, August 15, 2017 3:36:48 PM EDT Armin Krezović wrote: > > > On 15.08.2017 04:02, nerdopoli

Re: [PATCH] libweston: Support autodetection of the current XDG_SEAT

On Tuesday, August 15, 2017 3:36:48 PM EDT Armin Krezović wrote: > On 15.08.2017 04:02, nerdopolis wrote: > > Hi, > > > --- > > libweston/compositor-drm.c | 5 + > > libweston/compositor-fbdev.c | 5 + > > 2 files changed, 10 insertions(+) > &

Re: Starting Weston drm-backend from non-seat0 ?

On Wednesday, August 2, 2017 11:09:44 PM EDT nerdopolis wrote: > Hi > > I found out how to get the systemd session-seat to be my desired seat (with > --setenv=XDG_SEAT=seatx of which pam_systemd.so responds to) After assigning > devices to the seat, and trying to start it I get &

Starting Weston drm-backend from non-seat0 ?

Hi I found out how to get the systemd session-seat to be my desired seat (with --setenv=XDG_SEAT=seatx of which pam_systemd.so responds to) After assigning devices to the seat, and trying to start it I get "logind: session not running on a VT" Of which is a bit confusing as as far as I understan

Re: [ANNOUNCE] Wayland Live CD release

16, 2016 12:18 AM, "nerdopolis" > wrote: > > > Hi. > > > > I have pushed out new ISO files for the Wayland Live CD project, named > > after my favorite celebrity (Rebecca Black). > > I wanted to time the release to celebrate the release of her new >

[ANNOUNCE] Wayland Live CD release

Hi. I have pushed out new ISO files for the Wayland Live CD project, named after my favorite celebrity (Rebecca Black). I wanted to time the release to celebrate the release of her new song The Great Divide, but I had some issues I previously had to resolve This might be the last set of

Re: [PATCH weston] libweston-desktop: fix stale ping when a wl_shell_surface is destroyed

Hi Is this patch for https://bugs.freedesktop.org/show_bug.cgi?id=97892 , or is it for a different issue that I am getting confused with? It doesn't seem to fix the issue with wl_shell for qtwayland and EFL (when EFL is forced to use wl_shell) It actually seems to make the issue affect all surf

[ANNOUNCE] Wayland Live CD release

Hi. I have pushed out new ISO files for the Wayland Live CD project, named after my favorite celebrity (Rebecca Black). These have Wayland an Weston master, which when built, were a few commits ahead of the 1.8 releases of Wayland and Weston. Notably: The bash waylandloginmanager no longer use

[PATCH] desktop-shell: provide an option, background-bpp , for specifing the bit depth of the wallpaper

--- clients/desktop-shell.c | 13 +++-- man/weston.ini.man| 5 + tests/internal-screenshot.ini | 1 + 3 files changed, 17 insertions(+), 2 deletions(-) diff --git a/clients/desktop-shell.c b/clients/desktop-shell.c index 777a50a..d620daf 100644 --- a/clients/deskto

Re: [PATCH] desktop-shell: support an option to use 16 bit color or not, instead of using it by default

On Friday, May 22, 2015 01:19:58 AM you wrote: > On Thu, May 21, 2015 at 11:15:54PM -0400, nerdopolis wrote: > > On Thursday, May 21, 2015 05:23:30 PM you wrote: > > > On Thu, May 21, 2015 at 04:35:16PM -0400, nerdopolis wrote: > > > > --- > &g

Re: [PATCH] desktop-shell: support an option to use 16 bit color or not, instead of using it by default

On Thursday, May 21, 2015 05:23:30 PM you wrote: > On Thu, May 21, 2015 at 04:35:16PM -0400, nerdopolis wrote: > > --- > > clients/desktop-shell.c | 10 -- > > man/weston.ini.man | 4 > > 2 files changed, 12 insertions(+), 2 deletions(-) > >

[PATCH] desktop-shell: support an option to use 16 bit color or not, instead of using it by default

--- clients/desktop-shell.c | 10 -- man/weston.ini.man | 4 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/clients/desktop-shell.c b/clients/desktop-shell.c index e2f9f80..cc4a502 100644 --- a/clients/desktop-shell.c +++ b/clients/desktop-shell.c @@ -94,6 +94,7

[PATCH] desktop-shell: support an option to use 16 bit color or not, instead of using it by default

--- clients/desktop-shell.c | 13 +++-- man/weston.ini.man | 4 2 files changed, 15 insertions(+), 2 deletions(-) diff --git a/clients/desktop-shell.c b/clients/desktop-shell.c index e2f9f80..d4ba127 100644 --- a/clients/desktop-shell.c +++ b/clients/desktop-shell.c @@ -94,6 +9

Re: [PATCH] desktop-shell: support an option to use 16 bit color or not, instead of using it by default

this with obvious additions, rather than being forced > to add even more switches. > > I am also annoyed that the keywords have dashes in them (thus requiring > the C variable that stores the value to have a different name) but that > seems to be well-established here... &g

[PATCH] desktop-shell: support an option to use 16 bit color or not, instead of using it by default

--- clients/desktop-shell.c | 13 +++-- man/weston.ini.man | 4 2 files changed, 15 insertions(+), 2 deletions(-) diff --git a/clients/desktop-shell.c b/clients/desktop-shell.c index e2f9f80..970b9f0 100644 --- a/clients/desktop-shell.c +++ b/clients/desktop-shell.c @@ -94,6 +9

[PATCH] drm-backend: for now, on the egl backend, force gl cursors to be used instead of hardware cursors

Hardware cursors have been causing some problems with some drivers, mostly i915 This will probably be changed once Atomic Mode Setting arrives, to probably only force gl cursors to always be on when Atomic Mode Setting isn't supported by the driver, or kernel version --- src/compositor-drm.c |

  1   2   >