search for: fdec

...if(!nvfx->use_nv4x) + if(!nvfx->is_nv4x) goto nv3x_cflow; nv40_fp_brk(fpc); break; @@ -951,7 +951,7 @@ static boolean nvfx_fragprog_assign_generic(struct nv30_context *nvfx, struct nvfx_fpc *fpc, const struct tgsi_full_declaration *fdec) { - unsigned num_texcoords = nvfx->use_nv4x ? 10 : 8; + unsigned num_texcoords = nvfx->is_nv4x ? 10 : 8; unsigned idx = fdec->Range.First; unsigned hw; @@ -1002,7 +1002,7 @@ nvfx_fragprog_parse_decl_output(struct nv30_context* nvfx, struct nvfx_fpc *fpc, case 2: hw =...

A reworked version of 3 out of 4 patches mentioned earlier. [1/4]: Fixes nearly all piglit vertprog testcases, due to now being able to pass the results on to the fragment shader. V2: rename samplers to texcoords. [2/4]: Fixes shader compiler assertion errors, as some source registers do not exist for certain operations. Fixes several piglit tests when mesa is compiled with --enable-debug [3/4]:

For all these patches I'd say: testers are welcome. The first three patches seem good enough to push as we speak IMHO (so if you agree, go ahead!), whereas for the fourth I don't know if this is the desired way to fix. The result of these four patches is that NV34 gives a nearly-correct desktop experience, where only some fading animations appear broken. It's quite useable now! [1/4]:

...atching /local/domain/0/device-model/2/logdirty/cmd Watching /local/domain/0/device-model/2/command Watching /local/domain/2/cpu char device redirected to /dev/pts/2 qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 9d6fd940-b893-fdec-092d-208a90b9e5fc Time offset set 0 populating video RAM at ff000000 mapping video RAM from ff000000 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/2/xen_extended_power_mgmt): read e...

...; 10; >>> + for (result = 0; result < num_texcoords; result++) { >>> + if (fp->texcoord[result] == *idx + 8) { >> >> maybe i'm too tired, but why exactly *idx + 8 ? > See nvfx_fragprog.c: > > fpc->fp->texcoord[hw] = fdec->Semantic.Index + 8; > > when the semantic is GENERIC. (and 0xfffe when it's PCOORD). This is > because there can be up to 8 TEXCOORD's. yet you run for 8 or 10 texcoords. Wont this cause problems on nv40+? > >>> + sem = TGSI_SEMANTIC_TEXCOORD; >>&...

On 25.05.2015 21:29, Ilia Mirkin wrote: > Commit 8acaf862dfe switched things over to use TEXCOORD instead of > GENERIC, but did not update the nv30 swtnl draw paths. This teaches the > draw logic about TEXCOORD. > > Among other things, this fixes a crash in demos/arbocclude when using > swtnl. Curiously enough, the point-sprite piglit works without this. > > Signed-off-by:

At the point of this section *http://ruby.railstutorial.org/chapters/sign-up#sec-signup_failure*<http://ruby.railstutorial.org/chapters/sign-up#sec-signup_failure> clicking the "Create my account" button on the signup form shows the following image at <http://ruby.railstutorial.org/images/figures/signup_failure_rails_4.png> According to the tutorial, I must modify

Hi all! :) I see that this is partially covered in the mailing list archive but at the moment I can''t find a straight & working answer. I have an imq device with dynamically attacched classes/qdiscs/filters. There is a hashing filter that maps the last octet of an user''s IP address to a class (and associated qdisc). The "empty" filter looks like this: filter