Changes

Jump to navigation Jump to search
update mainline section
== What works ==
 
* Touchscreen
* Weston (has the red screen bug, but we have a workaround for that now 👍 )
== What does not work ==
 
* XWayland
* fbsplash only displays splash images very shortly, then goes to black screen
Looks like, we need to package the [https://github.com/LineageOS/android_device_lge_mako/blob/12ac6e9aeb32d5ac9fc832f2214ede2c7690d0a6/proprietary-blobs.txt#L152-L157 wcnss.* files] for wifi. A version from 2015 can be found [https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-14.1/mako/proprietary/vendor/firmware here]. It's a Qualcomm chip.
== freedreno / Mainline =={{note|See [[The Mainline Kernel]] for a general introduction to mainlining.}}Currently we only have a downstream vendor kernel packaged, not the mainline kernel. The <code>lg-mako</code> has the same [https://githuben.comwikipedia.org/freedrenowiki/freedreno/wiki freedrenoSystem_on_a_chip SoC] project brings an open source kernel driver for 3D acceleration. You would still need to run as the proprietary blob <code>asus-flo</code>, and on the GPU, but latter it makes 3D acceleration is possible at allto run [https://plus. There is google.com/111524780435806926688/posts/fkQ1BMjNNcn Android on a backport of freedreno to the 3.4 kernel, but the display doesn't work there. According close to robclark from Freedreno, it makes more sense to get [[The Mainline Kernel|mainline]] going:.
: ''tbhThis means, that most peripherals of the <code>mako</code> should work with mainline as well, once they are enabled in the exception of perhaps making phone calls DTS file. In fact, @vetzki reported in {{github|1079}} that the <code>mako</code> boots when using exactly the same DTS as the one from <code>flo</code> (modem)this is not recommended, upstream support for 8064 should be decent (as misconfiguring your device like the work that john stultz did on n7 tabletmay damage it).SSH appears to be working for a short time before getting kicked out, the display does not work. so I probably wouldn't try too hard on ancient 3.4 stuff''
Let us know if you're interested in doing this A good way forward would be using a minimal version of the <code>flo</code> DTS, where everything but USB is deleted, and talk fixing USB / trying to opendata26 (from postmarketOS) get the display working with the [https://github.com/freedreno/freedreno/wiki/DSI-Panel-Driver-Porting DSI Panel Porting Guide]. The downstream DTSI files that need to be ported to the upstream kernel are probably located [https://github.com/LineageOS/android_kernel_lge_mako/tree/lineage-15.1/arch/arm/boot/dts here], and robclark I guess the exact panel name appears when running <code>dmesg</code> after a successful boot (from freedrenoI did not verify this). With their help Please expand this when you're working on it should be quite feasible, and report your progress in #postmarketOS. Check out the [[Mainline Guide]].
== Links ==

Navigation menu