From owner-freebsd-x11@freebsd.org Mon Jul 2 16:10:56 2018 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 959FA102E074 for ; Mon, 2 Jul 2018 16:10:56 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 176028F0CC for ; Mon, 2 Jul 2018 16:10:55 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=PU/jnqgjFfwJ2Ks80IIrbhr8zz3g271aFNVCdqTm1z4=; b=OK/U5r0h6oAViBVbl3XG8zdieQmVM2UEWHfhV5rvDpFJAqffiOYW5Vj3wx5dllQbiUtrEvS2n7KIUUe7vzSMX29Nll2aaT+i9xhXem5+cH6JIQ2D1++ntU+qeo2oa4DgUYGNSzIWctWWDc4uAUnRdzZWgzA9GMXv8hmwbLl5V+k= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 198b54a2 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 2 Jul 2018 16:10:51 +0000 (UTC) Date: Mon, 02 Jul 2018 19:10:41 +0300 From: Greg V Subject: Re: Does either Gnome or KDE support Wayland on FreeBSD? [EOM] To: Grzegorz Junka Cc: x11-list freebsd Message-Id: <1530547841.1450.0@hraggstad.unrelenting.technology> In-Reply-To: References: <3f7629b0-1947-4bd3-f4fa-eb685dc2046b@gjunka.com> <1530481686.15209.0@hraggstad.unrelenting.technology> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-13; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 16:10:56 -0000 On Mon, Jul 2, 2018 at 1:44 AM, Grzegorz Junka wrote: >=20 > On 01/07/2018 21:48, Greg V wrote: >>=20 >> On Sun, Jul 1, 2018 at 2:45 PM, Grzegorz Junka =20 >> wrote: >>>=20 >>> On 30/06/2018 20:37, Johannes Lundberg wrote: >>>> I don=FFt know about Gnome or KDE but GTK3 apps work with Wayland.=20 >>>> It =7F=7F=7F=7Fneeds ports built with custom options though. >>>>=20 >>>=20 >>> Building ports isn't a problem, however I don't understand how=20 >>> =7F=7Fparticular apps can work with Wayland. I thought that they would=20 >>> need =7F=7Fto run inside Weston or some other compositor, which in turn= =20 >>> runs on =7F=7FWayland? Is the X server in that configuration running as= =20 >>> a Wayland =7F=7Fclient with with the GTK3 apps running outside of the X= =20 >>> server (i.e. =7F=7Fare managed by the compositor directly)? >>=20 >> Yes, you can run them inside e.g. Weston or Sway. >>=20 >> Compositors don't run "on" Wayland, Wayland is a protocol. >> The compositor is the display server, it implements the server side=20 >> of =7FWayland. >> (Compositors can run in windowed mode under X or under another=20 >> Wayland =7Fcompositor, for development/debugging purposes.) >>=20 >> For backwards compatibility, the X server is indeed running as a=20 >> =7FWayland client, this is called Xwayland, this is optional. >>=20 >> About KDE: I think KDE's kwin_wayland is available now too, but I'm=20 >> =7Fnot sure if it would run directly as the main display server (not=20 >> =7Fwindowed mode) right now on FreeBSD without additional patches=20 >> =7F(because of vt/session management stuff -- though maybe ConsoleKit2=20 >> =7Fmight work?). >>=20 >=20 > Thanks Greg for the clarification. Let me rephrase it to see if I got=20 > it right. Currently FreeBSD supports Wayland compositor in windowed=20 > mode under X and this is how the GTK3 applications are running. It=20 > might support Wayland as the main display server (not windowed), i.e.=20 > using KDE's kwin_wayland, but the status is currently not known. I'm currently running Weston as the main display server, so that is=20 known :) Well, my fork of weston actually: https://github.com/myfreeweb/weston Sway 0.x also worked, 1.x (master) should work too, unless they broke=20 something. The only unknown is KDE KWin ("might just work with ConsoleKit2?"). I guess I should look into that, but I'm busy with other stuff.. GNOME is definitely not supported ("needs patching to support=20 ConsoleKit2 or some other alternative to systemd-logind"). That's actually the main porting issue in general, many compositors use=20 logind, some (like gnome) *only* use logind. > If that's correct, then assuming that I compiled my ports with=20 > support for Wayland enabled, and assuming further that I have 11.2=20 > installed, what else would I need to do to be able to test this? >=20 > I guess I need to compile and install drm-next-kmod or=20 > drm-stable-kmod. Will either work on generic 11.2 or I need a custom=20 > kernel? I guess again that the later should work with the generic=20 > kernel but it will only supports Polaris Radeon cards. If I recall=20 > correctly Hans Petter Selasky was working on merging support for=20 > Radeon Vega (Linux kernel 4.15) into 11-STABLE (future 11.3). If that=20 > is correct and the merge was completed then I could compile a custom=20 > 11-STABLE kernel and together with the 11.2 userland be able to test=20 > windowed Wayland on Vega? For windowed mode, you don't need anything special. But for *anything on Vega*, you do need drm-next-kmod. LinuxKPI updates required for drm-next-kmod 4.15 have indeed been=20 merged into 11-STABLE:=20 https://svnweb.freebsd.org/base?view=3Drevision&revision=3D335436 Vega support is still not as stable as <=3DPolaris, btw: https://github.com/FreeBSDDesktop/kms-drm/issues/76 https://github.com/FreeBSDDesktop/kms-drm/issues/71 > Please correct if my guesses are wrong. Sorry for all those questions=20 > but without the updated wiki it gets a bit confusing :) > GrzegorzJ =