Sources
- Install the OEM firmware package for each Snapdragon machine
- Find the Snapdragon OEM firmware packages by what they provide
- Refresh the Snapdragon device tree list before every boot image build
- Show the disk unlock prompt on Snapdragon X2 machines
- linux-omarchy-aarch64: add the Anduril BlueChip (#2237)
- Refresh the Snapdragon device tree list before every boot image build (#17934)
- review-comment by
greptile-apps[bot]
- review-comment by
greptile-apps[bot]
dhh merged
birkskyum's OEM firmware installation work into quattro in omacom/omarchy#17389. It installs available machine-specific packages before the remaining Windows firmware extraction step and migrates existing installations, retaining pending work until firmware setup and the boot image rebuild finish. The companion ISO change discovers firmware packages by what they provide, carrying them in the Arm offline mirror without maintaining another list of machine names.
Two further birkskyum proposals merged by
dhh address black screens during boot. omacom/omarchy#17662 adds early display dependencies for Snapdragon X2 disk unlock prompts. omacom/omarchy#17934 refreshes the managed device-tree list before every boot image build, so kernel changes can introduce or rename a tree without leaving it out of the image. This matters for the dedicated Anduril BlueChip tree committed to the package repository in omacom/omarchy-pkgs@3fcd5d2393fa, which also enables its Goodix touchscreen.
greptile-apps[bot] identified failed-write and interrupted-migration hazards in the device-tree refresh proposal. The resulting committed change checks writes before replacing boot settings and records an owed rebuild before changing the list. These are quattro changes and package-repository commits, rather than evidence of a stable Omarchy release.
