aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/nouveau/nv50_fifo.c
diff options
context:
space:
mode:
authorBen Skeggs <bskeggs@redhat.com>2009-12-15 22:02:47 +1000
committerBen Skeggs <bskeggs@redhat.com>2009-12-16 17:05:39 +1000
commit054b93e444550a72aef17115363cdef253b9ee7c (patch)
tree667d10b686c62d64e0b998115209c65884bcc6de /drivers/gpu/drm/nouveau/nv50_fifo.c
parent15bee69ee1532a29e13124b298027ee6ef54bac8 (diff)
downloadkernel_samsung_aries-054b93e444550a72aef17115363cdef253b9ee7c.zip
kernel_samsung_aries-054b93e444550a72aef17115363cdef253b9ee7c.tar.gz
kernel_samsung_aries-054b93e444550a72aef17115363cdef253b9ee7c.tar.bz2
drm/nv40: implement ctxprog/state generation
The context programs are *very* simple compared to the ones used by the binary driver. There's notes in nv40_grctx.c explaining most of the things we don't implement. If we discover if/why any of it is required further down the track, we'll handle it then. The PGRAPH state generated for each chipset should match what NVIDIA do almost exactly (there's a couple of exceptions). If someone has a lot of time on their hands, they could figure out the mapping of object/method to PGRAPH register and demagic the initial state a little, it's not terribly important however. At time of commit, confirmed to be working at least well enough for accelerated X (and where tested, for 3D apps) on NV40, NV43, NV44, NV46, NV49, NV4A, NV4B and NV4E. A module option has been added to force the use of external firmware blobs if it becomes required. Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Diffstat (limited to 'drivers/gpu/drm/nouveau/nv50_fifo.c')
0 files changed, 0 insertions, 0 deletions