search for: glcalllists

...GetProcAddress func: 'glBegin' trace:wgl:wglGetProcAddress func: 'glBindTexture' trace:wgl:wglGetProcAddress func: 'glBitmap' trace:wgl:wglGetProcAddress func: 'glBlendFunc' trace:wgl:wglGetProcAddress func: 'glCallList' trace:wgl:wglGetProcAddress func: 'glCallLists' trace:wgl:wglGetProcAddress func: 'glClear' : Regards Zalle

Hi, My name is Krzysztof and currently I'm working on porting nouveau (gallium3d driver + libdrm + drm) to AROS Research OS (http://www.aros.org). I completed a quite successful port of "old" drm (one from libdrm git - now removed) and currently I'm working on drm port from the nouveau kernel tree git. Right now I'm faced with rather peculiar memory allocation/access

a fence in the command stream when you change the vtxbuf addresses, on nv50 that is, I don't know about nv40, sorry. But it *did* look like the blob inserts a fence after *uploading* new data to a vertex buffer. That's why there's method 0x142c in nv50_draw_arrays. > Other observations: > - the data during execution of gl commands actually seems to be put into > location C -

https://bugs.freedesktop.org/show_bug.cgi?id=63051 Priority: medium Bug ID: 63051 Assignee: nouveau at lists.freedesktop.org Summary: Displist with multiple OpenGL contexts crashes. Severity: major Classification: Unclassified OS: Linux (All) Reporter: ideasman42 at gmail.com Hardware: x86-64 (AMD64)

It seems that Noveau is assuming that once the FIFO pointer is past a command, that command has finished executing, and all the buffers it used are no longer needed. However, this seems to be false at least on G71. In particular, the card may not have even finished reading the input vertex buffers when the pushbuffer "fence" triggers. While Mesa does not reuse the buffer object itself,