Date: Sat, 05 Jan 2019 15:35:21 +0300 From: Greg V <greg@unrelenting.technology> To: Gunther Nikl <gnikl@justmail.de> Cc: freebsd-x11@freebsd.org, freebsd-questions@freebsd.org Subject: Re: AMDGPU RX580 OpenCL Message-ID: <1546691721.1768.0@smtp.migadu.com> In-Reply-To: <20190105122042.00004687@justmail.de> References: <CAFYkXjnVOspenga%2BM0oP-0pS=vxr4gmqs7XcrJZdSjnf1geEZA@mail.gmail.com> <20190102070113.1e9781fc9ac1c37bba8f1800@sohara.org> <CAFYkXjny-6Wihc=6=AGE3Vo6y6X2LMeD=T9LnzX1VbkXZW2YBA@mail.gmail.com> <1546646937.2475.3@smtp.migadu.com> <20190105122042.00004687@justmail.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 5, 2019 at 2:20 PM, Gunther Nikl <gnikl@justmail.de> wrote: > Greg V <greg@unrelenting.technology>: >> It's very usable, I'm running a Wayland compositor (Weston), with >> VAAPI and Vulkan and whatnot :) >=20 > Slightly OT, but can you describe what is required to get Wayland > running? What additional software is required? Can I (still) use=20 > xterm, > Opera 12, etc? Yes, you can run any X apps, Xwayland makes that work > I am interested in trying this stuff. However lacking the basics I > could not convince myself to undertake this adventure. Currently I am > on FreeBSD 11.2 (UEFI) using Xorg (1.20, patch for ports taken from > pr196678) with the modesetting driver on a Haswell system. The laptop > works with the base(!) drm without a glitch. The ports drm kmod works > as well, no idea if its preferable. I am always loading the kms module > manually... Yes, of course it's preferable, the base port is really old and=20 abandoned. Back in 2015 base was all we had, it didn't even support Haswell, I=20 bought my X240 right around when Haswell support was added=85 :D And now we don't lag behind Linux all that much, and there's AMD in=20 additon to Intel=85 So, if you want Wayland, - most importantly, you need a kernel built with the EVDEV_SUPPORT=20 option, otherwise you won't get any input devices - (btw you can use evdev+libinput in Xorg too) - EVDEV_SUPPORT has been enabled by default in CURRENT and 12-STABLE,=20 so 12.1 will be the first release to get evdev out of the box I think - set sysctl kern.evdev.rcpt_mask=3D12 to get events from individual=20 keyboards/mice instead of the multiplexer =97 important for touchpads - also it's very nice to have a kernel with=20 https://reviews.freebsd.org/rS342768 (just landed in CURRENT, will be=20 merged into 12-STABLE after a week) =97 otherwise unresponsive=20 applications can make the whole desktop unresponsive (kinda like in the=20 good old Mac OS 9.x days :D) =97 but it was surprisingly rare, I lived=20 with that bug for over a year - for now, you need access permissions on /dev/input* devices =97 I've=20 been working on fixing that, there are patches (on differential for the=20 kernel, on github for libudev-devd) but you can just chmod g+rw=20 /dev/input/* and ignore security lol - you need mesa, the UI toolkits, etc. built with wayland support =97=20 thankfully, it's on by default in ports now, so it should all be in the=20 official packages already :) - well, you need a compositor: - there's Sway https://github.com/swaywm/sway which has FreeBSD=20 support and it's already in a sort of user friendly state (for advanced=20 users :D) - there's my development fork of Weston=20 https://github.com/myfreeweb/weston + it needs to be launched with=20 https://github.com/myfreeweb/loginw =97 this is in development, not=20 really documented - KDE Plasma5 kwin_wayland =97 won't run directly on the desktop=20 right now I think, only in a window. I'll need to investigate=20 ConsoleKit2=85 =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1546691721.1768.0>