Do you suggest any such books?

>Attribution-NonCommercial-NoDerivative

i.e. not Open Source. What a shame.

It is a commercial hardware, and author wants to get some money back from it. Nothing wrong or shameful about this, as long as this is clearly stated from day 1 (and it is).

At least they provide full schematics here, which is better than many other products do.

Sure. Issue is particularly with the name, "PD-64", which suggests Public Domain (it's far from!). It may well be unintended.

C64 PSUs are C64 killers, which is why I feel strongly there should be as little as possible in terms of barriers to getting a replacement.

Yes, it is far better than the alternative (no schematics), as at least we can learn how it works without reverse-engineering, as well as build our own legally (just not sell).

>soldered it into a socket

You... what?

Why would you ever solder a chip into a socket, rather than just insert?

(they clipped the original chip, instead of desoldering it. The socket is then inserted into another socket on the board. Workable trick but... why, just why.)

– ? –

In Europe, this sort of thing is routine and doesn't make the news.

They got rid of anonymity, which makes this a trivial problem: Law enforcement takes care of it.

Now, whether giving up anonymity was worth it is a separate issue.

Not RISC-V? Uncool.

The low powered MCU (Raspberry Pi RP2350B) has RISC-V:

Dual ARM Cortex-M33 @ 150 MHz + Dual RISC-V Hazard3 @ 150 MHz

Good riddance.

>it's literally every DOS game ever

It is large, but seriously? I do not think it is complete, far from.

The microkernel-based systems (LionsOS, Genode and so on) already have sane interfaces.

What is needed in that regard is just to port more drivers over.