Skip to content
Projects

reMESA-devgroup/reMESA has 26 GitHub stars and 1 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-15 17:18 UTC. Last push 2026-11-13.

How these counts are measured

Measured star growth

in 24h
0
in 7 days
Update delayed
in 15 days
Update delayed
in 1 month
Update delayed

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

Open-source 3D driver for Intel Poulsbo / GMA 500 (PowerVR SGX535), Mesa Gallium + gma500 kernel work. SGX544 research.

Creative & Media

README.md

Original

reMESA logo

reMESA

Hey! I'm Gama. I started with one GPU (Intel Poulsbo) and somehow ended up with two. Welcome to reMESA: an independent effort to understand the GMA500 (SGX535) and SGX544 and eventually give them usable open graphics drivers, most unprofessional driver made in Galaxy Tab S7.

Pipoca says hello too.

Pipoca saying hello Pipoca: The Mini 12 can show a desktop, but that doesn't mean Linux has an open 3D driver for its GPU. That's why we're here.

Why are we doing this?

Intel Poulsbo machines can still display a Linux desktop, but gma500 alone doesn't provide a modern open SGX 3D stack (yet hehe). The SGX544 has its own platform and driver history, including Android graphics components. Public programming information is limited for both. So I've been digging.

Both projects are here because I want to understand these chips and build open graphics support for them. That doesn't mean they speak the same language: their command formats and hardware interfaces need their own evidence, even when a general tool can be shared.

The SGX535 project started on September 16, 2026. Since then I've been studying historical drivers, compiler behavior and hardware captures, writing independent code, and testing on a Dell Mini 12. Some discoveries took hours. 0x07000345 took a lot, lot, lot, LOT longer. ALWAYS.

Pipoca checking the details Pipoca: SGX535 is the one drawing on Gama's Mini 12. SGX544 is still at the research stage. Similar names don't make them the same GPU.
SGX535 SGX544
Architecture PowerVR Series5, rev121 in the tested Mini 12 PowerVR SGX544; its interfaces must be independently established
Devices and environment Intel Poulsbo / GMA 500, Dell Mini 12, Linux Android driver research; physical testing depends on access to suitable hardware
Maturity Experimental Mesa/Gallium and kernel integration Early reverse engineering, no independent working driver yet
Rendering Physical GPU triangles, color/depth scenes and a restricted original GLXGears run No independent GPU submission or framebuffer rendering demonstrated
Shaders Restricted independent USSE/PDS work and NIR integration GLSL-to-UniFlex compiler interface and UniPatch research; final encoder remains unresolved
Kernel Experimental gma500/DRM, GEM and MMU work No qualified kernel integration
Tests Offline tests and documented Mini 12 physical qualifications Research notes and testing plan; hardware execution not demonstrated
Limitations General OpenGL, desktop acceleration and packaging remain incomplete Compiler, command submission and hardware execution remain research
Code and notes Mesa, kernel, documentation SGX544 project

SGX535 beta status — November 13, 2026

The accelerated desktop/Minecraft beta is not released yet. The target is 1280×800 X11 with measured responsiveness and a 50 FPS goal, plus Minecraft Beta 1.7.3 opening and rendering its menus on the SGX535. Normal application admission, DRI2 buffer exchange and system activation still need qualification.

Recent work includes physically checked CPU clears between restricted GPU draws, faster CPU-only X11 SHM publication, and locally tested persistent context/render/presentation integration. The 120-frame continuous callback result is a model test, not 120 new hardware frames. OpenGL 2.1 completeness and stable 50 FPS are not established.

See the beta checkpoint for confirmed results, limitations and remaining work. This update publishes documentation; the latest implementation and private test bundles are not included in it.

What actually worked on SGX535

Pipoca celebrating Pipoca: Those triangles really came from the GPU! The whole desktop isn't accelerated yet, though. One triangle at a time.

The Mini 12's SGX535 rev121 has rendered real triangles, and an OpenGL glDrawArrays call reached the GPU through the Gallium implementation. A qualified original glxgears run at 1280×800 completed 600 GPU submissions and averaged 16.1345 FPS across six measurement windows. The physical results describe the conditions; the GLXGears guide explains what is and isn't currently reproducible from a clone.

Later restricted scene tests covered color, depth and retirement at 640×640 and 1280×800. These results are exciting, but they do not establish OpenGL 2.1 conformance or an accelerated whole desktop. I keep CPU-only experiments and physical GPU evidence distinct because otherwise it gets very easy to celebrate the wrong triangle.

The SGX544 side

Pipoca reacting to a difficult problem Pipoca: The SGX544 library points to a GLSL compiler and UniFlex. Finding that signpost isn't the same as finding the road to a finished shader.

The SGX544 research follows the original GLES shader compilation path, including dynamic loading of libglslcompiler.so, GLSLCompileToUniflex and parts of UniPatch. I've tried to make it clear in the notes what we actually observed and what we think might be happening. There's no working SGX544 renderer yet, and I can't just assume SGX535 command encodings will work on it.

The starting point was an Android driver archive, including an x86 32-bit GLES library. Static analysis traced glCompileShader to a compiler callback and the lookup of GLSLCompileToUniflex; it also found UniPatch setup. The matching compiler wasn't in that archive. Where UniFlex becomes final USSE, and how this device submits work and manages GPU memory, still need answers. See the findings and their evidence limits.

Special thanks to contributor Incogninto for sharing the Android driver binaries that made this investigation possible. The research repository does not redistribute those proprietary libraries (just install device firmware)

How the pieces fit

Pipoca thinking Pipoca: Mesa takes the OpenGL calls, and Gallium gives the driver the draws and state. Then Gama has to convince the GPU to do something with them.

Mesa supplies the OpenGL frontend; Gallium provides an interface through which a driver receives draws, state and resources. The experimental SGX535 userspace builds hardware-facing state and shader programs, while the kernel side handles controlled access to memory and submission. GPU virtual addresses, ownership, synchronization and fences all matter here.

Pipoca explaining GPU synchronization Pipoca: Submitting work means asking the GPU to run it. Fences help us wait; retirement tells us when the work is finished and resources can be released safely. A command that looks good on the CPU hasn't drawn anything yet.

GEM manages graphics buffers on the kernel side, and the GPU MMU maps the addresses used by the GPU. The implementation has to keep those mappings and their owners valid while work is in flight; getting the pixels right once isn't enough if the next draw uses freed memory.

USSE is the shader instruction architecture being investigated. PDS (aka: hell) programs participate in preparing and delivering data and tasks to the GPU. GLSL and UniFlex belong to compiler paths studied in the original software; their exact relationship to final instructions must be established from evidence. These terms are not interchangeable, and neither are the two GPUs' encodings.

Where to look

For now, I'm keeping hardware-specific code separate. Both names start with SGX, but that's not enough reason to make them share a backend (correct)

Next steps and contributing

Pipoca running Pipoca: Next up: more draws, textures and shaders. And eventually a desktop with actual applications. No pressure, Gama.

For SGX535, the next steps are general Mesa draws, textures, shaders and resource lifetime, followed by broader OpenGL coverage, a responsive accelerated desktop and application testing. OpenGL ES 2.0, desktop OpenGL 2.1, video acceleration and an installable beta are goals, not finished features, enhanced sgx535 (GMA600) also in plans

For SGX544, I need to understand more of the compiler and hardware interfaces, then establish memory and submission contracts before attempting independent GPU execution and verified readback on physical hardware. The research roadmap has the details. No pretend triangles.

Pipoca waiting for contributors Have compatible hardware, references, test results or driver experience? Issues and contributions are welcome. Please include the device, kernel, commands and evidence, and tell us whether the result was CPU-only or ran on the GPU. Keep track of where material came from, and please don't contribute proprietary driver code or binaries unless you have the right to redistribute them.

Thanks to Simon Fenney, e1zo, Alex, Garnet, monocasa, nicman24, intelminer, Incogninto, everyone sharing evidence, and of course Pipoca. The original README has the full thanks and more of the story.

Pipoca resting The goal is serious. The documentation and commit messages doesn't always have to be

— Gama
Stone Badge