Ben Skeggs 054b93e444 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>
2009-12-16 17:05:39 +10:00
..
2009-11-19 18:18:17 -05:00
2009-12-01 16:32:20 -08:00
2009-11-04 14:04:06 +01:00
2009-12-01 16:32:19 -08:00
2009-09-24 07:21:05 -07:00
2009-12-01 11:24:19 +01:00
2009-11-26 09:22:33 +01:00
2009-11-16 16:13:35 +00:00
2009-10-15 09:58:27 -06:00
2009-11-12 07:26:01 -08:00
2009-10-04 22:53:41 +02:00
2009-10-04 15:05:10 -07:00
2009-09-23 10:07:49 -07:00