The impact will depend on the timing of ARMv8.1 adoption (proper hardware PAN) relative to Android's Linux 4.1 and 4.4 kernel versions.
-
-
Replying to @CopperheadOS
Would you ship a 4.X kernel if someone took the plunge to forward-port Nexus 5X/6P support?
1 reply 0 retweets 1 like -
Replying to @astarasikov
That's not going to happen. And no, we wouldn't move to a proof of concept port without proper testing and ongoing support.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @astarasikov
This is something that can be fixed for future devices by landing the drivers in mainline and steadily moving from LTS to LTS.
1 reply 0 retweets 1 like -
Replying to @CopperheadOS @astarasikov
It isn't going to happen without the SoC vendor, OEM and Google cooperating and investing a lot of resources to make it happen.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @astarasikov
If they actually move to the Pixel C hardware model, then it would just be the SoC vendor (likely Qualcomm) and Google.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @astarasikov
Qualcomm is doing a very poor job at landing their code upstream though. Sadly there's not much competition in that space.
5 replies 0 retweets 0 likes -
Replying to @CopperheadOS
the problem is that drivers which are stubs for binary blobs will not ever land upstream
1 reply 0 retweets 0 likes -
Replying to @astarasikov
Pixel C uses Nouveau with binary blobs in userspace.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @astarasikov
Can we pretend video doesn't exist for this discussion? Secure devices could use dumb unaccelerated FBs.
1 reply 0 retweets 0 likes
Given the size of GPU attack surface that's probably a necessary condition for security anyway.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.