Displaying 13 results from an estimated 13 matches for "push_datap".
Did you mean:
push_data
2015 May 24
2
[Mesa-dev] [PATCH 2/2] nv30: fix clip plane uploads and enable changes
...t; 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);
> + PUSH_DATA (push, i);
> + PUSH_DATAp(push, nv30...
2015 May 24
2
[Mesa-dev] [PATCH 2/2] nv30: fix clip plane uploads and enable changes
...;>> - 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);
>>> + PUSH_DATA...
2015 May 24
2
[Mesa-dev] [PATCH 2/2] nv30: fix clip plane uploads and enable changes
...st->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_I...
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>
---
2015 Oct 10
3
[PATCH] nv50, nvc0: don't base decisions on available pushbuf space
...(!PUSH_SPACE(push, 16))
- break;
- nr = PUSH_AVAIL(push);
- assert(nr >= 16);
- nr = MIN2(count, nr - 1);
- nr = MIN2(nr, NV04_PFIFO_MAX_PACKET_LEN);
+ unsigned nr = MIN2(count, NV04_PFIFO_MAX_PACKET_LEN);
BEGIN_NI04(push, NV50_2D(SIFC_DATA), nr);
PUSH_DATAp(push, src, nr);
@@ -395,12 +388,9 @@ nv50_cb_push(struct nouveau_context *nv,
nouveau_pushbuf_validate(push);
while (words) {
- unsigned nr;
-
- nr = PUSH_AVAIL(push);
- nr = MIN2(nr - 7, words);
- nr = MIN2(nr, NV04_PFIFO_MAX_PACKET_LEN - 1);
+ unsigned nr = MIN2...
2015 Oct 10
2
[PATCH] nv50, nvc0: don't base decisions on available pushbuf space
...H_AVAIL(push);
>> - assert(nr >= 16);
>> - nr = MIN2(count, nr - 1);
>> - nr = MIN2(nr, NV04_PFIFO_MAX_PACKET_LEN);
>> + unsigned nr = MIN2(count, NV04_PFIFO_MAX_PACKET_LEN);
>> BEGIN_NI04(push, NV50_2D(SIFC_DATA), nr);
>> PUSH_DATAp(push, src, nr);
>> @@ -395,12 +388,9 @@ nv50_cb_push(struct nouveau_context *nv,
>> nouveau_pushbuf_validate(push);
>> while (words) {
>> - unsigned nr;
>> -
>> - nr = PUSH_AVAIL(push);
>> - nr = MIN2(nr - 7, words);
>> -...
2013 Sep 10
3
[Bug 69155] New: codegen/nv50_ir_emit_nv50.cpp:169:srcAddr8: Assertion `(offset <= 0x1fc || offset == 0x3fc) && !(offset & 0x3)' failed.
https://bugs.freedesktop.org/show_bug.cgi?id=69155
Priority: medium
Bug ID: 69155
Assignee: nouveau at lists.freedesktop.org
Summary: codegen/nv50_ir_emit_nv50.cpp:169:srcAddr8: Assertion
`(offset <= 0x1fc || offset == 0x3fc) && !(offset &
0x3)' failed.
Severity: critical
2015 May 17
14
[PATCH 00/12] Tessellation support for nvc0
This is enough to enable tessellation support on nvc0. It seems to
work a lot better on my GF108 than GK208. I suspect that there's some
sort of scheduling shenanigans that need to be adjusted for
kepler+. Or perhaps some shader header things.
Even with the GF108, I still get occasional blue triangles in Heaven,
but I get a *ton* of them on the GK208 -- seemingly the same issue,
but it's
2014 Feb 04
2
[PATCH 1/3] nv50: rework primid logic
Functionally identical but much simpler. Should also better integrate
with future layer/viewport changes/fixes.
Cc: 10.1 <mesa-stable at lists.freedesktop.org>
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
---
Not *strictly* necessary in stable, but it will make backporting later fixes
easier. No regressions in piglit.
src/gallium/drivers/nouveau/nv50/nv50_program.c | 5
2016 Jun 05
0
[RFC PATCH] nouveau: add locking
...pipe_context *pipe, const char *str, int len)
data_words = string_words;
else
data_words = string_words + !!(len & 3);
+ pipe_mutex_lock(nouveau_context(pipe)->screen->push_mutex);
BEGIN_NI04(push, SUBC_3D(NV04_GRAPH_NOP), data_words);
if (string_words)
PUSH_DATAp(push, str, string_words);
@@ -115,6 +120,7 @@ nv50_emit_string_marker(struct pipe_context *pipe, const char *str, int len)
memcpy(&data, &str[string_words * 4], len & 3);
PUSH_DATA (push, data);
}
+ pipe_mutex_unlock(nouveau_context(pipe)->screen->push_mutex);...
2014 Dec 31
0
[PATCH 2/2] nvc0: regenerate rnndb headers
...F(LINE_LENGTH_IN), 2);
+ BEGIN_NVC0(push, NVE4_P2MF(UPLOAD_LINE_LENGTH_IN), 2);
PUSH_DATA (push, 32);
PUSH_DATA (push, 1);
- BEGIN_1IC0(push, NVE4_P2MF(EXEC), 9);
+ BEGIN_1IC0(push, NVE4_P2MF(UPLOAD_EXEC), 9);
PUSH_DATA (push, 0x1001);
PUSH_DATAp(push, &tic->tic[0], 8);
@@ -437,13 +437,13 @@ nve4_validate_tsc(struct nvc0_context *nvc0, int s)
tsc->id = nvc0_screen_tsc_alloc(nvc0->screen, tsc);
PUSH_SPACE(push, 16);
- BEGIN_NVC0(push, NVE4_P2MF(DST_ADDRESS_HIGH), 2);
+ BEGIN_NVC0(push, NVE...
2014 Jan 13
20
[PATCH 00/19] nv50: add sampler2DMS/GP support to get OpenGL 3.2
OK, so there's a bunch of stuff in here. The geometry stuff is based on the
work started by Bryan Cain and Christoph Bumiller.
Patches 01-12: Add support for geometry shaders and fix related issues
Patches 13-14: Make it possible for fb clears to operate on texture attachments
with an explicit layer set (as is allowed in gl 3.2).
Patches 15-17: Make ARB_texture_multisample work
2014 Dec 31
2
[PATCH 1/2] nv50: regenerate rnndb headers
The headers hadn't been regenerated in a long time, and there were a few
minor divergences. Among other things, rnndb has changed naming to
G80/etc, for now I've not tackled switching that over and manually
replaced the nvidia codenames back to the chip ids. However no other
modifications of the headergen'd headers was done.
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>