drv-ps2-keyboard

drv-ps2-keyboard is the PS/2 keyboard protocol translator daemon.

EriX is a clean-room, capability-based microkernel operating system written entirely in Rust.

Technical requirements are tracked in the EriX requirements, conventions, and project documentation.

See:

• docs for design documents, specifications, and development plans.
• Related architecture repositories for kernel, services, libraries, drivers, and integration tooling.

Purpose of This Repository

This repository implements the EriX ps2 keyboard driver service. Its purpose in EriX is to mediate ps2 keyboard hardware or protocol behavior under explicit deviced / procd ownership.

Functionally, it implements the driver startup, runtime, and validation contracts for ps2 keyboard. The repository keeps the implementation, interface contracts, tests, and documentation for that behavior in one reviewable ownership boundary.

The maintained responsibilities are:

• implement the ps2 keyboard driver logic behind explicit driver authority
• bind only to startup-assigned device, interrupt, and transport capabilities
• serve bounded driver operations without creating public service authority
• keep driver validation and failure behavior documented for integration tests

Clean-Room Policy

EriX follows a strict clean-room philosophy:

• No external source code may be copied.
• No external Rust crates are allowed.
• No code generation tools that embed third-party code.
• All code must be authored within the project.

Violations will result in rejection of the contribution.

License

All EriX repositories are licensed under the ISC License.

Development Model

EriX development is modular, deterministic, reproducible, authority-explicit, security-first, and self-hosting oriented.

This repository follows the project roadmap and the validation rules documented in its own roadmap.

Runtime model

• Single-threaded translate-and-forward loop.
• Fixed message buffer (1024 bytes).
• Monotonic request IDs for i8042 reads and input appends.
• No dynamic allocation.

Feature flags

• drv-ps2-keyboard-runtime
• drv-ps2-keyboard-runtime-phase3-input
• compatibility aliases:
  • drv-ps2-keyboard-integration-smoke
  • drv-ps2-keyboard-integration-phase3-input
  • drv-ps2-keyboard-integration-force-fail

Build and test

cargo fmt --all -- --check
cargo clippy --all-targets --all-features -- -D warnings
cargo test --all-targets --all-features

Dependencies

• lib-bootstrap
• lib-capabi
• lib-ipc
• lib-service
• lib-input
• ipc-syscall-x86_64

No third-party crates are used.

Dynamic Boot Artifact Evidence

Phase 5.4.37 documents drv-ps2-keyboard as a dynamic boot artifact. The image build packages the PS/2 keyboard driver service as an ELF64 x86_64 ET_DYN executable with .erix_dynlink metadata in the signed dynlink- store and mirrors it under /lib/erix/dynlink with its required shared objects.

Startup remains deviced through procd dynamic driver creation with a role- derived executable identity; authority remains explicit controller/provider peers. Dynamic packaging and filesystem mirror records are evidence and launch inputs only; they do not grant filesystem, loader, object-store, service- discovery, provider-bypass, block-device, or dynlinkd authority. drv- ps2-keyboard receives only the documented startup endpoints, peers, and capabilities for its role.

Governance Principles

drv-ps2-keyboard governance is scoped to the ps2 keyboard driver role and its assigned hardware/provider authority.

The scoped governance rules are:

• It must be started and supervised through deviced and procd, not as an independently discovered public service.
• It uses only the device, interrupt, transport, and provider capabilities explicitly transferred at startup.
• It keeps hardware-specific behavior inside the driver while leaving device-matching policy to deviced.
• It rejects malformed device state and unexpected authority instead of broadening access.

Authority Boundaries

• drv-ps2-keyboard does not receive named, filesystem-provider, or peer-driver authority.
• New hardware access requires explicit manifest, startup, and integration-test coverage.

Contact

Development occurs in EriX organization and discussions happen in issues and design documents.

No decisions are considered valid without documented rationale.

Maintainers can be reached via email: admin@erikinkinen.fi.