pmaports/device/testing/device-postmarketos-trailblazer/modules-initfs

atmel_mxt_ts
bq25890_charger
edt-ft5x06
goodix
gpi
gpio_vibra
i2c-qcom-geni
led_bl
lmh
msm
panel-samsung-s6d7aa0
panel-samsung-sofef00
panel-visionox-rm69299
phy-qcom-qmp-combo
phy-qcom-qmp-ufs
phy-qcom-qmp-usb
phy-qcom-qusb2
rmi_core
rmi_i2c
ufs-qcom
zinitix
postmarketos-trailblazer: sort modules (MR 5257) 2024-06-20 14:51:25 +00:00			`atmel_mxt_ts`
			`bq25890_charger`
			`edt-ft5x06`
			`goodix`
			`gpi`
			`gpio_vibra`
			`i2c-qcom-geni`
			`led_bl`
			`lmh`
			`msm`
			`panel-samsung-s6d7aa0`
testing/device-postmarketos-trailblazer (MR 4967) trailblazer is a bleeding edge, unstable target for EFI capable ARM64 devices. It runs linux-next and should otherwise be adjusted to support as many devices as possible. The goal of trailblazer is to motivate more upstream kernel development by providing a tighter feedback loop (patches land in -next weeks before they make it into mainline or stable), as well as encouraging more generic solutions to the device specific hacks we have in userspace. On supported devices, trailblazer should reflect the current state of upstream. It allows users to easily appreciate what feature are unavailable, and more importantly appreciate when a new feature does get added upstream. Due to the instability of linux-next, the plan is to have BPO build trailblazer images nightly, so if next breaks then the images should only be broken for a day. Signed-off-by: Caleb Connolly <caleb@postmarketos.org> 2024-03-21 22:12:13 +00:00			`panel-samsung-sofef00`
			`panel-visionox-rm69299`
			`phy-qcom-qmp-combo`
			`phy-qcom-qmp-ufs`
postmarketos-trailblazer: sort modules (MR 5257) 2024-06-20 14:51:25 +00:00			`phy-qcom-qmp-usb`
testing/device-postmarketos-trailblazer (MR 4967) trailblazer is a bleeding edge, unstable target for EFI capable ARM64 devices. It runs linux-next and should otherwise be adjusted to support as many devices as possible. The goal of trailblazer is to motivate more upstream kernel development by providing a tighter feedback loop (patches land in -next weeks before they make it into mainline or stable), as well as encouraging more generic solutions to the device specific hacks we have in userspace. On supported devices, trailblazer should reflect the current state of upstream. It allows users to easily appreciate what feature are unavailable, and more importantly appreciate when a new feature does get added upstream. Due to the instability of linux-next, the plan is to have BPO build trailblazer images nightly, so if next breaks then the images should only be broken for a day. Signed-off-by: Caleb Connolly <caleb@postmarketos.org> 2024-03-21 22:12:13 +00:00			`phy-qcom-qusb2`
postmarketos-trailblazer: sort modules (MR 5257) 2024-06-20 14:51:25 +00:00			`rmi_core`
			`rmi_i2c`
testing/device-postmarketos-trailblazer (MR 4967) trailblazer is a bleeding edge, unstable target for EFI capable ARM64 devices. It runs linux-next and should otherwise be adjusted to support as many devices as possible. The goal of trailblazer is to motivate more upstream kernel development by providing a tighter feedback loop (patches land in -next weeks before they make it into mainline or stable), as well as encouraging more generic solutions to the device specific hacks we have in userspace. On supported devices, trailblazer should reflect the current state of upstream. It allows users to easily appreciate what feature are unavailable, and more importantly appreciate when a new feature does get added upstream. Due to the instability of linux-next, the plan is to have BPO build trailblazer images nightly, so if next breaks then the images should only be broken for a day. Signed-off-by: Caleb Connolly <caleb@postmarketos.org> 2024-03-21 22:12:13 +00:00			`ufs-qcom`
			`zinitix`