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
sony-pioneer: init #205
sony-pioneer: init #205
Conversation
Same SoC, same kernel version, most likely will work better that way
Otherwise untouched from OEM config.
We do not add LOCALVERSION to the kernels.
(As with xiaomi-lavender)
(As with xiaomi-lavender)
This one is important as, contrary to what the name sounds like, it builds the full device tree with the kernel, rather than rely on on-device overlays.
It is counter-productive for non-android systems.
(As with xiaomi-lavender)
…eOS defconfig This one comes from an artifact of starting up with the **OEM's** configuration, but actually using the LineageOS tree. LineageOS adds many alterations that may cause incompatibilities.
This is not strictly needed, but rather quite helpful to get network access until we can get WiFi working.
3d5b04f
to
5c68fac
Compare
5c68fac
to
78647e9
Compare
With this PR we're creating a kind of precedent, which I'm not 100% sure we'll keep using. We are now shipping unused files with information about the OEM images, as extracted by autoport. While this is not great because it's unused, it's actually not bad as it allows documenting some aspects of the device in a generic manner that is helpful for reviewers. By adding the data that autoport used to the repository, we can add fixes to autoport as needed and better understand why things were ported "that way". |
This is a demo PR (that will be merged) that shows all the work done to port a device from the autoport project.
It took 50 minutes moment I copied the config to the repo, to the moment I booted to the demo rootfs. This is a new record for myself.
The important bit, for future porter-users, are for the kernel.
I have taken another SDM660 device's kernel builder derivation (xiaomi-lavender) and copied it outright with patches (as the patches were known non-specific).
And finally the changes to the kernel configuration. I have basically used
nvim -d
on the default config and another SDM660 device to figure out what was missing.Note that the USB vid/pid have been figured out by looking through the files extracted from a system image. There is no failsafe way to get them, other than running the OEM's system image and looking at what the device advertises as.