Age | Commit message (Collapse) | Author |
|
restoring NV10_PGRAPH_CTX_SWITCH1 now works
|
|
"5a072f32 (Stephane Marchesin 2007-02-03 04:57:06 +0100" broke nv10 ctx switch by setting wrong PGRAPH_CTX_CONTROL reg
|
|
|
|
|
|
|
|
|
|
This is required to use TTM to allocate the ring buffer.
|
|
This was causing an oops in my miniglx code to try and use a TTM-only setup.
|
|
|
|
The PGRAPH init for the various cards will need cleaning up at some point,
a lot of the values written there are per-context state left over from the
all the hardcoding done in the ddx.
It's possible some cards get broken by this commit, let me know.
Tested on: NV5, NV18, NV28, NV35, NV40, NV4E
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
enough information is known about them to be sure as to what the values mean.
|
|
|
|
Note that just like the values written to R300_RB3D_DSTCACHE_CTLSTAT these
values are really unknown; ideally more reverse engineering should be done to
determine what these values mean and when they should be set.
|
|
|
|
|
|
|
|
R300_RB3D_DSTCACHE_02 or R300_RB3D_DSTCACHE_0A, rather than hexadecimal values.
|
|
|
|
|
|
|
|
|
|
|