Startup Sequence

From OLPC
Revision as of 13:26, 10 September 2007 by CScott (talk | contribs) (Related trac bugs: Add link to #3295)
Jump to: navigation, search

This page documents Eben's startup sequence design, as detailed in trac ticket #1543.

Initialization of every boot

These graphics are drawn by open firmware.

Step 1: off
Step 2: static XO man


Linux boot happens here with screen frozen by DCON.

Activation sequence

Skipped when activation lease is already valid. These simple graphics are drawn by Linux initrd directly onto the framebuffer.

Step 3a: Lease found on USB key
Step 3b: Activation failed.


First boot setup sequence

Assign names, colors, photo. Skipped once performed the first time. Drawn by X. Some transition is needed before step 4, since init/X/python startup takes a significant amount of time. Use the same graphics as the "loading animation" but with generic XO colors?

Step 4: Entering "first" name
Step 5: Entering "last" name
Step 6: Selecting the "next" button
Step 7: Color selection?
Step 8: Color selection?
Step 9: Taking photo?
Step 10: Done?


Loading animation

Occurs on every boot.

Step 11a: "Clock" animation
Step 11b: "Clock" animation
Step 12: Sugar started.


Discussion

  • Open Firmware currently displays some diagnostic information about boot sources. These icons are missing from Step 2 (and subsequent steps?).
  • Linux userland startup happens between activation and first boot setup; this needs some sort of animation.
  • Clock animation, if not done in X, will need to freeze between steps 11 and 12.

Related trac bugs