From owner-freebsd-x11@freebsd.org Mon Jul 2 03:41:44 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 ABC76102A2F7 for ; Mon, 2 Jul 2018 03:41:44 +0000 (UTC) (envelope-from dpolyg@gmail.com) Received: from mail-pl0-x242.google.com (mail-pl0-x242.google.com [IPv6:2607:f8b0:400e:c01::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2357F8E8C7 for ; Mon, 2 Jul 2018 03:41:44 +0000 (UTC) (envelope-from dpolyg@gmail.com) Received: by mail-pl0-x242.google.com with SMTP id z9-v6so7243952plo.1 for ; Sun, 01 Jul 2018 20:41:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=qYQZhc3iRRIpCUiSYH/IMLKWExx3CqhI2GHivx73czo=; b=PilpuXKej+ghOEHwK7QDvfly2dRfTceEZb1Q1onOGyfpJqeI3/5dn75XMSDpHczxoa 22/st4WXPyizfVGZx5Vw1Z06wkYxYnQDXZw0UkfsZu6a71JLu168Zbg84z6PtQhA4hql NFKPiaO7bHBVZ5evMF4Ctofi5IpWFqU07c2fseJUTdg7HwprXDmwkxJLijn2UmlokLBX Z6FrgyLuAcv6+HgYSrb5kF4ZxASAwaobaWhwD32GtSoouUvPQqAokB/IiwAqeW6C2Dgf 9pchCzVhlVEuHFRXpRVr08LP0RxZ0HFUedwhuI2eADFEa93+6akOV5RnAMDDZgYa9BKq g+YQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=qYQZhc3iRRIpCUiSYH/IMLKWExx3CqhI2GHivx73czo=; b=HjzGjlPEDEmbdfmW66E4uz76bm0e+Tf/f3GolmXviufYrEarcPIHJK66/Up8HlFcnS zxlTJrK5a5z31jbkvrgvoN8MjCIHDLn9qM19w9e0voYqeJUhpGwrZfmbFuXa1du8NNRW 0pF0g5DuNBQr/NDMZKH4yc8DTkkUGpGU/BKqMw2R11DAVCkCNxPFzpP3E/JQwmyOKNS+ tzavZNXu3NKqgo3pUNZjTvFKx61n7njrQitMEP4XzVMXzuRQBTWP5gUdG+xLATUK6AAz 9iy1Y3kaOVsJy0uTiFgj3l9JrRw2LHCVktqgaBHAJ1IuPuT45T9UA5os4EbrpQvoJdMi ko3A== X-Gm-Message-State: APt69E3UuAbt2CNvAiKhcTBX2/4nDSupTOCKqMAc4fc5I8h4zDfzt+Rh 9jFoFPoZnEf28mtLj+cLf3SW9OREfPVEIz8cm4E= X-Google-Smtp-Source: AAOMgpebQ4gK3k3/f3bXK1MC3xdxyXftHxRivHSCGtjh/oIkf8M1VDyr52krco3xfPUUHBJBOzoILi4nGrW23LJIA+g= X-Received: by 2002:a17:902:530a:: with SMTP id b10-v6mr20105043pli.316.1530502903014; Sun, 01 Jul 2018 20:41:43 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a17:90a:65c1:0:0:0:0 with HTTP; Sun, 1 Jul 2018 20:41:42 -0700 (PDT) In-Reply-To: References: <3f7629b0-1947-4bd3-f4fa-eb685dc2046b@gjunka.com> <1530481686.15209.0@hraggstad.unrelenting.technology> From: Denis Polygalov Date: Mon, 2 Jul 2018 12:41:42 +0900 Message-ID: Subject: Re: Does either Gnome or KDE support Wayland on FreeBSD? [EOM] To: Grzegorz Junka Cc: Greg V , x11-list freebsd Content-Type: text/plain; charset="UTF-8" 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 03:41:44 -0000 Hi Grzegorz, "Currently FreeBSD supports Wayland compositor" - this statement is too gen= eral. To my knowledge the situation is like follows. Currently FreeBSD support Wayland (protocol) out of the box, just type: $ pkg install wayland In order to be able to see anything on the screen (or in a window created b= y X) you need a so called "Wayland compositor". In a world of Wayland the compositor is _the_ heavy stuff with wide range of dependencies. On FreeBSD currently there is no Wayland compositor available "out of the box" i.e. from packages for example, so you have to compile one of them by yourself. Reference Wayland compositor - "Weston" is not in the ports tree yet but yo= u can find FreeBSD port for it under review here: https://reviews.freebsd.org/D10599?id=3D28017 In order to use Weston or any other Wayland compositor you need at least: 11.2-RELEASE FreeBSD drm-stable-kmod installed from ports mesa-libs compiled from ports with Wayland support Any other dependencies may differ for different Wayland compositors. The Weston for example require custom kernel with evdev enabled. kwin_wayland may require something else... Another Wayland compositor I manage to get run on a GENERIC 11.2 kernel is graphics/qt5-wayland. Hope this helps. Denis. On 7/2/18, Grzegorz Junka wrote: > > On 01/07/2018 21:48, Greg V wrote: >> >> On Sun, Jul 1, 2018 at 2:45 PM, Grzegorz Junka wrote: >>> >>> On 30/06/2018 20:37, Johannes Lundberg wrote: >>>> I don=E2=80=99t know about Gnome or KDE but GTK3 apps work with Waylan= d. It >>>> needs ports built with custom options though. >>>> >>> >>> Building ports isn't a problem, however I don't understand how >>> particular apps can work with Wayland. I thought that they would need >>> to run inside Weston or some other compositor, which in turn runs on >>> Wayland? Is the X server in that configuration running as a Wayland >>> client with with the GTK3 apps running outside of the X server (i.e. >>> are managed by the compositor directly)? >> >> Yes, you can run them inside e.g. Weston or Sway. >> >> Compositors don't run "on" Wayland, Wayland is a protocol. >> The compositor is the display server, it implements the server side of >> Wayland. >> (Compositors can run in windowed mode under X or under another Wayland >> compositor, for development/debugging purposes.) >> >> For backwards compatibility, the X server is indeed running as a >> Wayland client, this is called Xwayland, this is optional. >> >> About KDE: I think KDE's kwin_wayland is available now too, but I'm >> not sure if it would run directly as the main display server (not >> windowed mode) right now on FreeBSD without additional patches >> (because of vt/session management stuff -- though maybe ConsoleKit2 >> might work?). >> > > Thanks Greg for the clarification. Let me rephrase it to see if I got it > right. Currently FreeBSD supports Wayland compositor in windowed mode > under X and this is how the GTK3 applications are running. It might > support Wayland as the main display server (not windowed), i.e. using > KDE's kwin_wayland, but the status is currently not known. > > If that's correct, then assuming that I compiled my ports with support > for Wayland enabled, and assuming further that I have 11.2 installed, > what else would I need to do to be able to test this? > > I guess I need to compile and install drm-next-kmod or drm-stable-kmod. > Will either work on generic 11.2 or I need a custom kernel? I guess > again that the later should work with the generic kernel but it will > only supports Polaris Radeon cards. If I recall correctly Hans Petter > Selasky was working on merging support for Radeon Vega (Linux kernel > 4.15) into 11-STABLE (future 11.3). If that is correct and the merge was > completed then I could compile a custom 11-STABLE kernel and together > with the 11.2 userland be able to test windowed Wayland on Vega? > > Please correct if my guesses are wrong. Sorry for all those questions > but without the updated wiki it gets a bit confusing :) > GrzegorzJ > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" >