Daniel Micay on Twitter: "@AlwaysCurious__ It's nearly the same as the Pixel 4a (5G) and to a slightly lesser extent the Pixel 5. It's way easier to add support for it than any past devices. Auditor / AttestationServer support was the straightforward first step and then the other usual things but way less work than usual." / Twitter

twitter.com/DanielMicay/st This should all be figured out now. Expect to see GrapheneOS Pixel 5a support in the near future. Pixel 6 will be much harder to add than this. Ideally we'll get gotten memory tagging implemented for hardened_malloc beforehand since it'll likely have it.

Quote Tweet

Daniel Micay

@DanielMicay

Sep 6, 2021

Hoping that github.com/GrapheneOS/ker resolves the Pixel 5a audio issues. They moved to a different DAC in the Pixel 5a compared to the Pixel 4a (5G). Other than that, it's almost entirely the same hardware. I'm curious if it's actually substantially better than the previous one.

1

5

22

Replying to

What is the hardest part going to be?

1

Daniel Micay

@DanielMicay

Replying to

@AlwaysCurious__

It's nearly the same as the Pixel 4a (5G) and to a slightly lesser extent the Pixel 5. It's way easier to add support for it than any past devices. Auditor / AttestationServer support was the straightforward first step and then the other usual things but way less work than usual.

7:56 AM · Sep 7, 2021Twitter Web App

Replying to

and

The main difference is that they moved to a new DAC/amplifier so there's a new audio driver and it wasn't set up to be built into the kernel rather than as a dynamic kernel module. github.com/GrapheneOS/ker GrapheneOS builds all modules into the kernel and disables DKM support.

github.com

add missing configuration for in-tree build · GrapheneOS-Archive/kernel_google_barbet_techpack_au...

1

Replying to

and

Since doing that results in much finer-grained CFI, lower overhead for CFI and better performance overall which makes up for the overhead of other mitigations too. Also reduces complexity and attack surface but it's not really the main reason for us not wanting dynamic modules.

Conversation