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
amazon-austin: Init #311
Merged
Merged
amazon-austin: Init #311
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6df6e13
to
2756a00
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Comes from the repo used for the unofficial LineageOS 14.1
As-is, without a change.
2756a00
to
0b2c0a9
Compare
Though the vendor kernel is "self-hosted" by Mobile NixOS for convenience.
21dcc18
to
f5e3c67
Compare
I still have to think about whether I keep the third-party kernel attempt in the history. But eh, it now works against the untouched vendor kernel sources! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Not sure I want to merge this as-is.
I think I want to, instead, work from the kernel files from amazon.
The fork seems to have smushed together an arbitrary source tree from another MT8127 device, with the amazon drivers. The kernel looks... bad... imo.
I had to patch a lot of stuff to make
dmesg
not barf over all the time over. (Though some OEMs do do that too...)At the very least, building on top of Nixpkgs 56bb1b0f7a33e5d487dc2bf2e846794f4dcb4d01 works, with the changes from #306. (With a revert in the kernel builder). Current tip of master/unstable may have issues, to be investigated later.
The flashing procedure is clunky, but when a TWRP-compatible implementation is made, it will be less so, as it will not require an additional reboot. A simple
adb sideload
of a flashable zip should work.It is highly probable that on a 5th gen (
amazon-ford
) approximately the same implementation works. As the current kernel tree is shared between both devices, differing only by their initial defconfig. Usingamazon-ford
's defconfig, normalizing it, then applying the same changes may result in a usable port.TODO
Which means, first "rehydrate" them into distinct commits on the mobile-nixos linux repo.