Some nuance is in order.
Actually, Windows10 itself only auto-orients (if not locked, of course) on my tablet, not on my phone. The OS on a windows phone only works in portrait format. On the tablet all apps can auto-orient, on the phone most can, but a good many can’t.
So, a telephone with an OS that has more than one orientation is a step for me.
Just found this yesterday, extremely useful already!
Thanks for shedding some light on the “Aspen” issue too. It actually was the last thing I read on the Purism pages before I stopped reading their posts since I didn’t want to watch them go down
Now most of the things seem to be bright again though
While not exactly adding to it by myself (at least not for the moment), I wanted to point out or suggest a few things:
I once heard that GitLab is claimed to be inaccessible from the Ukraine. Is that still the case? If yes, might it be better to publish the wiki in a place more open to such countries that are considered “problematic” by some other countries?
Then, I couldn’t come up with definite answers to the following questions, but I’ll try to make some suggestions:
Q1: “Free” is even better than just “opensource”. Thus I want to find the lowest-level code that is run when the Librem 5 (insert batch here) boots. Where can I find it? (Put in “PC terms”: <<Where can I find the source code of my PC BIOS?>>)
Q3: What is the rough boot flow in the Librem 5 from the very first instruction to the last instruction before the Linux kernel finally takes over? For instance, where does this “u-boot” chime in? Is this u-boot a completely separate alternative approach from using the secure boot facilities or is it used on top of those?
A3: The tiny bit I can come up with is https://source.puri.sm/Librem5/arm-trusted-firmware/-/blob/librem5/docs/reset-design.rst. This not only depends on Purism employing those secure boot techniques in the first place, but also excludes all the higher-level parts which judging from the picture only run after the C-runtime has been initialized.
When looking at the level of the .S files in the Librem 5 u-boot project it may be completely separate to the secure boot stack. I.e. you can have one or the other but not both in the same firmware build.
On a side-note:
Maybe it is even possible to create a “developer” wiki or something like that, since Librem 5 newbies (except for me ) most likely won’t be interested in such deep matters?
If there is already such a wiki then maybe it should be referred to in a FAQ answer.
Feel free to rephrase my questions when possibly copying them to the existing ones.
As for the answers, these are what I have been able to come up with without expending days for the search. Hence I’m pretty certain that some of them are possibly far from truth.
I have asked that Purism create a general community wiki that covers all Purism products. See this thread for the discussion.
My Google searches in English didn’t turn up anything about GitLab being blocked in Ukraine. Perhaps that is a rumor that arose from this story about GitLab and Russia. If the gitlab.com domain is blocked in Ukraine, it is unlikely to cover source.puri.sm, which is a local installation of GitLab in another domain.
I can’t find the proprietary firmware for the DDR training which is stored in the SPI Flash chip. This page explains how SolidRun builds the flash.bin file that can be saved in the SPI Flash chip, but I don’t know if Purism does it the same way.
I added this text to the FAQ:
The following proprietary firmware for the Librem 5 is available for download in the Purism code repository:
Feel free to create a new page in the Librem 5 community wiki to explain what is the Librem 5 booting sequence. I don’t know enough to answer that question.
Missed that Wikipedia alleviated GitLab’s/Google’s statement: (<< To overcome this issue, the non-profit organization Framasoft provides a Debian mirror to make GitLab CE available in these countries.[31] >>)
I reckon, that this really isn’t too much of a problem then, especially not if they would block just the gitlab.com domain.
Will try to do so as soon as I’m able to conduct hands-on experiments on recompiling and re-flashing the complete firmware. Perhaps Q3/2021?
It doesn’t have UEFI–it uses u-boot instead. To test whether it has ACPI support, someone who has the phone should do this: sudo apt install acpi acpi -V
To determine its level of SBSA would take hours of reading the spec and testing each thing in the spec, and I doubt that very many people care about SBSA.
Purism has been accepting pre-orders for the Fir batch at the same price as the first version of the Librem 5, but has not made any further announcements, so it is not known whether Fir will have more RAM, more Flash memory storage, or different components than the Librem 5 (Evergreen).
This is not true that Purism made no further statements. Here is one:
Purism announced “Fir” on 2019-09-05 and @nicole.faerber made that comment one day later on 2019-09-06, and that comment doesn’t contain any more info about Fir than the original post. Since then, Purism employees have reaffirmed that Fir will happen on this forum, but Purism hasn’t released any further details about Fir.
Nothing is wrong. The FAQ could just be updated saying that the i.MX 8M Plus, first announced in early January 2020, is likely to become the power envelope for the phone according to not only to the existing FAQ link but also according to this link above I found.
Although you are right that no further announcements were made.
Since that answer was written Purism published a couple of very good articles and videos on convergence. I think they should be emphasized here and be linked in the very beginning, especially the first one: