Repository navigation
Add one keyboard without a reboot (PR-4) - #69
Closed
Cryptokid92 wants to merge 1 commit into
Closed
Cryptokid92 wants to merge 1 commit into
Cryptokid92 wants to merge 1 commit into
Conversation
The panel has no /dev/input. CONFIG_INPUT_UINPUT is off. A built-in uinput needs a new kernel and a reboot. build-uinput.sh builds drivers/input/misc/uinput.c as an external module for the phone release string. bridge.c writes one EV_KEY when it reads one byte. SEAT_DRY_RUN prints EV_KEY and does not open a device. The phone load is a later lane. Assisted-by: LLM [Grok]
Owner
|
Thanks for the interest in the Pixel 8 Pro, @Cryptokid92. I'm going to close this one rather than take it, and I want to explain why, because the effort is clearly real.
The place to start is issue #1: wait for the husky test image, get stock Android onto slot A first (your phone is on GrapheneOS), and run the published runbooks. Pull requests that come out of that, with results from your own phone, are very welcome. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The Pixel 8 Pro already shows the Omarchy clock, and
/dev/inputdoes not exist. Hyprland needs one keyboard.CONFIG_INPUTandCONFIG_INPUT_EVDEVare built in.CONFIG_INPUT_UINPUTis not set.input_register_deviceis exported, souinput.kocan load on the running kernel.bridge.copens/dev/uinputand writes oneEV_KEYwhen it reads one byte on stdin. With-DSEAT_DRY_RUNit printsEV_KEYand does not open a device.Scope
device/husky/seat/build-uinput.shcopiesdrivers/input/misc/uinput.cto/tmp/omamobile-seat-uinputand runsmake -C "$KERNEL_SRC" O="$KERNEL_OUT" ARCH=arm64 LLVM=1 M="$STAGING" modules.include/config/kernel.release, writes7.3.0-rc6-omamobile-push1-ge446d69d2ab2for the build, and restores the saved file on exit. It also saves and restoresinclude/generated/utsrelease.h, because module vermagic isUTS_RELEASE.Image.device/husky/seat/bridge.cis the keyboard.device/husky/seat/README.mdnames the printed module path, thebridgebinary, the insmod line, and the evtest line.Phone insmod, evtest, and Hyprland are out of this PR.
Tradeoffs
A built-in
CONFIG_INPUT_UINPUTneeds a new kernel and a reboot. This PR builds the sameuinput.cas a module and leaves the running kernel in place.Blast Radius
The diff is three new files under
device/husky/seat/. This head does not load a module and does not touch the phone. The clock, the panel, and slot B stay as they are. A failed module build still restores the saved release files.Verification
This head has only the host dry-run. The phone load is a later lane. The ten live lanes and the perf probe have not been run.
cc -DSEAT_DRY_RUN -o /tmp/seat-dry device/husky/seat/bridge.c && /tmp/seat-dryprintedstruct input_event { type = EV_KEY, code = KEY_A, value = 1 }and exited 0.