search for: nvxx_compute_upload_input

...I deal with >>>> those ? >>> >>> The input kernel parameters are directly passed through a call to >>> pipe_context::launch_grid. You just have to fill the >>> pipe_grid_info::input array with your parameters and they will be >>> uploaded by nvXX_compute_upload_input(). >> >> Right, the uploading side I understand, the question is how to get to >> them from >> the compute kernel's tgsi code ? > > Right, I wonder if there is already a DECL INPUT or something like that for input parameters of shaders. Oh yeah, there is TGSI_FILE_...

...t;> getting to the kernel input kernel parameters, how would I deal with >> those ? > > The input kernel parameters are directly passed through a call to pipe_context::launch_grid. You just have to fill the pipe_grid_info::input array with your parameters and they will be uploaded by nvXX_compute_upload_input(). Right, the uploading side I understand, the question is how to get to them from the compute kernel's tgsi code ? If I understand you correctly you are suggesting to use BUFFER[0] for this, that is fine from a nouveau point-of-view, but might be a bit nouveau centric way of looking at thing...

...;>> those ? >>>> >>>> The input kernel parameters are directly passed through a call to >>>> pipe_context::launch_grid. You just have to fill the >>>> pipe_grid_info::input array with your parameters and they will be >>>> uploaded by nvXX_compute_upload_input(). >>> >>> Right, the uploading side I understand, the question is how to get to >>> them from >>> the compute kernel's tgsi code ? >> >> Right, I wonder if there is already a DECL INPUT or something like >> that for input parameters of shad...

...>>>> >>>> >>>> The input kernel parameters are directly passed through a call to >>>> pipe_context::launch_grid. You just have to fill the >>>> pipe_grid_info::input array with your parameters and they will be >>>> uploaded by nvXX_compute_upload_input(). >>> >>> >>> Right, the uploading side I understand, the question is how to get to >>> them from >>> the compute kernel's tgsi code ? >> >> >> Right, I wonder if there is already a DECL INPUT or something like that >> for in...

...el parameters, how would I deal with >>> those ? >> >> The input kernel parameters are directly passed through a call to >> pipe_context::launch_grid. You just have to fill the >> pipe_grid_info::input array with your parameters and they will be >> uploaded by nvXX_compute_upload_input(). > > Right, the uploading side I understand, the question is how to get to > them from > the compute kernel's tgsi code ? Right, I wonder if there is already a DECL INPUT or something like that for input parameters of shaders. Oh yeah, there is TGSI_FILE_INPUT, maybe this is wh...

Hi, On 19-02-16 20:43, Ilia Mirkin wrote: > On Fri, Feb 19, 2016 at 5:36 AM, Hans de Goede <hdegoede at redhat.com> wrote: >> 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

...s not solve > getting to the kernel input kernel parameters, how would I deal with > those ? The input kernel parameters are directly passed through a call to pipe_context::launch_grid. You just have to 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 > ho...