summaryrefslogtreecommitdiff
path: root/src/gallium/drivers/nv30/nv30_vertprog.c
AgeCommit message (Collapse)Author
2010-03-15nv30, nv40: non-trivially unify nv[34]0_vertprog.cLuca Barbieri
vertprog.c is similar but has substantial differences: 1. nv40 supports clip planes 2. nv40 uses a more advanced register allocator 3. Some register setup is different 4. Constants with the same name have different values This patch unifies the two files. nv30 gains clip plane support and the nv40 register allocator. A new NVFX_VP(x) macro is introduced that at runtime resolved to either the nv30 or the nv40 constant value. nv30 clip planes are not tested and might not work
2010-03-15nv30, nv40: non-trivially partially unify nv[34]0_shader.hLuca Barbieri
shader.h is similar, except for the following differences: 1. The instruction sets are not exactly the same, but mostly similar 2. Vertex program fields are in different bit positions This patch unifies all parts of nv[34]0_shader.h except the vertex program fields. Vertex opcodes are also changed so that the constant names includes SCA if it is a scalar opcode and VEC if it is a vector opcode.
2010-03-15nv30, nv40: unify all structures and headers, except shadersLuca Barbieri
This patch unifies nv[34]0_screen.h, nv[34]0_context.h and nv[34]0_state.h The unified files are put in a new "nvfx" directory. nv30_context.h and nv40_context.h still exist to hold the function prototypes and include nvfx_context.h nv[34]0_screen.h and nv[34]0_state.h are deleted, replaced by the unified versions. nv40 includes some extra fields for swtnl and user clip planes support. These fields will be unused on nv30 until that functionality gets added to it too (by unification with nv40).
2010-03-15nouveau: s/rankine/eng3d/g; s/curie/eng3d/gLuca Barbieri
Result of running: perl -i -p -e 's/rankine/eng3d/g; s/curie/eng3d/g;' nv[34]0/*.[ch] This will allow to more easily unify nv30 and nv40.
2010-02-02gallium: pipe/p_inlines.h -> util/u_inlines.hJosé Fonseca
2010-01-05nouveau: rewrite nouveau_stateobj to use BEGIN_RING properlyMaarten Maathuis
- The previous solution was hacky and didn't do subchannel autobinding. - The beheaviour should match what libdrm_nouveau does closely. - The solution remains statically sized, but when debugging is on it will check for abuse. Signed-off-by: Maarten Maathuis <madman2003@gmail.com>
2010-01-05nouveau: kill nouveau_push.h and use libdrm versions of BEGIN_RINGs, etcMarcin Slusarz
2009-12-19gallium: fix up drivers for edgeflag changesRoland Scheidegger
several drivers which chose to ignore edgeflags might require some more work, while edgeflags never worked there they might now crash.
2009-11-24tgsi: rename fields of tgsi_full_src_register to reduce verbosityKeith Whitwell
SrcRegister -> Register SrcRegisterInd -> Indirect SrcRegisterDim -> Dimension SrcRegisterDimInd -> DimIndirect
2009-11-24tgsi: rename fields of tgsi_full_dst_register to reduce verbosityKeith Whitwell
DstRegister -> Register DstRegisterInd -> Indirect
2009-11-24tgsi: rename fields of tgsi_full_declaration to reduce verbosityKeith Whitwell
DeclarationRange -> Range
2009-11-24tgsi: rename fields of tgsi_full_instruction to avoid excessive verbosityKeith Whitwell
InstructionPredicate -> Predicate InstructionLabel -> Label InstructionTexture -> Texture FullSrcRegisters -> Src FullDstRegisters -> Dst
2009-11-24tgsi: reduce repetition of structure name in its membersKeith Whitwell
Rename Semantic.SemanticName to Semantic.Name. Similar for SemanticIndex, and the members of the tgsi_version struct.
2009-11-24gallium: try and update r300 and nv drivers for tgsi changesKeith Whitwell
It would be nice if these drivers built under the linux-debug header so that these types of interface changes can be minimally propogated into those drivers by people without the hardware. They don't have to generate a working driver -- though a command-dumping winsys would be an excellent for regression checking.
2009-07-22gallium: simplify tgsi_full_immediate structKeith Whitwell
Remove the need to have a pointer in this struct by just including the immediate data inline. Having a pointer in the struct introduces complications like needing to alloc/free the data pointed to, uncertainty about who owns the data, etc. There doesn't seem to be a need for it, and it is unlikely to make much difference plus or minus to performance. Added some asserts as we now will trip up on immediates with more than four elements. There were actually already quite a few such asserts, but the >4 case could be used in the future to specify indexable immediate ranges, such as lookup tables.
2009-06-05nouveau: remove unneeded code from ws, use pipe_buffer_ instead of ws->Ben Skeggs
2009-06-05nouveau: call notifier/grobj etc funcs directlyBen Skeggs
libdrm_nouveau is linked with the winsys, there's no good reason to do all this through yet another layer.
2009-03-07nouveau: make stateobjs start off with refcount of 1Ben Skeggs
2009-02-10nv30: Fix build -- rename Size to NrTokens.Michal Krol
2008-08-18nv30: add some opcodes.Stephane Marchesin
2008-08-07nouveau: fix buildBen Skeggs
2008-07-12nv30: does not have vp_attrib/resultPatrice Mandin
2008-07-12nv30: Change comment about slowdownPatrice Mandin
2008-07-12nv30: Emit vertex program using state objectsPatrice Mandin
2008-07-11nv30: Move constant buffers out of vert/frag prog structuresPatrice Mandin
2008-06-23nouveau: update for interface changes + hack around gallium x86_64 bustageBen Skeggs
2008-04-11nv30: Move some structures and functions from context to screenPatrice Mandin
2008-03-30nv30: use FREE macroPatrice Mandin
2008-03-13nouveau: match interface changesBen Skeggs
2008-03-12nv30: debug dumps vp constantsPatrice Mandin
2008-03-10nv30: put the card into vtxprog mode + small cleanups/fixesBen Skeggs
2008-03-06nv30: a couple of vtxprog fixesBen Skeggs
2008-02-16nouveau: match gallium code reorginisation.Ben Skeggs
That was... fun..