<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://donotsta.re/users/mwk" class="u-url mention">@<span>mwk</span></a></span> <span class="h-card" translate="no"><a href="https://oldbytes.space/@millihertz" class="u-url mention">@<span>millihertz</span></a></span> <span class="h-card" translate="no"><a href="https://tech.lgbt/@becomethewaifu" class="u-url mention">@<span>becomethewaifu</span></a></span> yeah but it doesnt matter if the instructions come from the FSM or spi flash or something, you still end up having to run some binary on the core at some point to provision it I think (unless you can coresight the entire setup i suppose? but that would just be nightmarishly painful i suspect lol)</p>

<p><span class="h-card" translate="no"><a href="https://ioc.exchange/@azonenberg" class="u-url mention">@<span>azonenberg</span></a></span> <span class="h-card" translate="no"><a href="https://donotsta.re/users/mwk" class="u-url mention">@<span>mwk</span></a></span> <span class="h-card" translate="no"><a href="https://oldbytes.space/@millihertz" class="u-url mention">@<span>millihertz</span></a></span> <span class="h-card" translate="no"><a href="https://tech.lgbt/@becomethewaifu" class="u-url mention">@<span>becomethewaifu</span></a></span> you could run the initial setup as instructions shifted into the ARM core in debug mode using an FSM :p</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@gamingonlinux" class="u-url mention">@<span>gamingonlinux</span></a></span> <br />Played this for quiet a while and it has been a great experience. However the native Linuxversion is crashing on startup if i run the game on my desktop.</p><p>This is caused by the KDE Plasma Wayland session. The games 7days to die has the same problem since it is based on Unity3D as well.</p><p>As a workaround i have to run the game with OpenGL instead of Vulkan.</p>

<p>Getting awfully fed up with all the stupid comparisons between SpaceX and NASA.</p><p>NASA pulled one silly political stunt in the 1960s then has done nearly nothing useful, in comparison, since as far as developing launch methods are concerned.</p><p>SpaceX has at least got re-usable orbital boosters working reasonably safely and cheaply - something nobody else has done. (No, the Shuttle was neither safe nor cheap. An approximately 1 in 70 chance a launch is going to kill the crew is less than acceptable. Maybe a 1 in 70 chance of a launch failure with, say, a 1 in 30 chance that the launch escape system fails is closer.)</p><p>Now SpaceX are having lots of troubles with Starship. Maybe the whole concept is fundamentally flawed or maybe they&#39;re just pushing a bit too hard and quality control has gone out the nozzle. I suspect quite a few people within the company have a good idea of which (or both) of these applies but maybe they&#39;re not up for telling the shithead in chief. From the outside it&#39;s hard to tell.</p><p>These are both problems NASA has had. E.g., quality control before the AS 204 fire or the under-trained &amp; overworked trajectory team for the Mars Climate Orbiter which failed to pick up on the famous SI/US customary units problem or the fundamental mess which was the Shuttle program which should have been canned well before its first launch.</p><p>(The lack of a credible crew escape system on both the Shuttle and on Starship is one commonality that bothers me. At the very least SpaceX needs to get rid of the hot-staging requirement, but I suspect they know that.)</p><p>SpaceX failed to make a controlled re-entry of one second stage resulting in a uncontrolled re-entry over Poland. Oops, shouldn&#39;t have happened but the outrage is interesting to compare with that of China leaving some 300 second stages (IIRC) in orbit which will eventually make uncontrolled re-entries.</p><p>Generally, I think SpaceX has been pushing too hard with Starship but that&#39;s fairly easy to say in retrospect. It&#39;s at least worth a try compared with the almost complete lack of progress though out the rest of the space industry.</p>

<p><span class="h-card" translate="no"><a href="https://donotsta.re/users/mwk" class="u-url mention">@<span>mwk</span></a></span> <span class="h-card" translate="no"><a href="https://oldbytes.space/@millihertz" class="u-url mention">@<span>millihertz</span></a></span> <span class="h-card" translate="no"><a href="https://tech.lgbt/@becomethewaifu" class="u-url mention">@<span>becomethewaifu</span></a></span> This is the closest you can get (to my knowledge) to a true antikernel system with zero privileged code (i.e. the initial setup is done by an rtl state machine) with currently extant silicon, unless you use a softcore CPU which is sloooow</p>

<p>I finally wrote an article about the last <a href="https://mastodon.social/tags/MirageOS" class="mention hashtag" rel="tag">#<span>MirageOS</span></a> retreat (<a href="https://mastodon.social/tags/OCaml" class="mention hashtag" rel="tag">#<span>OCaml</span></a>). It&#39;s available here: <a href="https://blog.osau.re/articles/last_mirageos_retreat.html" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">blog.osau.re/articles/last_mir</span><span class="invisible">ageos_retreat.html</span></a> Enjoy reading!</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.gamedev.place/@lritter" class="u-url mention">@<span>lritter</span></a></span> obviously if you&#39;re a witch/wizard you don&#39;t need a magic button to do magic</p>

<p>ironic that we live in a time where everybody owns a computer with a mandatory button that spawns a supposed &quot;magical genie&quot;, except for computer witches &amp; wizards who specifically do *not* have such a button anywhere, nor do they wish to have one</p>

<p><span class="h-card" translate="no"><a href="https://donotsta.re/users/mwk" class="u-url mention">@<span>mwk</span></a></span> <span class="h-card" translate="no"><a href="https://oldbytes.space/@millihertz" class="u-url mention">@<span>millihertz</span></a></span> <span class="h-card" translate="no"><a href="https://tech.lgbt/@becomethewaifu" class="u-url mention">@<span>becomethewaifu</span></a></span> this is where we take advantage of the fact that the the PL has an axi port that allows fabric to talk to hard IP on the PS side.</p><p>and I *think* (if this doesn&#39;t work, it&#39;s 100% definitely doable over EMIO JTAG but that would make it even more cursed) you can access CoreSight APB registers on the PS side from PL this way.</p><p>So you make an RTL context switcher module that periodically halts the A9, serializes its registers out to block RAM, loads a new context, loads a new page table, flushes caches etc as needed, then resumes execution.</p><p>Boom, hardware threading with no kernel mode software.</p>