From Fedora Project Wiki
(Nicer formatting + typo fix)
Line 24: Line 24:
 
== Summary ==
 
== Summary ==
 
<!-- 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. simplifying 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.
+
Default u-boot to using syslinux config files for booting. pxelinux for network and extlinux for local booting.
  
 
== Owner ==
 
== Owner ==
Line 62: Line 62:
 
<!-- 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.
 
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 ==
Line 90: Line 89:
 
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
+
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.  
+
Users will see a boot menu where they can select 1, 2, 3, etc fior the installed kernels.  
  
 
== Dependencies ==
 
== Dependencies ==
Line 114: Line 113:
 
== Release Notes ==
 
== Release Notes ==
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release.  
+
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved In this change, indicate them here.  A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release.  
  
 
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
 
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  

Revision as of 14:54, 7 March 2014


u-boot syslinux by default

Summary

Add syslinux support to u-boot enabling both pxelinux and extlinux support. simplifying 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