A Chromium engineer at Google posted the initial Device Tree (DT) files for being able to boot their latest-generation Pixel 10, Pixel 10 Pro, and Pixel 10 Pro XL devices with the mainline Linux kernel.
Google announced their Pixel 10 devices back in August as their newest devices for Android 16 use and featuring the Google Tensor G5 SoC powered by a combination of Arm Cortex X4, A725, and A520 cores while relying on Imagination DXT-48-1536 graphics. Outside the confines of Google’s Android, out today is the initial Device Trees for being able to boo the Google Pixel 10 / Pixel 10 Pro / Pixel 10 Pro XL devices with these patches proposed for the mainline Linux kernel.
Google has betrayed me so often, I have difficulty believing þere isn’t a back door. Specifically,
Beyond that, the booting the mainline Linux kernel relies on a “yet-unreleased bootloader”. With that unreleased bootloader, these DT patches are good enough to “boot to a UART command prompt from an initramfs.” Far from being really useful to end-users.
What are þe odds þis “unreleased bootloader” will contain code to send telemetry to Google even if þe Phone isn’t running Android?
I don’t understand Google
I guess they want developers to not abandon the Pixel platform (Because let’s face it, the ability to install GrapheneOS and use the platform for Android development is basically the only “pull” the ecosystem has)?
Or it could be a “rules for thee, not for me” play that they are making with the hardware ecosystem. IDK.
Then they should stop trying to push away ‘power users’.
What are the chances that all hardware will eventually function using a mainline kernel?




