There is no freedom and I have no solution to this problem. What we can even do?
>all hardware has chips with proprietary firmware
>"Open Source" and "Free Software" Nvidia drivers needs proprietary firmware
>"Open Source" and "Free Software" AMD drivers needs proprietary firmware
>all the "secure" and "privacy" coreboot forks are actually just proprietary binaries you flash
>"open source" coreboot compiled by user and flashed by user has proprietary blobs
>"libre" libreboot isn't libre and has proprietary blobs
>even the canoeboot meme isn't libre and has proprietary blobs
>even the GNU Boot needs chips that have proprietary blobs
>you can't use WiFi without chips that have proprietary blobs
>you can't use any ethernet/RJ45 based networking IN ANY WAY without chips that have proprietary blobs
>even your only "safe" option with a fucking "Respects Your Freedom Certification, RYF" needs chips that have proprietary blobs and that certification includes exceptions that allow those chips with proprietary firmware to be certified
>it is illegal and apparently impossible to use GSM networking or any modem ever without chips that have proprietary blobs
>even if you would sit on the floor of your 100% empty home without any device ever, these days you would still have +10 devices with chips that have proprietary blobs, running 24/7 near you

There is nothing you can do. Your Thinkpad X200 with GNU Boot still is proprietary, your hardware that "Respects Your Freedom" still is proprietary, you can't connect to the internet via WiFi, not with a ethernet cable, not via any networking protocol or hardware in any way ever without proprietary firmware.

Certain binary blobs are necessary and can be audited by people who know assembly, retard-kun

>>106127574 (OP)
RISC-V laptops coming in a couple of weeks.

>>106127603 >>106127804
RISC-V laptops won't achieve freedom. They'll contain at least one proprietary firmware chip (e.g., Ethernet/Wi-Fi controllers). Without free firmware replacements, even basic functions like internet access force users to run non-free code. Until all chips allow auditable/replaceable firmware, they're merely repeating the flaws of proprietary hardware.

>>106127904
They could by simply designing all of these things from scratch and compromise on video card competitivity for the sake of getting the whole thing out within a reasonable deadline. I'd buy it.

>uuh bu buu uhh there is no freedom and I have no solution to this problem waaaa
There will never be freedom for you as long as you expect it to be handed to you. You will never experience true freedom until you fight for it and take it without asking for permission. Until then, enjoy slavery nigger.

God I hate cattle.

>>106128013
It would cost over $10 million to develop per chip, IEEE standards are paywalled, requires a custom ASIC or FPGA-based design with open-source HDL, regulatory certifications (FCC, CE, etc.) cost $200k+ per region and require proprietary test tools and one slow ethernet card would cost something like $200k and nobody would buy it anyway.

>>106128043
Oh you clearly have all the freedom. Tell me what phone, wired/wireless card, computer, router, monitors, ISP etc. you use at the moment to post here on our FBI honeypot website? Or are you just crying without freedom because you feel bad and because you are really emotional?

>>106128043
You have never done anything to solve this issue in your whole life. You are just a butthurt crying child. You can't even argue and instead run away like a little shit.

>>106128238
Then it comes down to who's footing the bill here. You get somebody like Musk involved and it's gonna get done and it will be affordable.

>>106127574 (OP)
>"oh let's use my Free Software X200 Thinkpad with Trisquel to browse web with IceCat and all the privacy extensions"
>keyboard microcontroller chip with proprietary firmware processes key press signals
>keyboard USB controller chip with non-free firmware transmits data via USB protocol
>"b-b-but I have GNU Boot and my other pc has Libreboot a-and..."
>motherboard UEFI/BIOS chip with proprietary firmware handles USB input initialization
>motherboard chipset's I/O controller with closed-source firmware routes data to CPU
>CPU microcode (proprietary) interprets instructions from OS kernel
>OS kernel communicates with Ethernet controller via PCIe bus and non-free firmware chip
>NIC PHY chip with proprietary firmware modulates electrical signals
>NIC controller ASIC with closed-source firmware buffers packets in onboard memory
>"b-but I have OpenWRT and LibreCMC a-and!!!!"
>router's Broadcom System-on-Chip with proprietary firmware processes incoming packets
>router's Qualcomm WiFi chipset with non-free firmware handles wireless transmission
>ISP modem's DOCSIS chipset with proprietary firmware modulates cable signals
>ISP router's Cisco ASIC with closed-source firmware implements BGP routing

>>106127574 (OP)
>>106130091
>DNS server's RAID controller with proprietary firmware accesses cached records
>SSD controller chip (e.g., SandForce) with non-free firmware fetches zone files
>backbone router's Juniper custom silicon with proprietary firmware computes optimal paths
>web server's BMC chip with closed-source firmware manages hardware health
>server NIC's Intel i225 controller with proprietary firmware handles TCP segmentation offload
>server chipset's SATA controller with non-free firmware accesses storage
>NVMe SSD controller (e.g., Phison) with proprietary firmware reads flash cells
>database accelerator card with closed-source firmware processes SQL queries
>"b-b-but I have new OPEN SOURCE Nvidia and AMD drivers!!!"
>GPU video BIOS with proprietary firmware initializes rendering pipeline
>GPU display controller with non-free firmware generates TMDS signals
>"well my monitors are dumb unlike other people's TVs!!!"
>monitor scaler chip with proprietary firmware processes input timing
>LCD controller ASIC with closed-source firmware drives panel pixels
>monitor power management IC with proprietary firmware regulates backlight
>"fuck you! *takes his ReplicantOS phone*
>9001 proprietary chips with proprietary firmware

>bespoke hardware machine code
>useful replaceable code
It's unfortunate they're signed, but honestly, you aren't realistically replacing it.

>>106130091
You autistic faggots way overstate the risks of firmware. Last time I dealt with it, it was mostly just banging bits into registers so some OS gets an interrupt when something happen then the OS just reads some memory mapped register and moves on.

Drivers are a lot more important, though a driver can only do what the firmware exposes sadly. This is why stuff like nouveau is hampered.