On Mon, Nov 20, 2017 at 6:08 PM, Jason Ekstrand <ja...@jlekstrand.net> wrote: > On Sun, Nov 19, 2017 at 5:07 AM, Grazvydas Ignotas <nota...@gmail.com> > wrote: >> >> On Sun, Nov 19, 2017 at 1:51 AM, Jason Ekstrand <ja...@jlekstrand.net> >> wrote: >> > >> > I force-pushed the branch again with an added commit: "radv: Move wsi >> > initialization later in physical_device_init" that fixes the memory type >> > issue with radv. I've tested both radv + radeon and anv + radeon on my >> > HSW >> > + Rx550 and they both work now. I'm having a bit of trouble actually >> > getting my system to start up on the Intel card so I'll have to leave >> > testing radv on Intel for another day. >> >> Radv is working now on both displays, however "display on amd + anv" >> case still acts the same (black window on most, but not all >> SaschaWillems demos). I'm using xf86-video-amdgpu 1.4.0, 4.14 kernel >> and xorg-server 1.18.4, if that makes a difference. > > > I'm completely unable to reproduce. Here's my setup: > > - Fedora 27 > - X.org 1.19.5 > - xf86-video-amdgpu 1.3.0 > - Linux 4.13.12 > - Intel Haswell > - AMD RX550 > > I've tried with amdgpu, modesetting, and XWayland all running on the AMD > card and anv works on all three. I'm a little weirded out by the fact that > my X server is newer but my xf86-video-amdgpu is older.
Well I compiled my own xf86-video-amdgpu. Not sure why. > Two things I'd like you to try if you can: > > 1) Use modesetting. It may be a bug in your version of amdgpu. Same results (black window), plus all the tearing all over I usually get with it. Also tried the distro kernel (4.10). > 2) Try the attached patch with radv + display on AMD. It will make radv > use the prime path regardless of the fact that it's displaying on the same > GPU. Still works fine, albeit a bit slower (as expected I guess). Maybe something specific to SKL? GraÅžvydas _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev