oxidecomputer / oxidecomputer/propolis
Add support for more complicated keyboard scan codes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
https://github.com/oxidecomputer/propolis/pull/211 implements a basically-fully-functional ps/2 keyboard, but there are some gaps in scan code handling. Part of the differences here were driven by a desire for backwards compatibility between different sizes of keyboards.
Such gaps include:
- the Pause key (a 4-byte scan code) is not yet implemented (for Set 1 or Set 2)
- Some keys, such as Insert and Delete, will send different scan codes, depending on whether Shift is down or NumLock is on.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing pull request #211 and the existing PS/2 keyboard scan-code handling it introduced. Check how Set 1 and Set 2 are represented, then cover the Pause key and the Shift- or NumLock-dependent Insert and Delete scan codes; done means these listed gaps work while preserving keyboard-size compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100