Displaying 5 results from an estimated 5 matches for "vp_upload_const_id".
2015 May 24
2
[Mesa-dev] [PATCH 2/2] nv30: fix clip plane uploads and enable changes
...ate_clip(struct nv30_context *nv30)
> uint32_t clpd_enable = 0;
>
> for (i = 0; i < 6; i++) {
> - if (nv30->rast->pipe.clip_plane_enable & (1 << i)) {
> - if (nv30->dirty & NV30_NEW_CLIP) {
> - BEGIN_NV04(push, NV30_3D(VP_UPLOAD_CONST_ID), 5);
> - PUSH_DATA (push, i);
> - PUSH_DATAp(push, nv30->clip.ucp[i], 4);
> - }
> -
> - clpd_enable |= 1 << (1 + 4*i);
> + if (nv30->dirty & NV30_NEW_CLIP) {
> + BEGIN_NV04(push, NV30_3D(VP_UPLOAD_CONST_ID), 5)...
2015 May 24
2
[Mesa-dev] [PATCH 2/2] nv30: fix clip plane uploads and enable changes
...30)
>>> uint32_t clpd_enable = 0;
>>> for (i = 0; i < 6; i++) {
>>> - if (nv30->rast->pipe.clip_plane_enable & (1 << i)) {
>>> - if (nv30->dirty & NV30_NEW_CLIP) {
>>> - BEGIN_NV04(push, NV30_3D(VP_UPLOAD_CONST_ID), 5);
>>> - PUSH_DATA (push, i);
>>> - PUSH_DATAp(push, nv30->clip.ucp[i], 4);
>>> - }
>>> -
>>> - clpd_enable |= 1 << (1 + 4*i);
>>> + if (nv30->dirty & NV30_NEW_CLIP) {
>>> +...
2015 May 24
2
[Mesa-dev] [PATCH 2/2] nv30: fix clip plane uploads and enable changes
...d_enable = 0;
>>>>> for (i = 0; i < 6; i++) {
>>>>> - if (nv30->rast->pipe.clip_plane_enable & (1 << i)) {
>>>>> - if (nv30->dirty & NV30_NEW_CLIP) {
>>>>> - BEGIN_NV04(push, NV30_3D(VP_UPLOAD_CONST_ID), 5);
>>>>> - PUSH_DATA (push, i);
>>>>> - PUSH_DATAp(push, nv30->clip.ucp[i], 4);
>>>>> - }
>>>>> -
>>>>> - clpd_enable |= 1 << (1 + 4*i);
>>>>> + if (nv30-...
2015 May 24
2
[PATCH 1/2] nv30: avoid doing extra work on clear and hitting unexpected states
Clearing can happen at a time when various state objects are incoherent
and not ready for a draw. Some of the validation functions don't handle
this well, so only flush the framebuffer state. This has the advantage
of also not doing extra work.
This works around some crashes that can happen when clearing.
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
---
2010 Feb 26
5
[PATCH 0/5] renouveau: nv30/nv40 unification
This patchset applies some minor fixes to renouveau.xml and then unifies
the nv30 and nv40 register definitions.
nv30 and nv40 are very similar and have the same offsets for the registers
they share.
The major differences are:
1. Texture setup is different due to full NPOT support on nv40
2. More advanced blending/render targets on nv40
3. NV30 has fixed function registers, which NV40 lacks
The