All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zachary Catlin <z@zc.is>
To: dri-devel@lists.freedesktop.org
Subject: Questions about libdrm programming
Date: Fri, 10 Jun 2011 21:03:35 -0400	[thread overview]
Message-ID: <20110610210335.69fe18af@b-612.localnet> (raw)

I'm interested in (1) using my graphics card for computations and
(2) low-level shader code, and I'm looking for guidance on how I would
go about doing the following operations with libdrm (sans Mesa):

* client-side initialization
* loading textures into the GPU
* loading a bytecode shader into the GPU
* creating a texture on the GPU without uploading data
* running the shader using the uploaded textures as inputs and the
  non-uploaded texture as the output
* transferring the output texture into main memory
* tear-down, finalization

The GPU in question is a Radeon RV730, if any hardware-dependent
discussion is needed. I've tried to understand the workflow by looking
at the Mesa and Plymouth sources and the documentation I've found for
the DRI/DRM, but I could still use some guidance.

             reply	other threads:[~2011-06-11  1:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-11  1:03 Zachary Catlin [this message]
2011-06-11  1:39 ` Questions about libdrm programming Dave Airlie
2011-06-11  3:34   ` Zachary Catlin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110610210335.69fe18af@b-612.localnet \
    --to=z@zc.is \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.