-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add back Qualcomm DTBs on aarch64 #1467
Comments
This upstream PR merged 🎉. Once we get a new release of |
No, because it's not on by default yet. |
I think the idea is to turn this on in FCOS, possibly only on multi-arch. Will open a separate ticket to discuss this. But anyway, if it works well in FCOS for a while, then we could consider turning it on upstream too? |
Now that we have autopruning ability we can re-add the qcom dtbs on aarch64 that were dropped in coreos/fedora-coreos-tracker#1464 Fixes coreos/fedora-coreos-tracker#1467
Now that we have autopruning ability we can re-add the qcom dtbs on aarch64 that were dropped in coreos/fedora-coreos-tracker#1464 Fixes coreos/fedora-coreos-tracker#1467
Now that we have autopruning ability we can re-add the qcom dtbs on aarch64 that were dropped in coreos/fedora-coreos-tracker#1464 Fixes coreos/fedora-coreos-tracker#1467
In coreos/fedora-coreos-config#2435 the DTBs were added back for F39+. This change will follow F39 and get fixed when that gets merged over into our production streams. |
The fix for this went into |
Now that we have autopruning ability we can re-add the qcom dtbs on aarch64 that were dropped in coreos/fedora-coreos-tracker#1464 Fixes coreos/fedora-coreos-tracker#1467
Now that we have autopruning ability we can re-add the qcom dtbs on aarch64 that were dropped in coreos/fedora-coreos-tracker#1464 Fixes coreos/fedora-coreos-tracker#1467
The fix for this went into |
The fix for this went into |
In #1464, we decided to temporarily remove the Qualcomm device tree blobs to make enough space in the boot partition to allow for future upgrades. This was done because we deemed the likelihood of users being affected by this removal to be minimal.
This ticket tracks adding the blobs back once we can rely on ostreedev/ostree#2847.
The text was updated successfully, but these errors were encountered: