Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • X xf86-input-emulated
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Povilas Kanapickas
  • xf86-input-emulated
  • Merge requests
  • !1

Implement emulated input driver

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Povilas Kanapickas requested to merge initial into master Sep 11, 2020
  • Overview 14
  • Commits 1
  • Pipelines 4
  • Changes 12

This allows submission of fake input events to control the X server from tests.

The basic architecture is simple. Upon startup, the driver creates two fifo files, one for reading and another for writing at pre-configured paths. The controlling process would send events to the driver which would itself then call corresponding xf86Post*Event with appropriate parameters.

The controlling process can send a synchronization event which causes the driver to wait until previous input events have been processed. For this purpose the driver uses this new API in X server: xorg/xserver!510 (merged).

Currently we uses two pipes for bidirectional communication. A better idea would be to use a domain socket, but as initial implementation two pipes looked simpler.

Edited Sep 11, 2020 by Povilas Kanapickas
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: initial