Question on keyboard event devices in linux
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 858
- Forks
- 112
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 4
Description
Hi all,
I have a custom keypad served with uinput (or now with libevdev) in linux-arm host. This keypad is not hooked to any tty, but it creates just /dev/input/eventX device. I checked the repo and kbd_event.c is now deprecated. My question is what is the recommended solution to my setup? Should I bring back kbd_event.c into the compilation or there is another way the event device can be somehow redirected to tty and then standard kbd_tty.c driver could be used?
I dont use X11.
Thank you for you suggestions,
Michael
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 reading kbd_event.c and kbd_tty.c, then inspect how the Linux input path handles uinput or libevdev event devices without X11. The issue does not define a chosen implementation or acceptance criteria; completion would require maintainer guidance on whether to restore kbd_event.c or support another event-to-keyboard path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100