search for: nv50_compute_upload_input

...new MEMORY keyword look as intended to you? 2) This only solves the accessing of the global memory, it does not solve getting to the kernel input kernel parameters, how would I deal with those ? Currently the kernel input parameters are uploaded by src/gallium/drivers/nouveau/nv50/nv50_compute.c: nv50_compute_upload_input() Are we going to change how these parameters get uploaded ? And if not how do we get to these parameters from TGSI now that we no longer have RES[#] to do so ? I think we should also keep in mind that what works for nouveau may not work for other GPU-s, so we should either introduce a MEMORY[x],...

...fill the pipe_grid_info::input array with your parameters and they will be uploaded by nvXX_compute_upload_input(). I will have a look at the test_input_global(). Thanks! > > Currently the kernel input parameters are uploaded by > src/gallium/drivers/nouveau/nv50/nv50_compute.c: > nv50_compute_upload_input() > > Are we going to change how these parameters get uploaded ? And if not > how do we > get to these parameters from TGSI now that we no longer have RES[#] to > do so ? > > I think we should also keep in mind that what works for nouveau may not > work > for other GPU-s,...

Hi, On 18-02-16 17:39, Ilia Mirkin wrote: > On Thu, Feb 18, 2016 at 9:45 AM, Hans de Goede <hdegoede at redhat.com> wrote: >> But this does not seem to be hooked up yet for nouveau. > > Samuel has patches. See > https://cgit.freedesktop.org/~hakzsam/mesa/log/?h=arb_compute_shader_v3 Cool, I will take a look at those. >> So some questions: >> -The commit by