[Trac #600] Need board ID

[Zarro Boogs per Child]

#600: Need board ID
-------------------------------+--------------------------------------------
 Reporter:  wmb at firmworks.com  |        Owner:  mfoster 
     Type:  defect             |       Status:  assigned
 Priority:  high               |    Milestone:  BTest-2 
Component:  hardware           |   Resolution:          
 Keywords:                     |  
-------------------------------+--------------------------------------------
Comment (by wmb at firmworks.com):

 The manufacturing data block will be okay, so long as the information
 actually gets in there.  Downsides are:

 a) Difficulties in bringup, since the manufacturing data typically doesn't
 appear until actual production.  That can be worked around, but it's just
 another thing to worry about.

 b) Difficulty testing the firmware and software that keys off the id code.
 Again this is a process issue.  In the B1 build, we (the firmware and
 software team) never saw actual manufacturing data until the systems had
 already been manufactured.  And it was wrong, which required a solid week
 of effort on my part to construct a foolproof way of repairing it.  And
 the repair job is still not finished because I think there are still boxed
 systems that haven't been updated, so the manufacturing data repair recipe
 will have to be maintained in the updater image for a long time.

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