[PATCH 7/9] drm/vc4: Add support for drawing 3D frames.

Eric Anholt eric at anholt.net
Wed Dec 2 11:27:27 PST 2015


Emil Velikov <emil.l.velikov at gmail.com> writes:

> Hi Eric,
>
> On 1 December 2015 at 20:35, Eric Anholt <eric at anholt.net> wrote:
>> The user submission is basically a pointer to a command list and a
>> pointer to uniforms.  We copy those in to the kernel, validate and
>> relocate them, and store the result in a GPU BO which we queue for
>> execution.
>>
>> Signed-off-by: Eric Anholt <eric at anholt.net>
>> ---
>>  drivers/gpu/drm/vc4/Makefile           |   7 +
>>  drivers/gpu/drm/vc4/vc4_drv.c          |  15 +-
>>  drivers/gpu/drm/vc4/vc4_drv.h          | 192 +++++++
>>  drivers/gpu/drm/vc4/vc4_gem.c          | 640 ++++++++++++++++++++++
>>  drivers/gpu/drm/vc4/vc4_irq.c          | 210 ++++++++
>>  drivers/gpu/drm/vc4/vc4_packet.h       | 399 ++++++++++++++
>>  drivers/gpu/drm/vc4/vc4_render_cl.c    | 631 ++++++++++++++++++++++
>>  drivers/gpu/drm/vc4/vc4_trace.h        |  63 +++
>>  drivers/gpu/drm/vc4/vc4_trace_points.c |  14 +
>>  drivers/gpu/drm/vc4/vc4_v3d.c          |  37 ++
>>  drivers/gpu/drm/vc4/vc4_validate.c     | 955 +++++++++++++++++++++++++++++++++
>>  include/uapi/drm/vc4_drm.h             | 141 +++++
>>  12 files changed, 3303 insertions(+), 1 deletion(-)
>
> Am I assuming correct that the above are the exact same ones copied in
> mesa (and used only then simulator is used) ? In the short term
> keeping the two in sync would be fine, although wondering if you have
> plans to reshuffle things in the long term ?

This code is not exactly synced with Mesa, but I do sync between them on
a regular basis.  The in-Mesa copy is secondary, and just a way for me
to get testing done faster (in the simulation environment with gdb) than
I can in the kernel with printfs.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20151202/ea51e2b1/attachment-0001.sig>


More information about the dri-devel mailing list