#9457 BLOC Not Tri: XO-1.5 OS30 boot scripts are quite right

[Zarro Boogs per Child]

#9457: XO-1.5 OS30 boot scripts are quite right
-------------------------------+--------------------------------------------
           Reporter:  wad      |       Owner:  dsaxena      
               Type:  defect   |      Status:  new          
           Priority:  blocker  |   Milestone:  Not Triaged  
          Component:  kernel   |     Version:  not specified
         Resolution:           |    Keywords:               
        Next_action:  design   |    Verified:  0            
Deployment_affected:           |   Blockedby:               
           Blocking:           |  
-------------------------------+--------------------------------------------

Comment(by wmb at firmworks.com):

 Let's reconsider the "lock down the numbers" idea.

 On the XO, the internal disk is intended to be "non pluggable" from a user
 perspective.  That slot doesn't even support presence detect.  So I argue
 that it is good to force mmcblk0 to that device, even in the rare cases
 where the internal card is missing or defective.  That satisfies the
 principle of "it should be possible to describe the naming to users
 without waving your hands or launching into a series of disclaimers".

 So what we need is some way to tell the driver or whatever that the
 internal device is "fixed" and therefore to go ahead and declare its
 existence, even if a dynamic probe fails.  Such a feature ought to be
 useful for other machines, considering the advent of "wired down SD"
 devices like eMMC.

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