<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Qualcomm on Martin Cerven</title><link>https://martincerven.com/tags/qualcomm/</link><description>Recent content in Qualcomm on Martin Cerven</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 13 Oct 2026 12:53:57 +0200</lastBuildDate><atom:link href="https://martincerven.com/tags/qualcomm/index.xml" rel="self" type="application/rss+xml"/><item><title>Ventuno SSD install</title><link>https://martincerven.com/posts/ventuno_ssd_install/</link><pubDate>Tue, 13 Oct 2026 12:53:57 +0200</pubDate><guid>https://martincerven.com/posts/ventuno_ssd_install/</guid><description>&lt;h1 id="migrating-qualcomm-dragonwing--ventuno-q-to-nvme-safe-kernel-handoff-explained"&gt;Migrating Qualcomm Dragonwing / Ventuno Q to NVMe: Safe Kernel Handoff Explained&lt;/h1&gt;
&lt;p&gt;The Qualcomm Dragonwing (Arduino Ventuno Q) development platform is a capable ARM64 single-board computer, but its default 64 GB eMMC (typically ~55 GB usable) quickly becomes an I/O bottleneck under real-world workloads like compilation, Docker container orchestration, and on-device model inference.&lt;/p&gt;
&lt;p&gt;While adding an M.2 NVMe SSD offers a significant leap in throughput and capacity, &lt;strong&gt;naively cloning the drive as you would on x86 will fail or render the board unbootable&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>