<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hardware-Abstraction on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/hardware-abstraction/</link>
    <description>Recent content in Hardware-Abstraction on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 15 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/hardware-abstraction/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rust on Microcontrollers in 2026: embedded-hal vs esp-hal vs rp-hal Compared</title>
      <link>https://www.pistack.xyz/posts/2026-10-15-rust-embedded-hal-esp-hal-rp-hal-comparison/</link>
      <pubDate>Thu, 15 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-15-rust-embedded-hal-esp-hal-rp-hal-comparison/</guid>
      <description>&lt;p&gt;Embedded Rust stopped being an experiment the moment its interfaces stabilised. In 2026 the practical question is no longer &amp;ldquo;can I write firmware in Rust?&amp;rdquo; but &amp;ldquo;which HAL do I write my driver against, and what breaks when the silicon vendor changes it?&amp;rdquo; The three repositories that answer that question — &lt;code&gt;embedded-hal&lt;/code&gt;, &lt;code&gt;esp-hal&lt;/code&gt; and &lt;code&gt;rp-hal&lt;/code&gt; — sit at different layers of the same stack, which is why comparing them as rivals misses the point and comparing them as collaborators is what actually ships products.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
