search for: nouveau_staging_til

...75,10 @@ MODULE_PARM_DESC(runpm, "disable (0), force enable (1), optimus only default (-1 > int nouveau_runtime_pm = -1; > module_param_named(runpm, nouveau_runtime_pm, int, 0400); > > +MODULE_PARM_DESC(staging_tiling, "enable staging GEM_SET_TILING ioctl"); > +int nouveau_staging_tiling = 0; > +module_param_named(staging_tiling, nouveau_staging_tiling, int, 0600); > + > static struct drm_driver driver_stub; > static struct drm_driver driver_pci; > static struct drm_driver driver_platform; > @@ -897,6 +901,7 @@ nouveau_ioctls[] = { > DRM_IOCTL_DEF_D...

Second version of this patchset addressing Ben's comments and fixing a few extra things. This patchset proposes to introduce a "staging" module option to dynamically enable features (mostly ioctls) that are merged but may be refined before they are declared "stable". The second patch illustrates the use of this staging option with the SET_TILING ioctl, which can be used to

...75,10 @@ MODULE_PARM_DESC(runpm, "disable (0), force enable (1), optimus only default (-1 > int nouveau_runtime_pm = -1; > module_param_named(runpm, nouveau_runtime_pm, int, 0400); > > +MODULE_PARM_DESC(staging_tiling, "enable staging GEM_SET_TILING ioctl"); > +int nouveau_staging_tiling = 0; > +module_param_named(staging_tiling, nouveau_staging_tiling, int, 0600); Please use _unsafe here to make sure that setting this option taints the kernel and gives at least a bit of a deterrent. But in the end the policy is still that you can't regress anything if people complain, w...