Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

device: Google Pixel 2 (non-XL) // google-walleye #50

Merged
merged 6 commits into from Nov 19, 2019

Conversation

samueldr
Copy link
Member

@samueldr samueldr commented Nov 19, 2019

This adds the port for the Google Pixel 2 (non-XL variant).

#38 can be rebased off of these changes. It should match, except for the kernel config, where these notes from the android-linux-stable project are relevant.

A common kernel solution will need to be figured out in the long run, but for now, this works.

It seems to work to parity with other devices... though sometimes the framebuffer doesn't seem to init right, but X11 always ends up starting. (Meaning that the Google bootloader logo sticks around for longer).


The next time I go around closing PRs I'll re-read this one, try to review it with a blank mind.

The kernel build is technically the same as google-taimen, with some
options switched around. An upcoming improvement will be to share the
"wahoo" platform's kernel build with an option to switch between the
two at build time, and further along the line, with modular kernels,
sharing the same exact builds, but with the device-specifics as modules.
And related options.
@samueldr samueldr added the 4. type: port New device port label Nov 19, 2019
@samueldr samueldr self-assigned this Nov 19, 2019
@samueldr samueldr merged commit bcc0f77 into NixOS:master Nov 19, 2019
@samueldr samueldr deleted the devices/google-walleye branch November 19, 2019 19:09
@OliverOffing
Copy link

Does this mean NixOS Mobile on Google Pixel 2 (non-XL) is stable? Should it be included in the device list?

@samueldr
Copy link
Member Author

Sorry, no, it meant that 4 years ago there was tentative support added in hope that using vendor-based sources would be possible.

Since then, with all that was learned, and how the overall ecosystem learned, it is obvious that it is a dead-end. See #643.

To add support for any device, the device now needs to have some form of support either in mainline Linux, or in a mainline-adjacent "meant to go in mainline Linux" tree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4. type: port New device port
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants