they extended one set of assembly instructions with a bit of another. instruction sets are determined by the hardware and are called the architecture. RISCV is an extensible architecture meaning you can add in additional instructions without breaking compatibility with programs targeting the architecture.
I know as much as that and that intel has like a giant black box and gatekeeps giving people instructions (and prevents people from being able to fix their fuck ups, backdoors etc)
the x86 instruction set is public. implementing it breaks copyright law, if you aren't AMD or Intel. it has to be public or compilers/interpreters/assembly code couldn't exist.
no, it's not a hypervisor. it's a a bit of hardware with access to the network stack that allows firmware updates and monitoring (in the "is the computer on/overheating" sense - it gives access to the low level sensors). it's supposed to be disabled if you don't pay money to turn it on (ie enterprise customers) but there's no way to really know because the motherboard chipsets don't expose access to it. it /shouldn't/ be able to function because the motherboard needs to cooperate in order to make it function but we don't really know what the chipsets/bios do/don't implement. so it's a theoretical attack vector by the USG.
the AMD version of the same is much more limited and doesn't even exist on consumer chips, if you don't buy workstation or server hardware. and if you do buy those, the motherboard exposes the control functions with documentation on which network interfaces it's able to use. it's also frequently open spec these days so you can run your own FOSS management firmware. very handy if you e.g. need to access the bios when the video card won't turn on or your overclock is busto.
Intel is basically just stupid and too lazy to only include the extra silicon in chips where it's actually possible to use it. and too greedy to open up the specs to make it possible to control it yourself on chips where it can be used. don't give Intel money. AMD appears to be all in on open source specs and actively contributes to the open firmware/open source bios initiatives so it's likely that it will become standard on their hardware over the next 5ish years (their code sucks ass so it's very hard for projects to merge/debug quickly so it's a slow effort lol).
Fascinating. Anybody who just wants to know why they called it "RiscV-ish," apparently there's some MIPS thrown in as well.
what does that mean i only understand coding horrible applications, websites, and minetest and minecraft
they extended one set of assembly instructions with a bit of another. instruction sets are determined by the hardware and are called the architecture. RISCV is an extensible architecture meaning you can add in additional instructions without breaking compatibility with programs targeting the architecture.
I know as much as that and that intel has like a giant black box and gatekeeps giving people instructions (and prevents people from being able to fix their fuck ups, backdoors etc)
the x86 instruction set is public. implementing it breaks copyright law, if you aren't AMD or Intel. it has to be public or compilers/interpreters/assembly code couldn't exist.
isn't the main backdoor now like a separate chip that acts as a sort of hypervisor thingy?
no, it's not a hypervisor. it's a a bit of hardware with access to the network stack that allows firmware updates and monitoring (in the "is the computer on/overheating" sense - it gives access to the low level sensors). it's supposed to be disabled if you don't pay money to turn it on (ie enterprise customers) but there's no way to really know because the motherboard chipsets don't expose access to it. it /shouldn't/ be able to function because the motherboard needs to cooperate in order to make it function but we don't really know what the chipsets/bios do/don't implement. so it's a theoretical attack vector by the USG.
the AMD version of the same is much more limited and doesn't even exist on consumer chips, if you don't buy workstation or server hardware. and if you do buy those, the motherboard exposes the control functions with documentation on which network interfaces it's able to use. it's also frequently open spec these days so you can run your own FOSS management firmware. very handy if you e.g. need to access the bios when the video card won't turn on or your overclock is busto.
Intel is basically just stupid and too lazy to only include the extra silicon in chips where it's actually possible to use it. and too greedy to open up the specs to make it possible to control it yourself on chips where it can be used. don't give Intel money. AMD appears to be all in on open source specs and actively contributes to the open firmware/open source bios initiatives so it's likely that it will become standard on their hardware over the next 5ish years (their code sucks ass so it's very hard for projects to merge/debug quickly so it's a slow effort lol).
I guess I wasn't thinking about the bottom line enough, maybe a remnant of my pure FOSS ideology devoid of political consciousness
Thanks for clarifying that, it sounded insanely impractical