PostmarketOS Trailblazer (postmarketos-trailblazer)
Manufacturer | Various |
---|---|
Name | Various |
Codename | Various |
Model | Various |
Category | testing |
Pre-built images | yes |
Original software | Various |
Original version | Various |
Hardware | |
Chipset | Various |
CPU | Various (Qualcomm, i.MX, Rockchip, etc...) |
GPU | Various |
Architecture | AArch64 |
Type | "handset", "laptop", "convertible", "tablet" |
USB Networking | |
---|---|
Flashing | |
Touchscreen | |
Display | |
WiFi | |
FDE | |
Mainline | |
Battery | |
3D Acceleration | |
Audio | |
Bluetooth | |
Camera | |
GPS | |
Mobile data | |
Internal storage | |
SMS | |
Calls | |
Accelerometer | |
---|---|
Magnetometer | |
Ambient Light | |
Proximity | |
Hall Effect | |
Barometer | |
Power Sensor | |
Keyboard | |
---|---|
Touchpad | |
USB-A | |
HDMI/DP | |
Memory Card | |
Haptics | |
Ethernet | |
FOSS bootloader | |
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.
Contributors
Users running Trailblazer
Installation
Use pmbootstrap to build your own installation image.
Installation will depend on the device and usecase, for Qualcomm devices running U-Boot, install with pmbootstrap install --split --add my-device-firmware-package
and then flash with fastbboot flash userdata $(pmbootstrap config work)/chroot_native/home/pmos/rootfs/postmarketos-trailblazer-root.img flash system $(pmbootstrap config work)/chroot_native/home/pmos/rootfs/postmarketos-trailblazer-boot.img
.
For installing directly to the target medium (like an sdcard or USB stick -- or internal storage) do pmbootstrap install --disk /dev/sdX
where sdX
is the target device (which you can usually identify with lsblk
).
Reporting bugs
In general, you should expect things to not work properly here. If you aren't sure if an issue is already known, please ask in the postmarketOS devel Matrix or IRC channel. Please avoid filing issues on pmaports unless you're certain that it's a bug that either a) should be tracked by the postmarketOS community, or b) is an issue with the trailblazer target itself (like missing kernel modules, config options, or dependencies for a device).
Adding a new device
In general we want to support as many devices as possible, as such adding new modules to the initramfs, enabling new kernel modules, or installing additional firmware by default are all reasonable things to do.
If your device requires some additional services to run during boot, then this should be done in such a way that it doesn't affect other devices. For example the service should check that it's relevant for the underlying hardware and exit otherwise.