Conversation
Contributor
Author
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.
Closes #3.
Depends on #4 and is intentionally stacked on
codex/tiny-core-baseuntil the Tiny Core migration lands.This adds a 64-bit Termux host path without introducing a second kernel architecture.
android/setup-termux.shinstalls the QEMU/tools required by the existing Tiny Core fetcher, andandroid/run.shdelegates directly totinycore/run.sh, preserving the pinned CorePure64 image, checksum verification, QEMU TCG configuration, serial console, RAM override and kernel command-line contract used elsewhere.The Android device therefore remains only a QEMU host: no root, bootloader replacement or Android-kernel modification is required. The canonical guest remains x86_64 for now; an ARM64 guest should follow only when the shared Tiny Core/Flow target supports it.