drm/radeon: allow MIP_ADDRESS=0 for MSAA textures on Evergreen
MIP_ADDRESS should point to the resolved FMASK for an MSAA texture. Setting MIP_ADDRESS to 0 means the FMASK pointer is invalid (the GPU won't read the memory then). The userspace has to set MIP_ADDRESS to 0 and *not* emit any relocation for it. Signed-off-by: Marek Olšák <maraeo@gmail.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Cc: stable@vger.kernel.org
This commit is contained in:

committed by
Alex Deucher

parent
46fc8781bf
commit
61051afd35
@@ -65,9 +65,10 @@
|
||||
* 2.21.0 - r600-r700: FMASK and CMASK
|
||||
* 2.22.0 - r600 only: RESOLVE_BOX allowed
|
||||
* 2.23.0 - allow STRMOUT_BASE_UPDATE on RS780 and RS880
|
||||
* 2.24.0 - eg only: allow MIP_ADDRESS=0 for MSAA textures
|
||||
*/
|
||||
#define KMS_DRIVER_MAJOR 2
|
||||
#define KMS_DRIVER_MINOR 23
|
||||
#define KMS_DRIVER_MINOR 24
|
||||
#define KMS_DRIVER_PATCHLEVEL 0
|
||||
int radeon_driver_load_kms(struct drm_device *dev, unsigned long flags);
|
||||
int radeon_driver_unload_kms(struct drm_device *dev);
|
||||
|
Reference in New Issue
Block a user