RE: Limiting Xwayland to only one screen
Hi Pekka, Yes I am aware of the rootless mode as well, but seeing the black screen is only one of the issues. I would also like the apps to only run on a single screen. Some apps are written such that they find out how big of a buffer would fit the entire screen and then create an image which spans it (in my case both screens). I guess I can use xdotool to resize the app but that happens after the surface has been created and I would rather have the app only create one screen buffer to begin with. So is there an option that doesn't require modifying each app? -Satyeshwar -Original Message- From: Pekka Paalanen [mailto:ppaala...@gmail.com] Sent: Wednesday, February 6, 2019 12:16 AM To: Singh, Satyeshwar Cc: wayland-devel@lists.freedesktop.org Subject: Re: Limiting Xwayland to only one screen On Tue, 5 Feb 2019 19:51:41 + "Singh, Satyeshwar" wrote: > Hi, > I have a 2 screen configuration running Weston. When I run XWayland on > top, it initially shows a black screen on both the screens. I am > wondering if there is a way to limit XWayland to only using one > screen? Is there a config file or command line option that allows me > to do so? Hi, getting a black screen sounds like you are starting Xwayland manually in rootful mode, where all X11 apps will show up inside the one Xwayland window. Usually people use the Xwayland rootless mode instead, where Xwayland is started automatically by the compositor, and the X11 windows integrate seamlessly with other native Wayland windows. There is no one window for all of Xwayland. Do you intentionally use the rootful mode, or were you just not aware of the rootless mode? For more information on rootful vs. rootless, see https://wayland.freedesktop.org/docs/html/ch05.html Thanks, pq ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Limiting Xwayland to only one screen
On Tue, 2019-02-05 at 19:51 +, Singh, Satyeshwar wrote: > Hi, > I have a 2 screen configuration running Weston. When I run XWayland > on top, it initially shows a black screen on both the screens. I am > wondering if there is a way to limit XWayland to only using one > screen? Is there a config file or command line option that allows me > to do so? There is not an Xwayland option for this yet. Wouldn't be hard to add though, patches would be gratefully accepted. - ajax ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: Limiting Xwayland to only one screen
On Tue, 5 Feb 2019 19:51:41 + "Singh, Satyeshwar" wrote: > Hi, > I have a 2 screen configuration running Weston. When I run XWayland > on top, it initially shows a black screen on both the screens. I am > wondering if there is a way to limit XWayland to only using one > screen? Is there a config file or command line option that allows me > to do so? Hi, getting a black screen sounds like you are starting Xwayland manually in rootful mode, where all X11 apps will show up inside the one Xwayland window. Usually people use the Xwayland rootless mode instead, where Xwayland is started automatically by the compositor, and the X11 windows integrate seamlessly with other native Wayland windows. There is no one window for all of Xwayland. Do you intentionally use the rootful mode, or were you just not aware of the rootless mode? For more information on rootful vs. rootless, see https://wayland.freedesktop.org/docs/html/ch05.html Thanks, pq pgpnrjQ1SCILx.pgp Description: OpenPGP digital signature ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: [RFC 0/2] Add fp16 formats
On Tue, 5 Feb 2019 21:57:40 + "Strasser, Kevin" wrote: > Pekka Paalanen wrote: > > On Mon, 4 Feb 2019 22:10:00 + "Strasser, Kevin" > > wrote: > > > That is what I was trying to achieve, offering applications fp16 scan > > > out buffers. I'm not aware of any explicit requirement for adding the > > > wl_shm format outside of Mesa's Walyand egl driver, which includes > > > WL_SHM_FORMAT* for each supported visual (I think just for the swrast > > > path). > > > > That should really be only the software rendering paths and they use wl_shm > > specifically. > > > > The hardware rendering paths should use DRM formats (drm_fourcc), everything > > is kind of standardising around those these days. > > Ok, I *think* we are on the same page. Once the drm formats have landed in the > kernel we will add the equivalent to wl_shm (probably my first patch unless we > decide on some other fourcc definition). This will make fp16 visuals available > for hardware and software (swrast) paths in the egl driver. That should cover > the requirements for use in Weston's gl renderer. Hi, let me be more specific just in case. :-) The wl_shm format patch is only necessary if you want to have fp16 buffer format with software rendering. This is because the software rendering glue uses wl_shm Wayland buffers to send the content to a Wayland compositor. If you are happy to limit fp16 to hardware rendering on Wayland, you do not need to think of wl_shm at all. Hardware rendering uses zwp_linux_dmabuf (or the old wl_drm) Wayland buffers, which simply say "use the kernel DRM format definitions". Defining the formats is only for a common vocabulary. The formats a Wayland compositor will actually support are advertised explicitly at runtime, which I believe should affect things like what EGLConfigs an app sees available. Thanks, pq pgpYXEgTXAXfZ.pgp Description: OpenPGP digital signature ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
