#11146 NORM 1.75-so: XO-1.75 automatic firmware update triggered by installed operating system build (was: Add bootfw package to 1.75 build)

[Zarro Boogs per Child]

#11146: XO-1.75 automatic firmware update triggered by installed operating system
build
---------------------------------+------------------------------------------
           Reporter:  greenfeld  |       Owner:  cjb                              
               Type:  task       |      Status:  new                              
           Priority:  normal     |   Milestone:  1.75-software                    
          Component:  distro     |     Version:  Development build as of this date
         Resolution:             |    Keywords:                                   
        Next_action:  design     |    Verified:  0                                
Deployment_affected:             |   Blockedby:                                   
           Blocking:             |  
---------------------------------+------------------------------------------
Changes (by Quozl):

  * next_action:  diagnose => design
  * type:  defect => task
  * version:  1.75-B1 => Development build as of this date


Comment:

 @greenfeld, you propose solving this by adding package.

 The automatic update is normally (XO-1, XO-1.5) handled by the installed
 operating system build using the /bootpart/olpc.fth file, which is
 currently (XO-1.75 os36) provided by olpc-os-builder, but would normally
 (XO-1, XO-1.5) be provided by bootfw package.

 Now that kernels provide /proc/device-tree, the XO-1.75 specific olpc.fth
 can be reduced significantly.  But I'm not sure that is a good idea.

 olpc.fth is maintained by the packagers of bootfw*.rpm, which are Richard
 Smith, Paul Fox, Mitch Bradley, and I, depending on who turns the crank.
 It's not under version control.  I think it shouldn't be part of
 OpenFirmware or the bootfw*.rpm, but that's the way it is at the moment.
 I'd like to see that change.

 @pbrobinson, unless there's a particularly good reason for changing how
 the packages are built, I prefer to leave them as they are.  I've already
 changed XO-1.75's bootfw build to noarch, and both q4b06 and q4b07 are
 noarch.  XO-1 and XO-1.5 packages are still i386, but a future release may
 change them to noarch #11055.

 I see no reason why we need to provide .srpm, given that the current .srpm
 is binary and not source, and a different version of the source is used
 for the three laptop models.  We don't release upstream and then carve
 three firmware blobs from it.  Each is released in turn.

 Changed distro component owner to pbrobinson.

 Related tickets #11061 (firmware update security)

-- 
Ticket URL: <http://dev.laptop.org/ticket/11146#comment:2>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system