Many of these attacks target the bios.

BIOS is usually a SPI chip. It'd make sense to perhaps tie the write enable line so that it cannot be written to, unless jumpered.

It used to be a thing motherboards did. A BIOS flash enable jumper.

They kept the CMOS reset one, but for some reason got rid of the flash write enable.

Please elaborate.

To understand the age verification push, got to follow the incentives[0].

0. https://www.youtube.com/watch?v=RfukJ6uVHXs

Software-only fantasy consoles are an interesting concept, covered by a sister comment.

There are also hardware-based efforts, like BoxLambda[0], Agon[1], MEGA65[2], Uzebox[3], F256[4].

0. https://epsilon537.github.io/boxlambda/

1. https://www.thebyteattic.com/p/agon.html

2. https://mega65.org/

3. https://uzebox.org/

4. https://wildbitscomputing.com/

Finally, the ESP32-S3 has a true RISC-V successor.

I stopped using GNOME at that point, over this.

>Do note that there's a ton of media that is not very available via sailing the seas.

This is an argument for preservation.

i.e. everything should be available via sailing the seas. If something isn't, and you know where to obtain it, do your part.

Many films and records have been lost because nobody cared to do it.

The article spells RISC-V incorrectly as "Risk V" in some sentences.

This does not feel like the sort of error somebody going so far as to implement this would make.

Gut feeling is not good. Unfortunate.

I just like the game Risk. It boots!

Please follow the guidelines[0] going forward.

0. https://riscv.org/about/brand-guidelines/

OK fixed! As you clearly know this space well, what do think would make this project better? I was thinking I wanted to see a heatmap of memory access (pages?), and more detailed explaination of the opcodes, but getting the thing working took quite a while so I got a bit tired and stopped at the booting milestone, but I like the project a lot and now it is in a notebook I can basically probe any part of the system with dataviz tools to make it more tangible. Do you have anything you think would be helpful or cool for learners that you have not seen before in an emulator?

This is going to be very person by person.

e.g. I'd love to see cycles spent in each mode (machine/supervisor/user). Also how much idle (wfi).

I added a viz for that! Its cool! You can see the transition to user mode https://bsky.app/profile/larkworthy.bsky.social/post/3mjcpky...

I love it.

In the graph, does it show the highest level of execution within the sample interval, or the current one at sample time?

It counts every instruction and blends the colours for the three active modes. Then the height represents idleness. So it's a pretty high resolution measure!

GNU started with frustration over a cursed printer and a cursed proprietary driver for it.

2026, we are still dealing with this kinda thing.

The full-story is insane[0].

It is good that seL4 is now its own organization, fully independent. A tragedy that it was hampered by CSIRO for so many years.

0. https://microkerneldude.org/2022/02/17/a-story-of-betrayal-c...