search for: nv30_draw_vbo

Hi Ilia, you were straight to the point for me in: "src/mesa/vbo will upload it to a vbo. The driver then points the hardware at the vbo and tells it to read from there." But where is it the function that implements this? Is it in nv30_draw_vbo(...)? Please, give me a function name or at least a file name? 2016-04-19 10:04 GMT-04:00 Ilia Mirkin <imirkin at alum.mit.edu>: > On Tue, Apr 19, 2016 at 8:52 AM, Daniel Melo Jorge da Cunha > <dmjcunha at gmail.com> wrote: > > Hi, for example, if I have glVertex3f(0.75, 0...

...ut floats before it is sent to the card? Where is the code for it? If you say the floats are memory mapped as in exec->vtx.buffer_map = (GLfloat *)ctx->Driver.MapBufferRange(...) I would say from what I learned that it has to pass through gallium and that means: st_draw_vbo(...) ending up in nv30_draw_vbo(..) but these functions don't make any reference to those (memory mapped) input floats. So where is the piece of code that instructs the card to fetch those three (possibly processed) input floats and send them to the card? Thanks in advance. -------------- next part -------------- An HTML att...

...sibly when glXSwapBuffers is called? Is the glColor(...) (the three floats) stored in the mmapped twice, one for each vertex? HELP I'M LOST :( This mine consideration is wrong... I guess... st_draw.c coments that all "rendering" is done through st_draw_vbo() which would end up calling nv30_draw_vbo() which would send data to the card... but where is the missing link?? The floats (for the vertices and color) are already mapped by ctx->Driver.MapBufferRange...*/ glBegin(GL_LINES); glColor3f(1.0, 1.0, 1.0); glVertex3f(0.0f, 0.0f, 0.0f); glVertex3f(50.0f, 50.0f, 1.0f); glE...

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/gallium/drivers/nouveau/nouveau_buffer.c | 4 +--- src/gallium/drivers/nouveau/nouveau_context.h | 1 - 2 files changed, 1 insertion(+), 4 deletions(-) diff --git a/src/gallium/drivers/nouveau/nouveau_buffer.c b/src/gallium/drivers/nouveau/nouveau_buffer.c index e308ff4..904e2cc 100644 ---

...driver can't handle the format.) > > If you say the floats are memory mapped as in > exec->vtx.buffer_map = (GLfloat *)ctx->Driver.MapBufferRange(...) I would > say > from what I learned that it has to pass through gallium and that means: > st_draw_vbo(...) ending up in nv30_draw_vbo(..) but these functions don't > make > any reference to those (memory mapped) input floats. So where is the piece > of > code that instructs the card to fetch those three (possibly processed) input > floats > and send them to the card? > > Thanks in advance. The vbo mod...

...at gmail.com> wrote: > Hi Ilia, you were straight to the point for me in: > > "src/mesa/vbo will upload it to a vbo. The driver then points the > hardware at the vbo and tells it to read from there." > > But where is it the function that implements this? Is it in > nv30_draw_vbo(...)? Please, give me a function name or > at least a file name? Before draw_vbo is called, the vbo will have been set up via pipe->bind_vertex_elements_state and pipe->set_vertex_buffers. The draw call will then validate those, by calling nv30_state_validate (or something along those lin...

...but am not sure, that it will come in as a constant attribute (i.e. a VBO attribute with stride 0). > HELP I'M LOST :( This mine consideration is wrong... I guess... > st_draw.c > coments that all "rendering" is done through st_draw_vbo() which would end > up > calling nv30_draw_vbo() which would send data to the card... but where is > the > missing link?? The floats (for the vertices and color) are already mapped by > ctx->Driver.MapBufferRange...*/ The gallium state tracker does not support immediate vertex submission. There's a "vbo" layer in fron...

...alidate (nv30=nv30 at entry=0x805cc70, hwtnl=hwtnl at entry=1 '\001') at nv30_state_validate.c:487 screen = 0x8078800 push = 0x8078938 bctx = 0x805d340 bref = <optimized out> validate = 0xb76a9d78 <hwtnl_validate_list+88> #8 0xb66c629e in nv30_draw_vbo (pipe=0x805cc70, info=0xbfffef10) at nv30_vbo.c:563 push = 0x8078938 #9 0xb69a4fb3 in u_vbuf_draw_vbo (mgr=0x81144e8, info=info at entry=0xbfffef10) at util/u_vbuf.c:1128 pipe = 0x805cc70 start_vertex = <optimized out> min_index = <optimized out>...

...} nouveau_pushbuf_bufctx(push, bctx); diff --git a/src/gallium/drivers/nouveau/nv30/nv30_vbo.c b/src/gallium/drivers/nouveau/nv30/nv30_vbo.c index 67ab829..d4e384b 100644 --- a/src/gallium/drivers/nouveau/nv30/nv30_vbo.c +++ b/src/gallium/drivers/nouveau/nv30/nv30_vbo.c @@ -564,7 +564,7 @@ nv30_draw_vbo(struct pipe_context *pipe, const struct pipe_draw_info *info) if (nv30->vbo_user && !(nv30->dirty & (NV30_NEW_VERTEX | NV30_NEW_ARRAYS))) nv30_update_user_vbufs(nv30); - nv30_state_validate(nv30, TRUE); + nv30_state_validate(nv30, ~0, TRUE); if (nv30->draw_...