From owner-freebsd-questions@freebsd.org Sat Jan 5 12:35:24 2019 Return-Path: Delivered-To: freebsd-questions@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 46ECA1499F96 for ; Sat, 5 Jan 2019 12:35:24 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out.migadu.com (out.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.migadu.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1588080BDE for ; Sat, 5 Jan 2019 12:35:22 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: (Migadu outbound); Sat, 05 Jan 2019 12:35:21 +0000 Received: from [192.168.1.141] ([62.122.208.146]) by out.migadu.com (Haraka/2.8.16) with ESMTPSA id 33064106-DFE6-402F-B5EB-D8789F3D6C8F.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 verify=FAIL); Sat, 05 Jan 2019 12:35:20 +0000 Date: Sat, 05 Jan 2019 15:35:21 +0300 From: Greg V Subject: Re: AMDGPU RX580 OpenCL To: Gunther Nikl Cc: freebsd-x11@freebsd.org, freebsd-questions@freebsd.org Message-Id: <1546691721.1768.0@smtp.migadu.com> In-Reply-To: <20190105122042.00004687@justmail.de> References: <20190102070113.1e9781fc9ac1c37bba8f1800@sohara.org> <1546646937.2475.3@smtp.migadu.com> <20190105122042.00004687@justmail.de> X-Mailer: geary/0.12.4 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; bh=JC5FyCVmu7Imav6QOB2Xp9CYZam4AZlwi+fG1JGuBGo=; c=relaxed/simple; d=unrelenting.technology; h=from:subject:date:to; s=default; b=GhqXxJt9oSlAAmB6eh5pvUvLfRv7hp1cllTvAr32eqWh9JAatjAhvcD4O2bh88St89KhA/e+VjC10H/7Ya3pvvVlJxiuyzxziUWnBy8qwKWSCB7/MM03fBuyCdRwJklqjZ2JPQ4S1BTwtjGUfgGj5oU4SZ7Wp8VfR8Xs0v7FIrU= X-Rspamd-Queue-Id: 1588080BDE X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=GhqXxJt9; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 91.121.223.63 as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-6.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:91.121.223.63]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[unrelenting.technology:+]; MX_GOOD(-0.01)[cached: aspmx1.migadu.com]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; NEURAL_HAM_SHORT(-0.94)[-0.943,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-2.74)[ip: (-9.88), ipnet: 91.121.0.0/16(-4.26), asn: 16276(0.45), country: FR(-0.02)]; ASN(0.00)[asn:16276, ipnet:91.121.0.0/16, country:FR]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jan 2019 12:35:24 -0000 On Sat, Jan 5, 2019 at 2:20 PM, Gunther Nikl wrote: > Greg V : >> 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 =