search for: libdrm_amdgpu

...) libexpat.so.1 => /lib64/libexpat.so.1 (0x00007f8a68255000) libdrm_intel.so.1 => /lib64/libdrm_intel.so.1 (0x00007f8a68033000) libdrm_nouveau.so.2 => /lib64/libdrm_nouveau.so.2 (0x00007f8a67e2b000) libdrm_radeon.so.1 => /lib64/libdrm_radeon.so.1 (0x00007f8a67c1f000) libdrm_amdgpu.so.1 => /lib64/libdrm_amdgpu.so.1 (0x00007f8a67a16000) libdrm.so.2 => /lib64/libdrm.so.2 (0x00007f8a67807000) libelf.so.1 => /lib64/libelf.so.1 (0x00007f8a675ef000) libLLVMAMDGPUCodeGen.so.3.7 => /lib64/libLLVMAMDGPUCodeGen.so.3.7 (0x00007f8a672e2000) libLLVMAMDGPUAsmPar...

...rted by the amdgpu kernel driver. This release supports xserver versions 1.10-1.19. Highlights: * Allow TearFree to be toggled at runtime via an RandR output property "TearFree". The xorg.conf option "TearFree" now controls the default value of the output properties. * Use libdrm_amdgpu functionality to determine the GPU marketing name, remove corresponding tables from this driver. * Use DRM render nodes for DRI3 clients when available. Plus many other improvements and fixes. Thanks to everybody who contributed to this release in any way! Emil Velikov (1): autogen.sh: u...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Libdrm 2.4.63 has been released. It contains the new libdrm_amdgpu library. Alan Coopersmith (1): include <sys/types.h> & <sys/mkdev.h> directly for major() and minor() Alex Deucher (10): drm: consolidate common list implementations (v2) drm: add util_math.h drm: add libdrm_amdgpu (v7) drm: add tests/amdgpu (v3)...

...apped regions where access is illegal. > > All this is plus some hw specific caching flags. > > When Vulkan allocates a sparse VKBuffer what should happen is the following: > > 1. The Vulkan driver somehow figures out a VA region A..B for the > buffer. This can be in userspace (libdrm_amdgpu) or kernel (drm_mm), but > essentially is currently driver specific. There are NO plans to have drm_mm do VA region management, VA region management will be in userspace in Mesa. Can we just not bring that up again? This is for GPU VA tracking not management if that makes it easier we could ren...

...CRC Mika Kuoppala (1): tools/intel_reg: Add reading and writing registers through engine Petri Latvala (7): meson: Refactor get_option() calls for directories meson: Use absolute path for IGT_DATADIR meson: Don't build docs when cross-compiling configure.ac: Bump libdrm_amdgpu version requirement Update MAINTAINERS configure.ac: Properly bump libdrm_amdgpu version requirement Update NEWS, bump version to 1.22. Rhys Kidd (5): doc: Fix typos in CONTRIBUTING lib/igt.cocci: Fix typo doc: Correct sentence in README doc: Update CONTRI...

...is is used for things like unmapped regions where access is illegal. All this is plus some hw specific caching flags. When Vulkan allocates a sparse VKBuffer what should happen is the following: 1. The Vulkan driver somehow figures out a VA region A..B for the buffer. This can be in userspace (libdrm_amdgpu) or kernel (drm_mm), but essentially is currently driver specific. 2. The kernel gets a request to map the VA range A..B as sparse, meaning that it updates the page tables from A..B with the sparse setting. 3. User space asks kernel to map a couple of memory backings at location A+1, A+10, A+1...

...is is plus some hw specific caching flags. >>> >>> When Vulkan allocates a sparse VKBuffer what should happen is the >>> following: >>> >>> 1. The Vulkan driver somehow figures out a VA region A..B for the >>> buffer. This can be in userspace (libdrm_amdgpu) or kernel (drm_mm), >>> but essentially is currently driver specific. >> >> Right, for Nouveau we have this in userspace as well. >> >>> >>> 2. The kernel gets a request to map the VA range A..B as sparse, >>> meaning that it updates the page...

...ons where access is illegal. > > All this is plus some hw specific caching flags. > > When Vulkan allocates a sparse VKBuffer what should happen is the > following: > > 1. The Vulkan driver somehow figures out a VA region A..B for the > buffer. This can be in userspace (libdrm_amdgpu) or kernel (drm_mm), but > essentially is currently driver specific. Right, for Nouveau we have this in userspace as well. > > 2. The kernel gets a request to map the VA range A..B as sparse, meaning > that it updates the page tables from A..B with the sparse setting. > > 3....

This is the initial release of the xf86-video-amdgpu driver. It was forked from the xf86-video-ati radeon driver and modified to support the amdgpu kernel driver via libdrm_amdgpu, and by extension the latest AMD GPU families Tonga, Carrizo, Iceland, Fiji and Stoney. Some functionality was removed because it's not relevant for the GPUs supported by the amdgpu kernel driver, but other than that the two drivers are more or less on par with respect to functionality and bug...