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,699
    • Issues 2,699
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 911
    • Merge requests 911
  • 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
  • Issues
  • #42
Closed
Open
Created Sep 13, 2019 by Rob Clark@robclark💬Owner

kernel: clean up zap "shader" handling

Currently the kernel looks for zap firmware, and if it doesn't find it, decides that it is a platform where zap is not required to take the GPU out of secure mode at boot. Unfortunately trying to take GPU out of secure mode directly (without zap) on a platform where zap is required, means insta-reboot.

We should re-work this to refuse to load if zap fw is missing and the zap node in dtb is present. The presence/absence of a zap node is a more reliable way to tell if zap is required to take GPU out of secure mode.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking