ARMImageSelection

Revision 3 as of 2009-01-20 19:44:07

Clear message

Summary

This specification describes an informational discussion held at UDS Jaunty in Mountainview about the right selection for images for the armel architecture

Rationale

Use Cases

Scope

Design

Summary

Rationale

Scope and Use Cases

Use Cases

Implementation

Outstanding Issues

BoF agenda and discussion

ARM images

* Various ways to boot

  • - From JTAG (not considered for this session, use case covered in a different session) - Using a bootloader
    • - From USB - From network (tftp, others?) - From disk or flash

* Various bootloaders

  • - Uboot - Redboot - Others

* Content of the images

  • - We might want to provide kernel-less "generic" filesystem images (rootfs);
    • first because the kernel is usually stored separately, and second because there will be many ARM kernels (one per subplatform almost)
    - We might instead include all kernels in a "generic" image, but this would
    • be very big (20 MB per kernel x number of flavours)

* Do we need d-i? Yes, e.g. installation over SSH for display-less devices

* Jaunty vfat images, kernel-less

  • - live ubuntu-desktop - d-i ubuntu-server

* Possible images, if we get community support

  • - live UNR (needs GL support) - live kubuntu - live xubuntu

* Future possible images

  • - live MID - extremely small image which would fit in flash and wouldn't require mass
    • storage such as a SATA disk

Work Needed

* We need a tool to edit an image to add a kernel (ogra volunteering)

Unresolved Issues

* Is there a standard similar to El Torito for ISO, or Master Boot Record, or

  • Multiboot specification?

    - If not, how do we have <device> boot from USB? requires feedback from

    • vendors

CategorySpec