Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,882
    • Issues 2,882
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 924
    • Merge requests 924
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mesa
  • mesamesa
  • Merge requests
  • !10820

Merged
Created May 16, 2021 by Ilia Mirkin@imirkinOwner

nvc0: fix 3d images

  • Overview 1
  • Commits 1
  • Pipelines 4
  • Changes 2

The hardware has no support for 3d image loads/stores. So present the image as a larger 2d image and fudge the coordinates. Note that a 2d image (in the shader) may be backed by a slice of a 3d image, so we always have to do the coordinate adjustments for 2d as well.

This is largely copied from the nv50 support, which has the same restriction, with extra care taken to differentiate loads (which specifies the X coordinate in bytes) and stores, which specifies it in (formatted) pixels.

Signed-off-by: Ilia Mirkin imirkin@alum.mit.edu

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: fermi-3d-images