Just speaking as one free software lover to another, I am happier that the Redpine Signal doesn't need downloadable firmware to function.
It means that there will be just one version of firmware shipped. Just one version of firmware that the whole community will focus on analyzing, patching (only for the librem phone, it's only pure chance if that helps any other device), and if a patch is needed:
* Redpine can either tell the entire community how to flash the firmware, or else the egg is on their face for shipping a broken firmware. *
(There's basically no chance that the Redpine chip is actually not field-upgradeable if you have the right vendor tool and probably also a windows box to run the tool on.)
The rest of the world seems to think, "flash it every time it boots up and I don't really care where that binary blob came from."
I'll also just add, I can respect your position. Thanks for supporting Free Software, and I get it that there's value to being able to upgrade. That's kind of what I'm hoping happens later, if (cough, cough, when) there's a bug or exploit or worse.
If purism waited until a manufacturer offered a perfectly open device, they'd have to wait until GNU Hurd ships on a phone... j/k
Well, of course, not having to deal with distributing and handling the firmware in your OS is a very nice bonus. However, I could have worded myself better: FSF's RYF certification actually isn't about "downloadable firmwares", it's about "upgradable firmwares". IOW, if the user is able to install the software by themselves, the preinstalled one must be free, period - and no closed alternatives can be advertised or suggested. Redpine releasing a tool to flash the proprietary firmware would likely make the Librem 5's RYF certification void, which is a thing that IMO isn't helpful to anyone involved.
Openmoko already went through that route, although AFAIR there was no formal RYF programme yet back then. Freerunner was all fine from FSF PoV until Openmoko released a firmware upgrade for the Calypso baseband that fixed some ugly bugs, suddenly making it not free enough for FSF. Which is especially funny considering that it basically opened the way to run OsmocomBB on that thing.
Yeah, the Openmoko situation and OsmocomBB really highlights the nuances of the situation.
I wish the FSF RYF requirements explicitly allowed a later release of a flash tool. (It seems like this only improves the user's freedom - suddenly you can treat your device as programmable, but only if you want to.)
But I don't think people will be nearly as upset if the Librem 5's RYF certification becomes void later.
I think the impact will still be large if it has RYF certification on launch.
It means that there will be just one version of firmware shipped. Just one version of firmware that the whole community will focus on analyzing, patching (only for the librem phone, it's only pure chance if that helps any other device), and if a patch is needed:
* Redpine can either tell the entire community how to flash the firmware, or else the egg is on their face for shipping a broken firmware. *
(There's basically no chance that the Redpine chip is actually not field-upgradeable if you have the right vendor tool and probably also a windows box to run the tool on.)
The rest of the world seems to think, "flash it every time it boots up and I don't really care where that binary blob came from."
I'll also just add, I can respect your position. Thanks for supporting Free Software, and I get it that there's value to being able to upgrade. That's kind of what I'm hoping happens later, if (cough, cough, when) there's a bug or exploit or worse.
If purism waited until a manufacturer offered a perfectly open device, they'd have to wait until GNU Hurd ships on a phone... j/k