Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
W
weston
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 273
    • Issues 273
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 114
    • Merge Requests 114
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • wayland
  • weston
  • Issues
  • #305

Closed
Open
Opened Nov 15, 2019 by Pekka Paalanen@pqMaintainer

Manual DRM-backend smoke-test with VKMS

Add a test in the test suite that runs Weston/DRM/pixman using the non-default seat seat-vkms. Whether this actually runs depends on whether there is a DRM device available on seat-vkms, otherwise the test is skipped. Input devices are not required or used.

I call this a manual test, because this test would depend on the local system setup to have VKMS kernel module loaded and seat-vkms configured.

It requires Weston to be able to start on a non-default seat with normal user permissions: either the user must have access to the VKMS DRM device, or logind needs to be able to hand that out. weston-launch cannot be used, because it would require root permissions to install as setuid-root, and without setuid-root it cannot provide anything useful.

Weston on non-default seat depends also on skipping all VT/tty setup.

This task depends on !287 (merged).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: wayland/weston#305