Conversation
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
1 participant
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.
What
Research notes on what Knulli support requires — the OS, the target hardware, and the packaging format a Knulli .opk needs.
.jez/artifacts/research-brief-knulli-support.md— full research brief.Why
Knulli is a popular retro-handheld OS that ships apps as .opk packages. Before committing to a build pipeline, we need to know the target (Anbernic RK3326), the toolchain expectations, and what the existing retsurf Knulli work did or didn't ship.
How
The brief captures device specs, the Knulli software stack, the .opk packaging format, known retsurf efforts, and open blockers. The second commit clarifies which blockers are deferred (e.g. GPU acceleration, launcher integration) versus must-solve (AArch64 .opk that boots and sends).