#9457 BLOC 1.5-F11: XO-1.5 OS30 boot scripts aren't quite right

[Zarro Boogs per Child]

#9457: XO-1.5 OS30 boot scripts aren't quite right
---------------------------------+------------------------------------------
           Reporter:  wad        |       Owner:  dsd          
               Type:  defect     |      Status:  new          
           Priority:  blocker    |   Milestone:  1.5-F11      
          Component:  initramfs  |     Version:  not specified
         Resolution:             |    Keywords:               
        Next_action:  design     |    Verified:  0            
Deployment_affected:             |   Blockedby:  9558         
           Blocking:             |  
---------------------------------+------------------------------------------
Changes (by dsaxena):

 * cc: dsaxena (added)


Comment:

 (IGNORE above comment as I miss-typed udev instead of OFW several times)

 > As the above shows, we boot from mmcblk0p2 both times, but the kernel
 knows what device path points to that device. In the external case it is
 pci-mmc1, in the internal case it is pci-mmc0.
 > The 4-digit ID afterwards is the card's Relative Card Address which OFW
 can retrieve. But really, if we just have the
 >

 Finishing that sentence:

 If we just have the "/pci/sd at c/disk@<number>" from OFW, we can map that to
 the proper by-path device by knowing that disk@<number> means pci-
 mmc<@number-1>:<don't_care>. I still really like the idea of OFW just
 passing us the UUID from the ext[234] fs as OFW's bootpath for USB is
 "/usb/disk" and there's no way to map that to a given USB device in the
 case where there is more than one USB key plugged in.

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