Startup Sequence: Difference between revisions
Jump to navigation
Jump to search
(Details of startup sequence frames.) |
(Added discussion and links to trac bugs.) |
||
Line 2: | Line 2: | ||
==Initialization of every boot== |
==Initialization of every boot== |
||
These graphics are drawn by open firmware. |
|||
[[Image:intro_00.png|thumb|left|Step 1: off]] |
[[Image:intro_00.png|thumb|left|Step 1: off]] |
||
[[Image:intro_01.png|thumb|left|Step 2: static XO man]] |
[[Image:intro_01.png|thumb|left|Step 2: static XO man]] |
||
<br clear="all" /> |
<br clear="all" /> |
||
Linux boot happens here with screen frozen by DCON. |
|||
==Activation sequence== |
==Activation sequence== |
||
Skipped when activation lease is already valid. |
Skipped when activation lease is already valid. |
||
These simple graphics are drawn by Linux initrd directly onto the framebuffer. |
|||
[[Image:intro_02.png|thumb|left|Step 3a: Lease found on USB key]] |
[[Image:intro_02.png|thumb|left|Step 3a: Lease found on USB key]] |
||
[[Image:intro_03.png|thumb|left|Step 3b: Activation failed.]] |
[[Image:intro_03.png|thumb|left|Step 3b: Activation failed.]] |
||
Line 12: | Line 15: | ||
==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? |
|||
[[Image:intro_04.png|thumb|left|Step 4: Entering "first" name]] |
[[Image:intro_04.png|thumb|left|Step 4: Entering "first" name]] |
||
[[Image:intro_05.png|thumb|left|Step 5: Entering "last" name]] |
[[Image:intro_05.png|thumb|left|Step 5: Entering "last" name]] |
||
Line 27: | Line 31: | ||
<br clear="all" /> |
<br clear="all" /> |
||
==Discussion== |
==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== |
|||
* [http://dev.laptop.org/ticket/1543 1543 - First boot user experience] |
|||
* [http://dev.laptop.org/ticket/534 534 - Need image for splashscreen] |
|||
* [http://dev.laptop.org/ticket/2336 2336 - First boot color chooser] |
|||
* [http://dev.laptop.org/ticket/1328 1328 - Look and feel enhancements for the boot process] |
|||
* [http://dev.laptop.org/ticket/692 692 - Shutdown design] |
Revision as of 17:14, 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.
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.
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?
Loading animation
Occurs on every boot.
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.