Androïd/x86 port of Mesa drivers https://git.hiegel.fr/cgit/android-x86-mesa.git/atom?h=r300 2010-03-15T04:03:04Z 2010-03-15T04:03:04Z Luca Barbieri luca@luca-barbieri.com 2010-02-21T14:13:12Z urn:sha1:f9d09a2e7859a2cf025d71b7c3cb189edb6688c4 This is the last nvfx unification patch. nv[34]0_fragtex.c are moved to the common directory nv[34]0_shader.h are renamed to nv[34]0_vertprog.h and moved to the common directory The separate nv30 and nv40 directories are removed from the build system 2010-03-15T04:03:03Z Luca Barbieri luca@luca-barbieri.com 2010-02-24T14:08:48Z urn:sha1:7d210fa05f286eb19398ac2f8c8f631f6f83c859 Many things, like texture wrap modes and min/mag filters are common. Some others, like annisotropy and lod settings, are not. 2010-03-15T04:03:03Z Luca Barbieri luca@luca-barbieri.com 2010-02-21T13:40:32Z urn:sha1:da5103c3b382ca08368a19a195a24278596db4cb They are now almost identical, except for nv30 vs nv40 fragtex initialization. 2010-03-15T04:03:03Z Luca Barbieri luca@luca-barbieri.com 2010-02-21T13:31:27Z urn:sha1:10f464fc1073e8f3b53dbcf2209a2204f4924094 The files have the same structure but are substantially different. They are unified with appropriate conditionals. 2010-03-15T04:03:03Z Luca Barbieri luca@luca-barbieri.com 2010-02-21T12:33:48Z urn:sha1:840c36f5e6d940343a3154af7e76fec341ca46e6 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-15T04:03:03Z Luca Barbieri luca@luca-barbieri.com 2010-02-21T10:12:08Z urn:sha1:6e1d0fc5eba8cda4f4c8f3188f53fec6d2d2e9c3 The files are identical, except for swtnl support which is commented out on nv30 and restart being initialized on nv30 to avoid a compiler warning. 2010-03-15T04:03:03Z Luca Barbieri luca@luca-barbieri.com 2010-02-21T10:17:55Z urn:sha1:f9eafeca297497a94c438ea28ed59f3a45ed2566 nv30_draw.c is a stub. This patch makes both nv30 and nv40 use the nv40 swtnl path. Note that this doesn't actually work on nv30 because the vertex program is encoded in the nv40-only layout. However, swtnl was unimplemented before on nv30, so this is not a regression. Furthermore, a patch to fix this is available near the end of the patchset. 2010-03-15T04:03:02Z Luca Barbieri luca@luca-barbieri.com 2010-02-21T09:55:41Z urn:sha1:bcb37411fc9159a5c1af50b7defbf1f526b50793 The files are mostly the same except: 1. On NV40, some TGSI instructions are emulated with several hardware ones 2. Some instructions such as DDX/DDY, and STR were missing from nv30 3. NV40 has more sophisticated register management nv30 now supports all instructions and uses the nv40 register management. 2010-03-15T04:03:02Z Luca Barbieri luca@luca-barbieri.com 2010-02-20T23:59:30Z urn:sha1:cd0d03adab65a9586e0c5d60e9ee487677914f3b The files are significantly different due to: 1. nv30 support 2 render targets, nv40 4 2. z-buffer pitch is set differently 3. nv30 has a limitation of colour_bits >= zeta_bits. This may not actually exist in the driver though 4. nv30 points color0 at depth in the depth-only case 5. nv30 sets NV34TCL_VIEWPORT_TX_ORIGIN to 0. This is probably unnecessary This patch attempts to unify the two files and preserve the existing behavior. 2010-03-15T04:03:02Z Luca Barbieri luca@luca-barbieri.com 2010-02-20T22:30:59Z urn:sha1:4d93ef1a015c8ec7341b0793e87ec375014436b3 The files are identical, except for an extra comment in nv30.