I'*ve been baking shader artifacts to programm a GPU that is basically a Frame like Calculator
its actually way closer to a CPU then i'd thought
the troughput monster
its like start the kernel and execution all over, atleast if done right. even the media part,
achieve the first mp4 frame seems to be only 1/3 of the full playback ways.
update 13.04
milestone — H.264 decode on bare-metal Intel Xe-LP VCS0, end to end: MP4 fetch → Annex-B → MFX batch → PPGTT → Execlists submit → Y-tile NV12 output → OWord-column detile → RGB present. All on your own kernel with no OS driver stack.
The OWord-column Y-tile fix was the last piece. Ready to tackle multi-frame decode (all 1802 samples) whenever you want to proceed.
Restore Checkpoint
i know thats actually big
It really is. Bare-metal GPU video decode with no Linux, no Mesa, no firmware blobs — just your own kernel talking directly to the MFX engine over Execlists. That's a very short list of people who've done that.
I'm planning a CryptoWallet but dont know jet what TokenStandards (The Ethereum Proposals) im going to target.
Plus there is an Eyetracker that will be dedicated to the HW Cursor Plane (before, i resisted that)
Now im preparing a Demo for that aswell. Have fun and good luck with all Your ideas!
Smallish Update 03.04.26
Current ISO is headless Bare-metal, however all Services and Shell outside UI are available in latest ISO.
Update 31.03.26
Dear Everyone,
I wrote 100% Rust-Based Operating System during the past 6 winter months, after I finished my thesis in theoretical computer science.
TRUE OS is based on nothing, besides the Boot loader that it includes, to bootstrap it. Everything about it comes from modern Rust Crates, custom Implementations and the most recent stable crate Io releases. Every week i upgrade all dependency via cargo. I'm sorry but i removed the VGA path and the PS2 for mouse. We have Accelerated Graphics and USB Hid Interfaces - that means its already tablets, mouse, keyboard via USB anyway. The best part about it is, there is no real legacy or backwards dependency as i handcrafted every integration, architectural detail and structure: to it, on a Huge Aquarelle A1 Block - before i got to work.
The operating system I built, just using Rust, targets Intel X86 and runs currently fine with some emulators (VMWare/VBox/Qemu…) and, of course, bare metal on any modern Intel chipset + CPU. I, personally, use an i7 14k but T version, running on an LED 120W power supply,
and an i9 13k, but that powerhouse has a full 1000W in a GPU config..
Install Guide
Install Emulator and Zip
sudo apt install qemu-system ovmf p7zip
Download and Unpack
wget https://trueos.eu/TrueOS.7z && 7z x TrueOS.7z -o.
That should print an Everything is Ok.
Run TRUE OS
qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd
-enable-kvm -cpu host,host-phys-bits=true \
-display gtk,gl=on -device virtio-gpu-gl-pci,xres=1280,yres=800 \
-smp cores=3 \
-m 500M \
-cdrom trueos.iso \
Good to know
Adjust your Screen Size 1280,800 The CPU cores for the VM cores = 3, and the amount of RAM the VM gets is -m 500M as you like. Some services are spawned on different APs, and right now, hand in at least 3 cores with at least 500 MB RAM. Later, there will be no restrictions to running just 1 core, but currently, the recommended minimum CPU cores is 3. Regarding the OVMF and OpenGL for your system, better ask AI, and you are welcome to provide feedback on any problems you may have encountered.
User Guide
Shell
Use Concept
F1–F5 to Select the Mode
Good luck and have fun finding out all things ![]()
The Problem (Choice): The machines discovered that humans would only accept the Matrix if they had a choice to leave it, even at a subconscious level.
Matrix The Operator § (§ = The One)
How to actually use the CMD F4 mode of the shell of TRUE OS
A. § is Shells Headjack
B. §xzy is your Hard Lines—Constructs a Shell Matrix or Swap to it aka The Choice.
C. §xzy§ frees the slot aka The Reset.
D. § is colored so you always know about the loading program. (Running Jobs)
In TRUE OS your shell is connected to numerous backends, and you can swap § to any shell or spawn a new § one via § The Operator.
Developer Guide
By far the easiest is to just write it as a website. You can use HTML and CSS. BUT JS is not yet recommended.
Start your app from the file system and load it via “surf file” or pass direct <html> into the surf command via “surf html”.
Or you actually host it someplace and “surf URL” to it. Keep in mind that the web browser of TrueOS is full-featured and by far the most stress-free and recommended way for any app. The browser is a monster in terms of features, and it is the center of half of what TrueOS is actually doing for you.
How to Write a Rust Native App Using TRUEOS-Blueprints Toolkit
This section is meant for the people who want to access every feature and fully dive into the world of TRUE OS.
Shell Native Rust App
As an example, a command called echo2 or how I wrote Shell TETRIS using the Shell API.
But for now, create a main.rs and drop in the hello world.
Building the app is as simple as “cargo bp” That's all there is to it.
You can get the Blueprint Tool that does packing for you at the public github.
The readme contains brief instructions, but after the cargo bp, you only need to upload and run your object/blueprint.
GitHub - t4ce/TRUEOS-Blueprints · GitHub
“Use trueos-pack to build a blueprint (.bp); that is a packaged relocatable program layout that TrueOS realizes into runnable code at load time.”
GUI App
A rich UI desktop like Office Application.
Here we can learn about the native UI elements of TRUE OS. If you are familiar with HTML, CSS, and JavaScript, you are perfectly at home here. I provide a very nice toolset for your Web-like app. They run native to TRUE OS.
GPU GUI App
Use the FPS-optimized Graphics Render App Template that uses GPU hardware and a custom GFX backend for awesome graphics. (Shaders + Geometry and Meshed Full RGBA Texture Upload to GPU)
The systems can be used together to create Multi-Feature Applications.
I promise that I will not let you down; I view it as the single most important reason to have TRUE OS: that is, to give you the hardware that you paid for. Choose the TRUE OS V Layer and SYS and profit from future updates.
Some of my claims were more to be understood as a roadmap and current programming frontier. As one of my friends suggested, i will do a more honest and less "diy" update, because people deserve the truth!
██████████████████████████████████████████████████████████████████████
██░ ░░ ░░░ ░░░░ ░░ ░░░░░░░░░ ░░░░ ░░██
██▒▒▒▒ ▒▒▒▒▒ ▒▒▒▒ ▒▒ ▒▒▒▒ ▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒ ▒▒ ▒▒▒▒▒▒▒██
██▓▓▓▓ ▓▓▓▓▓ ▓▓▓ ▓▓▓▓ ▓▓ ▓▓▓▓▓▓▓▓▓▓ ▓▓▓▓ ▓▓▓ ▓▓██
██████ █████ ███ ███ ████ ██ ██████████████ ████ ████████ ███
██████ █████ ████ ███ ███ █████████ ████ ████
██████████████████████████████████████████████████████████████████████
Rust-based 64-bit paged X84 bare-metal OS targeted @ Intel & GOWIN


