zlacker

[parent] [thread] 3 comments
1. rollca+(OP)[view] [source] 2022-03-22 14:44:28
> I’ve read somewhere recently that in order to keep the phone mostly free of proprietary firmware, Purism had no choice but pick lots of discrete components.

This is only a half the story. The Purism still runs on proprietary firmware. The discrete components in question are an actual full auxiliary CPU core, its only purpose being to load the hard-coded blob to properly boot the primary SoC. This was done because under FSF's definition, if the end user cannot update the firmware blob, then the firmware is considered one with the hardware, and the hardware as a whole is "free enough".

So they took away the user's ability to update the firmware, fused it in a ROM with every possible bug and inefficiency frozen in place for the rest of eternity, wasted silicon and engineering time to do so, only to grant themselves an arbitrary, honorary badge.

This isn't even radicalism anymore, this is hypocrisy. As a power-user who values freedom, and a long-time Free Software sympathiser, I am personally offended, and won't give my money to either party until they reverse course on their user-hostility.

replies(1): >>seba_d+Av
2. seba_d+Av[view] [source] 2022-03-22 17:03:34
>>rollca+(OP)
> So they took away the user's ability to update the firmware, fused it in a ROM

That's simply not true. Users can upgrade those firmwares if they want (and absolutely no weird tricks like disassembling or soldering are necessary for that). PureOS doesn't distribute any non-free updates, but if you want, you absolutely can reflash these blobs.

replies(1): >>rollca+qd1
◧◩
3. rollca+qd1[view] [source] [discussion] 2022-03-22 20:50:44
>>seba_d+Av
From TFA: https://puri.sm/posts/librem5-solving-the-first-fsf-ryf-hurd...

> The RYF has a “secondary processor” exclusion that can be granted on a case by case basis. We will leverage this exclusion to load and train the DDR PHY on the i.MX 8. We will use a secondary processor to keep binary blobs out of u-boot and the kernel.

replies(1): >>seba_d+0c2
◧◩◪
4. seba_d+0c2[view] [source] [discussion] 2022-03-23 04:58:46
>>rollca+qd1
So what? How exactly would that "take away the user's ability to update the firmware"?

Librem 5 does not lock the firmwares in any kind of ROM. Nothing is taken away from the user.

[go to top]