Chrome OS devices TODO
-
Fix #1414 (closed); -
Implement booting with UUIDs to avoid issues having 2 installations; -
Adjust postmarketos-update-depthcharge-kernel to properly handle cases when there are 2 pmOS installations at the same time (e.g. on both eMMC and SD); -
All related kernels should have kconfigcheck-community; -
Rebase exynos 5 kernel; -
Workaround the issue about losing crossystem settings after battery discharge or add a warning about installation on eMMC - another solution: port U-Boot to as many armv7 chrome os devices as possible and recommend users to reflash SPI with U-Boot
- see https://wiki.postmarketos.org/wiki/Chrome_OS_devices#GBB_flags
-
Make use of depthcharge dtb selection where possible/appropriate; -
Try to fix mt8183 sound drivers to avoid configs like https://gitlab.postmarketos.org/postmarketos/pmaports/-/blob/master/device/testing/device-google-krane/modules-load.d/sound.conf; -
Port more rk3288 and rk3399 devices -
Improve depthcharge-tools packaging and move it to community; - !3792
-
Fix https://gitlab.com/cherrypicker/unl0kr/-/issues/36; -
Get more devices from Chrome OS devices page tested (maybe make a blog post about them to attract people); -
Discuss how we should test new releases on similar boards. Do we have to test a new release on a board if it is already 90+% covered with testing another board? If yes, we will probably never be able to move all these devices. -
Generic ports; -
port ondev2 installer -
consider implementing more generic ports for armv7 devices -
add some configuration for custom keyboard layout of these devices -
get most of userspace working with panel orientation quirks (#2240 (closed))
Edited by Administrator