Skip to content

Identify MiniLoong Pocket 1 on LoongOS - #388

Open
jenny92-tech wants to merge 1 commit into
PortsMaster:mainfrom
jenny92-tech:feat/miniloong-pocket1-model
Open

jenny92-tech wants to merge 1 commit into
PortsMaster:mainfrom
jenny92-tech:feat/miniloong-pocket1-model

Conversation

@jenny92-tech

Copy link
Copy Markdown

On LoongOS 1.4.0.52, the device tree reports Rockchip RK3566 RK817 MINILOONG LP4X Board. Map that exact model to MiniLoong Pocket 1 when running LoongOS.

Tested the candidate probe on a MiniLoong Pocket 1. It reported MiniLoong Pocket 1, RK3566, and 960x720. Regression tests cover the matching board, a different board, and a different firmware.

@jenny92-tech
jenny92-tech force-pushed the feat/miniloong-pocket1-model branch from 1cbea4f to b706d6f Compare November 20, 2026 11:41
@jenny92-tech

Copy link
Copy Markdown
Author

@bmdhacks A follow-up on the MiniLoong Pocket 1. After testing LoongOS 1.3, I shared PortMaster’s firmware compatibility checklist with the MiniLoong firmware team. LoongOS 1.4 now covers most of the gaps I ran into on 1.3.

The biggest change for this PR is how the firmware handles SD cards. On 1.3, I had to point PortMaster at the card’s mount path directly. On 1.4, /roms/ports follows the card the game was launched from, and /PortMaster picks up the installation on that card, falling back to the bundled copy if needed. That removes the need for the path override I originally proposed here.

I also verified that 1.4 identifies itself as LoongOS in /etc/os-release, ships Python 3.10 and GNU tools such as sed, find, and tar, and supports Zstandard-compressed SquashFS runtimes. Those were all gaps on 1.3.

On my Pocket 1 running 1.4.0.52, I tested the official installer and GUI. The firmware launcher still needed a small fix to preserve the installer script when launching it. With that fix, installation completed, and after a reboot I could open the official PortMaster GUI from the SD card. My testing so far covers installation, GUI startup, and device detection.

That leaves a small upstream change in #388. It maps the board’s device-tree model to MiniLoong Pocket 1 and bumps DEVICE_INFO_VERSION so existing installations refresh their cached result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant