[Trac #978] Firmware recoverability and security

[Zarro Boogs per Child]

#978: Firmware recoverability and security
---------------------------------+------------------------------------------
 Reporter:  wmb at firmworks.com    |        Owner:  wmb at firmworks.com
     Type:  defect               |       Status:  new              
 Priority:  normal               |    Milestone:  CTest            
Component:  ofw - open firmware  |   Resolution:                   
 Keywords:                       |  
---------------------------------+------------------------------------------
Comment (by AlbertCahalan):

 Isn't the keyboard easy to access without a complex software stack? (this
 is still not documented; I don't know if it is USB, PS/2 or some custom
 thing)

 Assuming the keyboard is easy to access:

 1. prepare keyboard
 2. load primary (most recent?) image into RAM
 3. if errors found or keys pressed, load the alternate image into RAM
 4. jump to the image in RAM

 A small power-on noise might be good to have. Make a tiny beep as soon as
 the keyboard is ready to be used for switching to the alternate image.
 Make a second beep when jumping to the image, higher in pitch if using the
 primary image but lower in pitch if using the secondary image.

-- 
Ticket URL: <http://dev.laptop.org/ticket/978#comment:1>
One Laptop Per Child <http://laptop.org/>