From: Ari Hirvonen ahirvo...@nvidia.com
Add new NOUVEAU_GEM_SET_TILING ioctl to set correct tiling
mode for imported dma-bufs. This ioctl is staging for now.
Signed-off-by: Ari Hirvonen ahirvo...@nvidia.com
[acour...@nvidia.com: carry upstream, fix style]
Signed-off-by: Alexandre Courbot
Add a module option allowing to enable staging/unstable APIs. This will
allow us to experiment freely with experimental APIs for a while before
setting them in stone.
Signed-off-by: Alexandre Courbot acour...@nvidia.com
---
drm/nouveau/nouveau_drm.c | 18 ++
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 specify the
https://bugs.freedesktop.org/show_bug.cgi?id=90513
--- Comment #2 from Ilia Mirkin imir...@alum.mit.edu ---
Confirmed that I get redness coming in on that draw on my GK208, whereas it's
fine on i965.
There are a few awkward things, but nothing completely ridiculous:
1. 4096x4096 srgb dxt1/5
A 32-bit shift is a no-op, which will also make the new planemask get
or'd with ~0, thus negating the usefulness of the subsequent
planemask != ~0 check. Only do this if it's a less-than-32-bit per pixel
format, in which case it will have the desired effect of setting the
high bits.
On 19/05/15 23:28, Ilia Mirkin wrote:
A 32-bit shift is a no-op, which will also make the new planemask get
or'd with ~0, thus negating the usefulness of the subsequent
planemask != ~0 check. Only do this if it's a less-than-32-bit per pixel
format, in which case it will have the desired effect
On Tue, May 19, 2015 at 4:35 PM, Martin Peres martin.pe...@free.fr wrote:
On 19/05/15 23:28, Ilia Mirkin wrote:
A 32-bit shift is a no-op, which will also make the new planemask get
or'd with ~0, thus negating the usefulness of the subsequent
planemask != ~0 check. Only do this if it's a
