From Fedora Project Wiki
< Changes
(Add a new feature) |
Immanetize (talk | contribs) (→Owner) |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 37: | Line 37: | ||
* Email: pjones at fedoraproject dot org | * Email: pjones at fedoraproject dot org | ||
* Email: richard at hughsie dot com | * Email: richard at hughsie dot com | ||
* Release notes owner: | * Release notes owner: [[User:immanetize| Pete Travis]] | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | ||
| Line 57: | Line 57: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1230554 #1230554] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 125: | Line 125: | ||
== Contingency Plan == | == Contingency Plan == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: (What to do? Who will do it?) | * Contingency mechanism: (What to do? Who will do it?) Don't ship it. | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? N/A (not a System Wide Change), | * Blocks release? N/A (not a System Wide Change), No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Blocks product? | * Blocks product? none <!-- Applicable for Changes that blocks specific product release/Fedora.next --> | ||
== Documentation == | == Documentation == | ||
| Line 149: | Line 148: | ||
TBD | TBD | ||
[[Category: | [[Category:ChangeAcceptedF23]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 04:21, 2 September 2015
System Firmware Updates
Summary
This change is to add the ability to perform firmware updates on UEFI machines.
Owner
- Name: Peter Jones
- Name: Richard Hughes
- Email: pjones at fedoraproject dot org
- Email: richard at hughsie dot com
- Release notes owner: Pete Travis
Current status
Detailed Description
This adds the ability to perform updates of system firmware, as well as some peripheral firmware, on machines supporting the UEFI Capsule Update mechanism and UEFI 2.5's "ESRT" feature.
Right now this is generic support—the number of machines for which we actually have firmware updates available is very small, as the underlying technology is quite new—and it doesn't include any actual delivery mechanism for such firmware images. But if they're put at the right place for fwupd to notice them, and the system supports the right features, they'll show up as updates in gnome-software.
Benefit to Fedora
This allows us to introduce firmware updates for specific machines in the future. Firmware updates are good.
Scope
- Proposal owners: Get fwupdate, fwupd, and a version of gnome-software that can use them into Fedora, maintain it in the future, etc.
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
N/A (not a System Wide Change)
Dependencies
This depends on a re-factoring of efibootmgr and efivar-libs, as efibootmgr currently contains a lot of non-library functionality that fwupdate relies on.
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) Don't ship it.
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), No
- Blocks product? none
Documentation
TBD
N/A (not a System Wide Change)
Release Notes
TBD