From Fedora Project Wiki
(Created page with "<!-- Self Contained or System Wide Change Proposal? Use this guide to determine to which category your proposed change belongs to. Self Contained Changes are: * changes to is...")
 
Line 25: Line 25:
 
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
 
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
 
add syslinux support to u-boot enabling both pxelinux and extlinux support. simnplfying booting arm machines, making anaconda installs easy and overall providing for a better user experience.
 
add syslinux support to u-boot enabling both pxelinux and extlinux support. simnplfying booting arm machines, making anaconda installs easy and overall providing for a better user experience.
 +
default u-boot to using syslinux config files for booting. pxelinux for network and extlinux for local booting.
  
 
== Owner ==
 
== Owner ==
Line 56: Line 57:
 
== Detailed Description ==
 
== Detailed Description ==
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 
+
u-boot has support for booting using syslinux style configuration files, this change is to default to using it on all supported systems.
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 +
This takes away the complexity of booting arm systems. There is no need to know addresses or to wrap images with mkimage. Users will get a menu that allows them to choose which kernel to boot. making things like a boot.img will be possible. Initiating installs via anaconda will also be much more simple and straight forward.
 +
  
 
== Scope ==
 
== Scope ==
 
<!-- What work do the developers have to accomplish to complete the change in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do the developers have to accomplish to complete the change in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
  
 
+
* Proposal owners: default u-boot to loading extlinux.conf files. anaconda to write a devicetreedir line in extlinux.conf on arm systems. appliance-creator to write out a devicetreedir in extlinux.conf on arm systems
* Proposal owners:  
+
* Other developers: grubby to update extlinux.conf appropriately.
* Other developers:  
+
* Release engineering: None
* Release engineering:  
+
* Policies and guidelines: None
* Policies and guidelines:  
 
  
 
== Upgrade/compatibility impact ==
 
== Upgrade/compatibility impact ==
 
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
 
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
 +
Existing booting via arm-boot-config should still work, so existing systems will work as before. longer term we will need to provide a simple way to create a extlinux.conf file and update u-boot for systems to migrate.
  
 
== How To Test ==
 
== How To Test ==
Line 87: Line 90:
 
3. What are the expected results of those actions?
 
3. What are the expected results of those actions?
 
-->
 
-->
 
+
install u-boot onto an sdcard or update u-boot to a newer binary and use an image or run an anaconda install via a pxe tree
  
 
== User Experience ==
 
== User Experience ==
 
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 +
users will see a boot menu where they can select 1, 2, 3, etc fior the installed kernels.
  
 
== Dependencies ==
 
== Dependencies ==
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
 
+
Outside of my control is changes to grubby that I will work with the maintainer to ensure support is in for.
  
 
== 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?) if for some reason we fail horribly at migrating into primary we would go back to secondary,  the fix would be removing armv7hl from the build arches by Release Engineering
+
* Contingency mechanism: (What to do?  Who will do it?) make sure all supported boards work with arm-boot-config and use it as a fallback.
 
<!-- 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: Alpha
 
* Contingency deadline: Alpha
 
<!-- 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?  Yes
+
* Blocks release?  No
  
 
== Documentation ==
 
== Documentation ==

Revision as of 15:48, 6 March 2014


u-boot syslinux by default

Summary

add syslinux support to u-boot enabling both pxelinux and extlinux support. simnplfying booting arm machines, making anaconda installs easy and overall providing for a better user experience. default u-boot to using syslinux config files for booting. pxelinux for network and extlinux for local booting.

Owner

Current status

  • Targeted release: Fedora 21
  • Last updated: 2014-03-03
  • Tracker bug:

FESCo resolution:

Detailed Description

u-boot has support for booting using syslinux style configuration files, this change is to default to using it on all supported systems.

Benefit to Fedora

This takes away the complexity of booting arm systems. There is no need to know addresses or to wrap images with mkimage. Users will get a menu that allows them to choose which kernel to boot. making things like a boot.img will be possible. Initiating installs via anaconda will also be much more simple and straight forward.


Scope

  • Proposal owners: default u-boot to loading extlinux.conf files. anaconda to write a devicetreedir line in extlinux.conf on arm systems. appliance-creator to write out a devicetreedir in extlinux.conf on arm systems
  • Other developers: grubby to update extlinux.conf appropriately.
  • Release engineering: None
  • Policies and guidelines: None

Upgrade/compatibility impact

Existing booting via arm-boot-config should still work, so existing systems will work as before. longer term we will need to provide a simple way to create a extlinux.conf file and update u-boot for systems to migrate.

How To Test

install u-boot onto an sdcard or update u-boot to a newer binary and use an image or run an anaconda install via a pxe tree

User Experience

users will see a boot menu where they can select 1, 2, 3, etc fior the installed kernels.

Dependencies

Outside of my control is changes to grubby that I will work with the maintainer to ensure support is in for.

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) make sure all supported boards work with arm-boot-config and use it as a fallback.
  • Contingency deadline: Alpha
  • Blocks release? No

Documentation

No documentation.

Release Notes