Kevin Karhan :verified:<p>Thanks to <span class="h-card" translate="no"><a href="https://mastodon.social/@geerlingguy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>geerlingguy</span></a></span> for <a href="https://www.youtube.com/watch?v=GKGtRrElu30&t=290" rel="nofollow noopener" target="_blank">addressing the elephant in the room.</a></p><p><span class="h-card" translate="no"><a href="https://mastodon.social/@RaspberryPi" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>RaspberryPi</span></a></span> dominates the <a href="https://infosec.space/tags/SBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SBC</span></a> market because they know how to write <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>documentation</span></a> and build <a href="https://infosec.space/tags/drivers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>drivers</span></a> that get accepted into <a href="https://infosec.space/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mainline</span></a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> kernel.</p><ul><li>The best specs and hardware is useless if it needs intimate knowledge on how to roll one's own kernel. And oftentimes one doesn't even get proper drivers and reproduceable build instructions but just some <em>"vomited" out</em> bootable images to <code>dd</code> onto a microSD!</li></ul><p>That's why my <a href="https://infosec.space/tags/BananPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BananPi</span></a> Zero M2 is still unused to this day: It's way too inconvenient and whilst I <a href="https://github.com/OS-1337/OS1337/blob/c4a19af5a62d7afbb80dfc416773a92074e6cc32/docu/ideas/architectures.tsv#L10" rel="nofollow noopener" target="_blank">do want to support it someday</a>, it's just not a good start when the 1st <a href="https://infosec.space/tags/RasperryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RasperryPi</span></a>'s documentation to this day is still the bare minimum and vendors can't be assed to do that.</p><ul><li>The only reason <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a>-based <a href="https://infosec.space/tags/SBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SBC</span></a>|s don't have the same issues as <a href="https://infosec.space/tags/arm64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>arm64</span></a> is because <a href="https://infosec.space/tags/BIOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BIOS</span></a> & <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UEFI</span></a>-boot alongside the way <a href="https://infosec.space/tags/hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hardware</span></a> is initialized make it trivial to make it <em>"go brrrr..."</em></li></ul>