News for hackers. Stuff that matters.

A comment on The FSF’s relationship with firmware is harmful to free software users. Parent comment

Re:The FSF’s relationship with firmware is harmful to free s... by tedunangst on Saturday January 22, 2022 @09:22PM (#30043028)
Whether it's loaded into RAM or ROM is the most useless distinction to make. It's functionally identical. Now whether a driver requires executing proprietary code on the host CPU, that is a useful distinction to make, because it allows independent OS implementations to create free drivers.
[ Parent | on HN ]
Re:The FSF’s relationship with firmware is harmful to free s... by kevin_thibedeau on Saturday January 22, 2022 @09:29PM (#30043056)
It isn't identical. With a fixed ROM, every user is denied an opportunity to upgrade rather than just those without an anointed OS. It's about equal access.
[ Parent | on HN ]
Re:The FSF’s relationship with firmware is harmful to free s... by tedunangst on Saturday January 22, 2022 @09:34PM (#30043072)
Sounds like a good reason to certify hardware that puts firmware in RAM.
[ Parent | on HN ]
Re:The FSF’s relationship with firmware is harmful to free s... by kevin_thibedeau on Saturday January 22, 2022 @09:44PM (#30043122)
Most peripheral ICs have an on board micro with internal RAM and flash. Their RAM isn't typically accessible.
[ Parent | on HN ]
Re:The FSF’s relationship with firmware is harmful to free s... by tedunangst on Saturday January 22, 2022 @10:22PM (#30043316)
Nevertheless, the first thing the driver for wifi in my laptop does is load up a big firmware file from disk, caused to be shoved into IC RAM, and then proceed to connect to the network. That this process could somehow become more free by embedding a frozen firmware image blows my mind.

And it's not like I haven't seen what the other side looks like. The Broadcom "full MAC" chipsets are also supported, with their remotely exploitable firmware. But those are also "fully" free. Hurray.

[ Parent | on HN ]