#9457 BLOC Not Tri: XO-1.5 OS30 boot scripts are quite right
Zarro Boogs per Child
bugtracker at laptop.org
Fri Sep 18 04:02:57 EDT 2009
#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 dsaxena):
Replying to [comment:1 pgf]:
>
> optimally, we should lock down the numbers to the slots. having the
numbers change for fixed interfaces is a bug, not a feature.
The number does not correspond to the interface, but the virtual block
device. In the case of both internal and external, the internal is being
scanned and found first, so it MMC block device 0 and the external is
device 1. If no internal device, then the external block device is the
only one in the system and is being assigned 0. Not a bug from that
perspective, but not the most user-friendly either. Changing this code so
that block device numbering is tied to board interface scan order is
likely non-trivial.
> barring that, perhaps olpc.fth can calculate the right device name,
based on where olpc.fth itself is running from?
You will also have to check if there's an internal card or not. Another
option, is to use "root=UUID:<ID>", where the ID is the ext file system ID
stored in the filesystem superblock (which OFW should have access to).
This option may depend on having udev running at the right time so it can
map the UUID to the right device, but not 100% sure.
--
Ticket URL: <http://dev.laptop.org/ticket/9457#comment:2>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list