Startup Sequence: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Link trac #3300.)
Line 16: Line 16:
==First boot setup sequence==
==First boot setup sequence==
Assign names, colors, photo. Skipped once performed the first time.
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?
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? ([http://dev.laptop.org/ticket/3300 trac #3300])


(name selection: doesn't match design, [http://dev.laptop.org/ticket/3296 trac #3296])
(name selection: doesn't match design, [http://dev.laptop.org/ticket/3296 trac #3296])
Line 43: Line 43:
==Discussion==
==Discussion==
* Open Firmware currently displays some diagnostic information about boot sources. These icons are missing from Step 2 (and subsequent steps?).
* 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.
* Linux userland startup happens between activation and first boot setup; this needs some sort of animation. [http://dev.laptop.org/ticket/3300 trac #3300]
* Clock animation, if not done in X, will need to freeze between steps 11 and 12.
* Clock animation, if not done in X, will need to freeze between steps 11 and 12.
==Related trac bugs==
==Related trac bugs==
Line 54: Line 54:
* [http://dev.laptop.org/ticket/3296 3296 - Name entry does not match first boot spec]
* [http://dev.laptop.org/ticket/3296 3296 - Name entry does not match first boot spec]
* [http://dev.laptop.org/ticket/3297 3297 - We don't take a photo at first boot]
* [http://dev.laptop.org/ticket/3297 3297 - We don't take a photo at first boot]
* [http://dev.laptop.org/ticket/3299 3299 - Dynamic "loading" animation for first boot]
* [http://dev.laptop.org/ticket/3299 3299 - Dynamic "loading" animation for boot]
* [http://dev.laptop.org/ticket/3300 3300 - Need transitions around first boot name/color/photo chooser.]

Revision as of 18:46, 10 September 2007

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. (needs work: trac #534)

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. (needs work: trac #1328) These simple graphics are drawn by Linux initrd directly onto the framebuffer.

Step 3a: Lease found on SD card
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? (trac #3300)

(name selection: doesn't match design, trac #3296)

Step 4: Entering "first" name
Step 5: Entering "last" name
Step 6: Selecting the "next" button


(color selection: needs work, trac #2336)

Step 7: Color selection?
Step 8: Color selection?


(photo selection: needs work, trac #3297)

Step 9: Taking photo?
Step 10: Done?


Loading animation

Occurs on every boot.

(doesn't match design, trac #3299)

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


Shutdown animation

See trac #692

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. trac #3300
  • Clock animation, if not done in X, will need to freeze between steps 11 and 12.

Related trac bugs