Created attachment 41021 [details] [review]
[PATCH] Enable microtiling for R200 if DRM >= v2.x
Mesa only checks the minor DRM version number when deciding whether to enable texture microtiling. This would imply that microtiling hasn't been enabled since the 2.6.30 kernel.
The HyperZ check for R200 does examine that the major DRM version number, but completely disables HyperZ for DRM v2.x. I don't know if this is intentional or not.
There is a similar absence of DRM major version number checking in the radeonCreateScreen() funtion in radeon_screen.c
This is correct, v2.x is a whole new interface that needs support to be added for these features.
Having v2 doesn't imply all the v1.x features since the whole kernel interface changed.
(In reply to comment #2)
> Having v2 doesn't imply all the v1.x features since the whole kernel interface
Then the current code is NOT correct, because it should examine the DRM major version number and insist that it equals 1 instead.
radeonCreatescreen is only called in DRI1 system,
radeonCreateScreen2 is called on DRI2 systems.
You can only have a version 1.x driver with a DRI1 system
and a version 2.x driver with a DRI2 system.
Short of hacking things to force some wierd codepaths you can't cross the streams.
Created attachment 41039 [details] [review]
[PATCH] Don't even consider enabling microtiling unless DRM major version is 1.
If DRM v2.x doesn't support microtiling on R200 yet then the DRM version check in Mesa is no longer adequate.
(In reply to comment #5)
> Created an attachment (id=41039) [details]
> [PATCH] Don't even consider enabling microtiling unless DRM major version is 1.
> If DRM v2.x doesn't support microtiling on R200 yet then the DRM version check
> in Mesa is no longer adequate.
Did you read/understand Dave's previous comment?