<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Low-level Hardware on Dev's Log</title><link>https://piot5.github.io/devs_log/tags/low-level-hardware/</link><description>Recent content in Low-level Hardware on Dev's Log</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 05 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://piot5.github.io/devs_log/tags/low-level-hardware/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter Two: Talking to the Silicon</title><link>https://piot5.github.io/devs_log/posts/chapter-two-talking-to-the-silicon/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://piot5.github.io/devs_log/posts/chapter-two-talking-to-the-silicon/</guid><description>Software-side display management (resolution and position) is only half the battle. To truly control a workspace, we need to talk to the monitor&amp;rsquo;s internal firmware. This is where DDC/CI (Display Data Channel Command Interface) comes into play.
1. The Physical Monitor Bridge In Windows, a &amp;ldquo;Logical Monitor&amp;rdquo; (GDI) is not the same as a &amp;ldquo;Physical Monitor&amp;rdquo; (The actual plastic and glass hardware). As seen in ddc.rs, we must first bridge this gap using the GetPhysicalMonitorsFromHMONITOR API.</description></item></channel></rss>