HNHacker News
TopNewBestAskShowJobs

amosbatto

252 karma · joined November 24, 2017

submissionscomments
amosbatto··on Manufacturing the Librem 5 USA Phone in the US
It would be almost impossible to make a phone with parts that are entire manufactured in the US. Most silicon foundry work is done in Taiwan (TSMC, UMC, Vanguard) and S. Korea (Samsung, DB HiTek). See: https://www.cnbc.com/2021/03/16/2-charts-show-how-much-the-w...

However, if you are interested where the Librem 5 parts are made, see: https://source.puri.sm/Librem5/community-wiki/-/wikis/Freque...

amosbatto··on Manufacturing the Librem 5 USA Phone in the US
Yes, the CPU is weak, suspend-to-RAM hasn't yet been added to the mainline Linux driver for the i.MX 8M, camera auto-focus doesn't yet work, and lot of work is needed for full functionality of the Megapixels camera app and use of an OpenPGP smartcard, but you are ignoring all the progress that has been made. Purism started with a new chip that didn't yet have good mainline Linux support and had to make several hundred commits to mainline Linux to support half a dozen new chips. Purism created a new mobile environment for Linux, which 65% of PinePhone users say in a poll is their favorite interface. Purism created the first free/open hardware phone since the Golden Delicious GTA04 in 2014 and manufactured the first phone in the US since the Motorola Moto X in 2013. The Librem 5 contains 6 innovations in the mobile phone industry, which is more innovations than any phone since the Samsung Galaxy S5 released in 2014. This is the first phone ever produced where the manufacturer promises lifetime software updates and the processor will be produced by the manufacturer (NXP) until at least Jan. 2033.

All of this info is on the FAQ: https://source.puri.sm/Librem5/community-wiki/-/wikis/Freque...

amosbatto··on Manufacturing the Librem 5 USA Phone in the US
The NXP i.MX 8M Quad processor in the Librem 5 has "Made in Korea" stamped on them and there have been news articles published about how NXP was switching its foundry work from TSMC to Samsung. By the way, the i.MX 8M is designed in Austin, Texas (by the old Motorola division, which turned into Freescale and then was bought by NXP).

For more info, see: https://source.puri.sm/Librem5/community-wiki/-/wikis/Freque...

amosbatto··on Why FSF Endorsing PureOS Matters
Purism has said that it will be providing proprietary firmware updates, and it already has instructions how to update the firmware for the RS9116 WiFi/BT on its web site.

Because Purism selected components for the Librem 5 that will be manufactured for many years, it is more likely to get firmware updates than most smartphones. Because the drivers are all FOSS, they can be updated by the community, and some cases the manufacturer helps maintain the mainline Linux drivers, so timely updates are very likely. For example, NXP promises to sell its i.MX 8M Quad processor until at least Jan. 2028 and it helps maintain the mainline Linux driver. Likewise, Redpine Signals helps maintain the mainline driver for the RS9116 WiFi/BT and likely to keep manufacturing the chip for at least the next 5 years.

In contrast, the SoC used in a typical smartphone is only manufactured for 1-2 years and it typically only gets 2-3 years of support from the manufacturer, so the Librem 5 is more likely proprietary firmware updates than most smartphones.

As for the question of whether it is better to store the proprietary firmware in the /lib/firmware directory or in the component or in Flash chips on the motherboard, there are advantages and disadvantages, so you have to weight what is important. When firmware is stored and loaded from the /lib/firmware directory, it is easier to update and the user will automatically get the latest firmware when upgrading the software on the device. In contrast, the user has do a separate procedure to upgrade the firmware and many users are unlikely to do it, so any potential security holes in the firmware are less likely to be closed with updates. However, a lot of this depends on what Purism does in the future to push firmware updates, so we shouldn't automatically assume that the Librem 5 will be insecure. The benefit of not storing the firmware in /lib/firmware is because it makes the user more conscious of the proprietary blobs on the device, and the user can make a deliberate choice whether to install firmware updates or not, after reading the description of each update. Also, it is harder for the firmware to be hacked by a bad actor when it is stored in the component or a separate Flash chip, because it requires a separate procedure to flash the firmware, so it can be argued that it is more secure. Another benefit is that system updates can be offered without including any proprietary files, so there are no restrictions on how they are distributed and installed.

In terms of promoting software freedom, I don't know of any cellular modems or any GNSS with FOSS firmware. There were only two WiFi/BT model series whose firmware was reverse engineered by the community but they never got past the experimental state and are now hopelessly outdated since they were 802.11b/g devices. There are some ath9k 802.11n models that required no firmware, but they have poor range and are energy inefficient and require proprietary firmware for the Bluetooth.

In other words, there is no realistic way to make a modern computing device without proprietary firmware, and the only hope is to pressure the manufacturers to release code or documentation for its firmware, but the modern patent situation with wireless communications makes that extremely unlikely to happen. However, the FSF's insistence on trying to separate the proprietary firmware and not let it be executed on the main CPU cores does draw public attention to the problem and show the component manufacturers that there is public demand for free firmware. When companies like Purism go through extreme steps to avoid executing DDR timing code on the main CPU cores, by adding a separate SPI Flash chip to the board to hold the blob and not using the Cortex-M4 core for any other purpose but to execute that blob, it sends a message to NXP that its customers really hate that proprietary blob and it should be eliminated. In contrast, a company that stick that blob in the main Linux file system tells NXP that its customers don't care about that blob and there is no pressure for NXP to eliminate it in future chips. The value of buying RYF products like the Librem 5, RaptorCS computers and Lulzbot is that it is creating a public statement that consumers care about not having proprietary blobs, and that the hardware industry should cater to that crowd. What Purism is doing value in promoting a public message and it is based on a long-term strategy to pressure the industry to free its firmware, whereas the people who criticize it have no strategy for ever achieving change. If they have an alternative strategy for how to free the firmware, I would love to hear it.

The more important point is that Purism selected components from hardware companies that are more willing to collaborate with the community and listen to Purism's requests, so there is more possibility of driving change up the supply chain. Purism paid Redpine Signals to modify its firmware so it could meet the RYF criteria and NXP engineers work with the community on the mainline Linux driver for the i.MX 8M, so it is possible to influence these component suppliers.

amosbatto··on Why FSF Endorsing PureOS Matters
I'm a strong believer in "free software" as RMS defined it, and I give the man a lot of credit for getting the movement started. However, my few interactions with him were not pleasant, although I did have an interesting conversation with him once about promoting the environmental benefits of hardware running free software.

My main problem with the FSF has been more in terms of poor strategy in terms of how it engages with the software and hardware industry, rather than the philosophical vision.

amosbatto··on Why FSF Endorsing PureOS Matters
I have no idea whether the internal process at the FSF changed or not, but the rules are the same for the FSF endorsing a distro and giving its Respects Your Freedom certification to a piece of hardware.

This page has stayed the same: https://ryf.fsf.org/about/criteria

However, I raised a question about how to interpret the RYF criteria with regard to proprietary firmware updates, and I'm hoping the FSF will clarify the RFY criteria in a way that allows proprietary firmware updates for components that don't execute on the main CPU cores. See: https://forums.puri.sm/t/does-respects-your-freedom-certific...

amosbatto··on Why FSF Endorsing PureOS Matters
There has been documentation for how to update the proprietary firmware for the RS9116 modem on the Librem 5 since early 2019: https://developer.puri.sm/Librem5/Development_Environment/Bo...
amosbatto··on Librem 5 Evergreen vs. Pinephone
The people doing the final assembly of the Librem 5 USA are working in Purism's Fulfillment Center in Carlsbad, California, which is a suburb of San Diego. Housing is very expensive in the San Diego area, so we are talking about wages for assembly workers that are much higher than $13 or $14 per hour. It sounds like the company making the PCB's is also located in the San Diego area (based on what Purism said about its Librem 5 DevKit), which means that Purism is paying a company that likely makes prototype boards, which means that Purism is paying a lot more for its boards than Chinese mass production prices. I doubt that Purism has more than a couple hundred orders for the Librem 5 USA, but it says that it will store the parts for the phone and do the final assembly itself. It also is doing just-in-time manufacturing of the phone in very small quantities. All of this has very high unit costs.

Frankly, ThatGeoGuy's assessment of the Librem 5 USA is ridiculous. First of all, he doesn't evaluate what it costs to set up a facility in a San Diego suburb that stores parts with supply chain security, orders small-scale PCBA production, and does small-scale final assembly. Second, he ignores the fact that the Librem 5 USA is a niche product for corporate and government clients who need supply chain security. It is competing with products like the Silent Circle's Silent Phone, Motorola Solutions' LEX L11 and Bittium's Tough Mobile 2. The only one of those phones which publicly lists its price is the Bittium Tough Mobile 2, which costs €1550 (US$1816), so the Librem 5 USA is in the same price range. Third, he totally ignores the cost of paying roughly a dozen developers to work for 3.3 years to develop a Linux phone. How does a company recover those high development costs that have gone way over budget? One way is to develop a side product with high profit margins that caters to niche customers with specialized needs.

amosbatto··on Librem 5 Evergreen vs. Pinephone
ThatGeoGuy, Since you called me that "crazy uncle at Thankgiving," I feel that the "crazy uncle" should have a chance to respond to the arguments that you made in your review: https://forums.puri.sm/t/pinephone-vs-librem-5/9092/83
amosbatto··on Librem 5 Evergreen vs. Pinephone
For info on Jumpdrive and many other things, see the FAQ: https://source.puri.sm/Librem5/community-wiki/-/wikis/Freque...
amosbatto··on Pine64 November Update: KDE PinePhone CE and a Peek into the Future
Looking at the pin description on page 24 of the A64 Datasheet, it looks like the 8 data pins (CSI_D0 … CSI_D7) are for a MIPI Camera Parallel Interface (CPI), but Allwinner is calling it "CSI" (MIPI Camera Serial Interface).

This is really confusing, but I am simply repeating what the A64 docs say.

Out of curiosity, what is the highest-resolution still photo anyone has taken so far on the PinePhone? Maybe I should list that in the table.

Is 1080p@15fps the best video anyone has managed so far with the PinePhone?

amosbatto··on Pine64 November Update: KDE PinePhone CE and a Peek into the Future
Hi megous, I created the spec table comparing the two phones.

The "2.7. Image In" section on page 10 of the A64 Datasheet (https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_...) calls MIPI CSI a "8bitYUV422 CMOS sensor parallel interface". Are you referring to that parallel interface or something else?

--------

2.7. Image In

CSI

•Support 8bitYUV422 CMOS sensor parallel interface

•Support CCIR656 protocol for NTSC and PAL

•Maximum still capture resolution to 5M

•Maximum video capture resolution to 1080p@30fps

-----

I see that I was mixing up inputs/outputs and channels. The A64 supports 4 inputs and 4 outputs, but only two channels in the DAC and ADC. I see that the DAC supports 8 - 192 kHz, but the ADC only supports 8 - 48 kHZ. OK, I'll clarify that in the table.

-----

2.8.Audio Subsystem

Audio Codec

•Two audio digital-to-analog(DAC) channels

•Stereo capless headphone drivers:

-100dB SNR@A-weight

-Support DAC Sample Rates from 8KHz to 192KHz

•Support analog/ digital volume control

•Differential earpiece driver

•Analog low-power loop from line-in/microphone to headphone/earpiece outputs

•Support Dynamic Range Controller(DRC) adjusting the DAC playback output

•Accessory button press detection

•Four audio inputs:

-Twodifferential microphone inputs

-One differential Phone input

-Stereo Line-in L/R input

•Four audio outputs:

-Earpiece amplifier differential output

-Phone amplifier differential output

-Headphone amplifier L/R channel output

-Line-out L/R output

•Two audio analog-to-digital(ADC) channels

-96dB SNR@A-weight

-Supports ADC Sample Rates from 8KHz to 48KHz

•Support Automatic Gain Control(AGC) and Dynamic Range Control(DRC) adjusting the ADC recording output

•Two PCM interface connected with BB and BT

•One 128x24-bits FIFO for data transmit, one 64x24-bits FIFO for data receive

•Support Audio HUBI

-----

amosbatto··on Purism – Fund Your App
A lot depends on what online services you are using. The goal of Purism is to provide a suite of online services at Librem One (https://librem.one/) so you don't have to share your personal data with Google, Facebook, Twitter, etc.

Also see: https://source.puri.sm/Librem5/community-wiki/-/wikis/Freque...

amosbatto··on Purism – Fund Your App
Current shipping date is estimated at mid-to-late November 2020. It is definitely getting closer. I try to keep the community FAQ up-to-date, if you want current info: https://source.puri.sm/Librem5/community-wiki/-/wikis/Freque...
amosbatto··on Purism – Fund Your App
The recent versions of Squeekboard have a full keyboard like Hacker's Keyboard in Android. See: https://source.puri.sm/Librem5/squeekboard/-/merge_requests/...
amosbatto··on Purism – Fund Your App
The Librem 5 apps will use flatpack with bubblewrap. See: https://source.puri.sm/Librem5/community-wiki/-/wikis/Freque...
amosbatto··on Purism – Fund Your App
It also gives Purism some idea where to focus its development efforts, since Purism literally has a thousand problems to solve so it has to prioritize what is truly important and what can wait.
amosbatto··on Purism – Fund Your App
The "L" part was an effort to include all the speakers of Romance languages who say "software libre" or "software livre". In my experience living in South America, very few people say "código abierto" or "fuente abierto" at the Linux conferences except if they are companies presenting business plans. For most, they don't see the need for the division between "free software" and "open source", so FLOSS is a more inclusive term to cover more of the world.

My personal belief is that we need the discourse of both the OSI and FSF because they appeal to different segments, and we need both the business community and people care about user rights to be in the movement if we want FOSS to succeed.

amosbatto··on Purism – Fund Your App
If you want a list of the apps for the Librem 5, see: https://source.puri.sm/Librem5/community-wiki/-/wikis/Freque... (in the first link, it tells how ready the software is to be used in the Librem 5, and that list is maintained by the developers so it should be up to date.)

You can also try out recent images of the Librem 5 to see what apps work: https://source.puri.sm/Librem5/community-wiki/-/wikis/Freque...

← PreviousPage 2 of 2