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))
Activity
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
This question may be worth its own issue, since it's a common one that is also somewhat unanswered for the MSM8916 devices. I would generally say "no", because testing every single of them is really a waste of time that could be better invested in something else, while the chance that just a single device is affected by a regression is fairly low.
By Minecrell on 2022-12-10T22:10:59
Edited by Ghost Useradded discussion label
-
All related kernels should have kconfigcheck-community
Which kernels does this include?
Port more rk3288 and rk3399 devices
Is this a requirement for getting the existing ones into community?
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
As Minecrell said, let's make a separate issue about this. Do you want to have a go at that?
By Newbyte on 2022-12-11T08:47:24
-
All related kernels should have kconfigcheck-community
Which kernels does this include?
-
linux-postamrketos-exynos5(!3675 (merged)); -
linux-google-nyan(!3708 (merged)); -
linux-google-veyron(includes that initially); -
linux-postmarketos-rockchip(includes that initially); -
linux-postmarketos-mediatek-mt8173(!3707 (merged)); -
linux-postmarketos-mediatek-mt8183(!3667 (merged)).
Port more rk3288 and rk3399 devices
Is this a requirement for getting the existing ones into community?
No, but many existing ones are not tested, and I do not want to look for people to test devices (e.g. making a blog post if maintainers do not mind) when some devices are still not ported, especially when initial porting all of those is a 1-hour step
By jenneron on 2022-12-11T10:44:50
Edited by Administrator -
-
making a blog post if maintainers do not mind
Making a blog post sounds like a great idea to me :)
By Newbyte on 2022-12-11T20:02:29
Edited by Ghost User
-
As Minecrell said, let's make a separate issue about this. Do you want to have a go at that?
Done #1824 (closed)
By jenneron on 2022-12-11T11:14:24
marked the checklist item All related kernels should have
kconfigcheck-community(!3675 (merged), !3708 (merged), !3707 (merged), !3667 (merged)); as completedBy jenneron on 2022-12-14T07:01:02
marked the checklist item Fix #1414 (closed) (!3726 (merged)); as completed
By jenneron on 2022-12-14T09:09:58
mentioned in merge request !3279 (merged)
By jenneron on 2023-01-02T20:16:09