<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jetson on ferkakta.dev</title><link>https://ferkakta.dev/tags/jetson/</link><description>Recent content in Jetson on ferkakta.dev</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright fizz.</copyright><lastBuildDate>Fri, 20 Feb 2026 11:00:00 -0600</lastBuildDate><atom:link href="https://ferkakta.dev/tags/jetson/index.xml" rel="self" type="application/rss+xml"/><item><title>I assumed model conversion worked like compilation. It doesn't.</title><link>https://ferkakta.dev/tensorrt-architecture-boundary-ansible-pipeline/</link><pubDate>Fri, 20 Feb 2026 11:00:00 -0600</pubDate><guid>https://ferkakta.dev/tensorrt-architecture-boundary-ansible-pipeline/</guid><description>&lt;p&gt;I sit at an M3 Max MacBook Pro that runs x86 Docker images through Rosetta. I&amp;rsquo;ve spent my career watching architecture boundaries dissolve.&lt;/p&gt;
&lt;p&gt;So when the ML engineer told me the TensorRT model conversion &lt;em&gt;had&lt;/em&gt; to run on the Jetson — the actual ARM edge device, not the x86 GPU server sitting next to it — I assumed it was cargo cult.&lt;/p&gt;
&lt;p&gt;It wasn&amp;rsquo;t.&lt;/p&gt;
&lt;h2 id="the-pipeline"&gt;The pipeline&lt;/h2&gt;
&lt;p&gt;We were shipping an RT-DETR object detection model to NVIDIA Jetson Orin devices on drones.&lt;/p&gt;</description></item></channel></rss>