# Setting the Record Straight: PinePhone Misconceptions

DevFeed: [Setting the Record Straight: PinePhone Misconceptions](<https://devfeed.tech/articles/setting-the-record-straight-pinephone-misconceptions-34805.md>)

Original publisher: [Read original article](<https://pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/>)

Published: 2020-01-24T00:00:00Z

Content type: opinion

Language: en

Sources: [Community blog on PINE64](<https://devfeed.tech/sources/community-blog-on-pine64.md>)

Topics: [Pinephone](<https://devfeed.tech/topics/pinephone.md>), [allwinner](<https://devfeed.tech/topics/allwinner.md>), [foss](<https://devfeed.tech/topics/foss.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [SOC](<https://devfeed.tech/topics/soc.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [GPU](<https://devfeed.tech/topics/gpu.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>)

Tags: [bluetooth](<https://devfeed.tech/tags/bluetooth.md>), [boot](<https://devfeed.tech/tags/boot.md>), [foss](<https://devfeed.tech/tags/foss.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [linux](<https://devfeed.tech/tags/linux.md>), [misconceptions](<https://devfeed.tech/tags/misconceptions.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [pinephone](<https://devfeed.tech/tags/pinephone.md>)

## AI overview

The article addresses misconceptions that the PinePhone is closed-source. It explains that the Allwinner A64 SoC uses mainline Linux, mainline ATF and u-boot, with open-source drivers for its main components. It also identifies non-FOSS parts, including WiFi and Bluetooth firmware, optional camera autofocus firmware, and the Quectel EG25-G modem's closed-source operating system.

## Source excerpt

I take no pleasure in writing this blog post. In fact, even as I am writing these words I am internally torn on whether this is the right approach to addressing the problem on hand. Whether I've chosen the right approach remains to be seen, but regardless, I now feel it's time to confront misconceptions about the PinePhone. What's the misconception? The misconception concerns the openness of the PinePhone. On numerous occasions I've seen the PinePhone being refereed to as closed-source on one level or another. I don't know the origin of this misconception nor do I understand the reason why it has become propagated throughout the internet. What I do know, however, is that it has been repeatedly quoted in online articles covering the PinePhone or other Linux devices for over a year now. So let's set the record straight: the PinePhone is not 'full of closed-source firmware' and, moreover, is one of the most open devices out there. Here's what's open Let's start with the Allwinner A64 SoC, which is the brains of the PinePhone; it runs mainline Linux, uses mainline ATF and u-boot and there are open source drivers for all main SoC components. This openness extends to the Lima GPU driver introduced in kernel 5.2. Linux 5.6 will contain drivers for all major components of the SoC. The parts which still need to be upstreamed to mainline are HDMI audio and msgbox - both drivers are in the works. For more information on mainlining efforts, please refer to the A64 column at https://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix It's worth mentioning that LPDDR3 initialization is done by u-boot SPL, which is also open source. There are no blobs in there either. Needless to say, the PinePhone itself is an open platform for any OS to run on. The grand majority of the OSes developed for the PinePhone are, in and of themselves, completely open too. So, where are the blobs? The non-FOSS parts of the phone are as follows: WiFi and Bluetooth firmware must be uploaded to the Real