Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://floss.social/@jbqueru" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jbqueru</span></a></span> OFC and in terms of <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RISCv</span></a> vs. <a href="https://infosec.space/tags/ARM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARM</span></a> it won't be competitive for quite some time as ARM includes a lot of <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proprietary</span></a> and <a href="https://infosec.space/tags/patented" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>patented</span></a> <a href="https://infosec.space/tags/PowerSaving" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PowerSaving</span></a> technologies that are just not available outside of said closed ISA.</p><ul><li>I do thus treat <a href="https://infosec.space/tags/ARM64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARM64</span></a> like <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a>: A <em>"black box"</em> that I cannot audit, verify or control beyond what it allows me to.</li></ul>