#PinePhone's A64 Display Engine is now supported in Apache #NuttX Kernel ... How will it be called by our PinePhone Display Driver? All shall be explained in this article
#PinePhone's A64 Display Engine 1️⃣ Reads pixels from Multiple Framebuffers 2️⃣ Blends the pixels into a Single Image 3️⃣ Pushes the image to the LCD Display
Article: https://lupyuen.github.io/articles/de3?2#allwinner-a64-display-engine
Let's render 3 Framebuffers with #PinePhone's A64 Display Engine
Article: https://lupyuen.github.io/articles/de3?3#ui-channels
Here's how we define the #NuttX Framebuffers for #PinePhone A64 Display Engine
Article: https://lupyuen.github.io/articles/de3?4#nuttx-framebuffer
Let's draw a Test Pattern in our #NuttX Framebuffers for #PinePhone
Article: https://lupyuen.github.io/articles/de3?6#test-pattern
#PinePhone won't render pixels correctly unless we use Arm64 DMB Barrier ... Not sure why 🤔
Article: https://lupyuen.github.io/articles/de3?6#test-pattern
Our #NuttX Display Driver for #PinePhone is nearly complete! Just a few bits of Zig code to port over
Article: https://lupyuen.github.io/articles/de3?7#complete-display-driver
Up Next: #NuttX Drivers for #PinePhone's LCD Panel and Power Mgmt IC
Article: https://lupyuen.github.io/articles/de3?8#upcoming-drivers
Here's why #NuttX Drivers should call up_mdelay() instead of sleep() ... And #PinePhone is the fastest NuttX Device ever!
Article: https://lupyuen.github.io/articles/de3?8#appendix-calibrate-nuttx-delay
Apache #NuttX Kernel now supports Allwinner A64 Display Engine! Here's how we call it to render graphics on #PinePhone's LCD Display
@lupyuen Is NuttX even any good?
@kreyren We're still doing the initial port of NuttX to PinePhone ... Lots more work to be done
Rendering Framebuffers with the #NuttX Driver for A64 Display Engine on #PinePhone
Article: https://lupyuen.github.io/articles/de3?5#render-framebuffers