<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Development log · poulsback</title>
    <link>https://poulsback.in/blog/</link>
    <description>Notes from bringing SGX535 back to life: driver design, real hardware and the measurements behind each step.</description>
    <language>en-us</language>
    <lastBuildDate>Mon, 09 Nov 2026 20:55:00 &#43;0900</lastBuildDate>
    <atom:link href="https://poulsback.in/blog/index.xml" rel="self" type="application/rss+xml" />
    
    
    
    <item>
      <title>Poulsback needs you</title>
      <link>https://poulsback.in/blog/poulsback-needs-you/</link>
      <guid isPermaLink="true">https://poulsback.in/blog/poulsback-needs-you/</guid>
      <pubDate>Mon, 09 Nov 2026 20:55:00 &#43;0900</pubDate>
      <description>We develop poulsback on two machines, and there were dozens of GMA 500 designs. A new live USB stick collects a device report in one boot, with nothing to type and nothing installed. Here is how to make one and send it.</description>
    </item>
    
    
    
    <item>
      <title>Same GPU, a 2 GHz Atom</title>
      <link>https://poulsback.in/blog/same-gpu-a-two-ghz-atom/</link>
      <guid isPermaLink="true">https://poulsback.in/blog/same-gpu-a-two-ghz-atom/</guid>
      <pubDate>Sun, 08 Nov 2026 16:35:00 &#43;0900</pubDate>
      <description>A 5.6-inch Fujitsu LOOX U/C50N pairs the same Poulsbo SGX535 with a 2.00 GHz Atom Z550. Separating the display aperture from the SGX 2D window brought it up cleanly, and matched benchmarks show where a faster CPU moves the frame rate.</description>
    </item>
    
    
    
    <item>
      <title>Teaching SGX535 to build its own mipmaps</title>
      <link>https://poulsback.in/blog/teaching-sgx535-to-build-its-own-mipmaps/</link>
      <guid isPermaLink="true">https://poulsback.in/blog/teaching-sgx535-to-build-its-own-mipmaps/</guid>
      <pubDate>Thu, 05 Nov 2026 10:15:02 &#43;0900</pubDate>
      <description>The smallest mip holds four bytes of pixel data. Reaching it on SGX535 meant understanding tile writes, ordering six GPU passes and checking application draw state and queries.</description>
    </item>
    
    
    
    <item>
      <title>A tablet, a familiar core, a different machine</title>
      <link>https://poulsback.in/blog/a-tablet-a-familiar-core-a-different-machine/</link>
      <guid isPermaLink="true">https://poulsback.in/blog/a-tablet-a-familiar-core-a-different-machine/</guid>
      <pubDate>Wed, 04 Nov 2026 11:30:07 &#43;0900</pubDate>
      <description>A working Linux console, a deliberate driver refusal and an unexpected x87 test failure: the Q550 turns a second machine into a useful set of questions.</description>
    </item>
    
    
    
    <item>
      <title>A cube that can measure the driver</title>
      <link>https://poulsback.in/blog/a-cube-that-can-measure-the-driver/</link>
      <guid isPermaLink="true">https://poulsback.in/blog/a-cube-that-can-measure-the-driver/</guid>
      <pubDate>Tue, 03 Nov 2026 14:33:00 &#43;0900</pubDate>
      <description>A benchmark we can understand gives the neon cube another job: connect what the GPU draws with the time and CPU work needed to draw it.</description>
    </item>
    
    
    
    <item>
      <title>When the gears finally turned</title>
      <link>https://poulsback.in/blog/when-the-gears-finally-turned/</link>
      <guid isPermaLink="true">https://poulsback.in/blog/when-the-gears-finally-turned/</guid>
      <pubDate>Tue, 03 Nov 2026 14:33:00 &#43;0900</pubDate>
      <description>Getting glxgears onto the Dell’s panel joined Mesa, the kernel driver and X11. Moving its vertex work onto SGX535 was a later milestone.</description>
    </item>
    
    
    
    <item>
      <title>From the first cube to the logo</title>
      <link>https://poulsback.in/blog/from-the-first-cube-to-the-logo/</link>
      <guid isPermaLink="true">https://poulsback.in/blog/from-the-first-cube-to-the-logo/</guid>
      <pubDate>Tue, 03 Nov 2026 14:33:00 &#43;0900</pubDate>
      <description>The first successful cube gave poulsback a recognisable shape. It also taught us to ask exactly which parts of a rendered frame were working.</description>
    </item>
    
    
    
    <item>
      <title>A second life for a ¥500 Dell</title>
      <link>https://poulsback.in/blog/a-second-life-for-a-five-hundred-yen-dell/</link>
      <guid isPermaLink="true">https://poulsback.in/blog/a-second-life-for-a-five-hundred-yen-dell/</guid>
      <pubDate>Tue, 03 Nov 2026 14:33:00 &#43;0900</pubDate>
      <description>Around July, a non-working Dell from HARD OFF in Japan became the next poulsback machine. Repairing it gave the project a reference it could keep testing.</description>
    </item>
    
    
    
    <item>
      <title>How poulsback began</title>
      <link>https://poulsback.in/blog/how-poulsback-began/</link>
      <guid isPermaLink="true">https://poulsback.in/blog/how-poulsback-began/</guid>
      <pubDate>Tue, 03 Nov 2026 14:33:00 &#43;0900</pubDate>
      <description>I started on February 1, 2026, because I wanted Linux to work better on my VAIO P. A broken motherboard and a ¥500 Dell changed the plan.</description>
    </item>
    
    
    
    <item>
      <title>Giving the GPU room to work</title>
      <link>https://poulsback.in/blog/giving-the-gpu-room-to-work/</link>
      <guid isPermaLink="true">https://poulsback.in/blog/giving-the-gpu-room-to-work/</guid>
      <pubDate>Tue, 03 Nov 2026 00:00:00 &#43;0900</pubDate>
      <description>Moving vertex work onto SGX535 was the first step. A frame trace showed how much time the GPU still spent waiting for its own engines.</description>
    </item>
    
  </channel>
</rss>
