> anyone else is able to start supplying the same thing
Not if there's a custom extension.
Additionally, "supplying the same thing" is equivalent of asking someone to write a perfect drop-in replacement for the Linux kernel, to connect to your example.
It's not that simple, by far.
> It still costs resources to do it, but there is no artificial block because of patents.
Actually, no. CPU IP can be patented and no, RISC-V does not prohibit it.
You are asking for someone to design a new CPU, while also supporting whatever custom extension already exists, while also navigating the huge patent minefield.
I would not be so eager to advertize my ignorance of such simple language devices. Are you sure you want to play that stupid? It's not usually the best way to show how on top of things you are and how much your opinions matter and how seriously everyone else should take your reasoning and arguments.
Anyway...
Patended customizations are irrelevant.
If the open part of a risc-v cpu or platform may or may not be the entire end-user product, so what?
So there is one open brick and a useful product needs 10 bricks and some of those other bricks don't exist in an open form yet. So what? It in no way invalidates the value of attaining any given one of the bricks.
Sooner or later, if not already, now that some parts exist, someone will tackle the next part and the next part.
We all know this already, thanks...
> anyone else is able to start supplying the same thing
Not if there's a custom extension.
Additionally, "supplying the same thing" is equivalent of asking someone to write a perfect drop-in replacement for the Linux kernel, to connect to your example.
It's not that simple, by far.
> It still costs resources to do it, but there is no artificial block because of patents.
Actually, no. CPU IP can be patented and no, RISC-V does not prohibit it.
You are asking for someone to design a new CPU, while also supporting whatever custom extension already exists, while also navigating the huge patent minefield.