On 03/10/2016 01:23 AM, Ilia Mirkin wrote:
On Wed, Mar 9, 2016 at 6:23 PM, Samuel Pitoiset
wrote:
+ if (screen->base.class_3d <= NVF0_3D_CLASS &&
+ screen->base.class_3d != NVEA_3D_CLASS) {
Why? NVEA should be the same as NVF0 I think... and actually
NVEA_3D_CLASS is 0xa
On Wed, Mar 9, 2016 at 6:23 PM, Samuel Pitoiset
wrote:
> + if (screen->base.class_3d <= NVF0_3D_CLASS &&
> + screen->base.class_3d != NVEA_3D_CLASS) {
Why? NVEA should be the same as NVF0 I think... and actually
NVEA_3D_CLASS is 0xa297, while the NVF0 one is a197...
-ilia
_
Because compute support is not enabled by default for these chipsets,
NVF0_COMPUTE=1 needs to be used, along with GALLIUM_HUD to enable
performance counters.
Signed-off-by: Samuel Pitoiset
---
.../drivers/nouveau/nvc0/nvc0_query_hw_sm.c| 216 +++--
.../drivers/nouveau/nvc
