Hacker News Reader

Comment by strcat | Hacker News Reader

The kernel drivers are fully open source and moving to new kernel branches is a standard part of the update process. Pixels are currently moving from 6.1 and 6.6 to 6.12 with Android 17 QPR2. This is part of the hardware requirements for GrapheneOS listed here:

https://grapheneos.org/faq#future-devices

View on HN

Are you saying that GraphebneOS running on Google Pixels has no proprietary blobs apart from the firmware?

No, but all of the kernel drivers are open source and always were. The closed source userspace libraries such as the Mali GPU library aren't a barrier to porting to a new kernel version which is what was said above. We could move to 6.12 ourselves but we choose to wait for them for much broader testing which is happening with Android 17 QPR2.

Is there a list of the drivers and closed libraries somewhere?

The kernel drivers are all published in the GrapheneOS kernel repositories. A subset of the libraries/services in the vendor partition used with those drivers are closed source.

Pixels were headed towards all of the device support code for the OS being open source along with open sourcing large portions of the firmware including for the TEE (Trusty OS) and secure element (OpenTitan). It was ended after the launch of Android 16. It's a major factor in why GrapheneOS is going to be focused on future Motorola Mobility devices. You can still see a large portion of the Pixel userspace driver libraries and services in the AOSP source tree but they stopped pushing new releases for a lot of it.

We don't assume bad faith 'round these parts, so I have to ask a genuine question: Have you been diagnosed with any reading and/or learning disabilities? His comment was straightforward, clear, and three brief sentences long, yet you got something out of it that completely wasn't there.

You ask the same questions again of the same audience, year after year after year, either misunderstanding or totally disregarding the numerous simple, clear and direct answers you receive.

What's going on?

This comes down to doubts and a wish to get precise information with links/lists of drivers/firmware. Requests come not just from my side either, https://news.ycombinator.com/item?id=48585732

When I do recommend GOS, I want to know what I recommend precisely. Have you got an article about GOS similar to this one? https://pine64.org/2020/01/24/setting-the-record-straight-pi...

sigh. always this reply. go look at all the binary blobs in the source tree. you won't get modem, video out, touch, etc etc etc working without extracting eom drivers as binary.

also, there's ZERO mentions of drivers or binary blobs on that link!

Reply on news.ycombinator.com