#7463 BLOC Never A: New board ID moving into production

[Zarro Boogs per Child]

#7463: New board ID moving into production
----------------------------+-----------------------------------------------
   Reporter:  wad           |       Owner:  rsmith                    
       Type:  enhancement   |      Status:  new                       
   Priority:  blocker       |   Milestone:  Never Assigned            
  Component:  not assigned  |     Version:  Update.1                  
 Resolution:                |    Keywords:  hardware, kernel, firmware
Next_action:  code          |    Verified:  0                         
  Blockedby:                |    Blocking:                            
----------------------------+-----------------------------------------------
Changes (by rsmith):

 * cc: dilinger, dsaxena (added)
  * keywords:  hardware => hardware, kernel, firmware


Comment:

 Replying to [ticket:7463 wad]:

 > This change will be delayed until the necessary software changes have
 been made, tested, and communicated to Quanta.  Quanta would like to make
 the change ASAP.
 >

 The EC modifications for this are trivial.  I will make up a new test
 firmware tomorrow and wad is going to mod a board with the new resistor.
 The new ID will be C3.

 The _real_ question is whats going to break when the kernel/olpc-configure
 sees a board ID of C3.  In the past audio stopped working cause it falls
 back on the older wiring scheme.

 Kernel folk can you please take gander at the code that deals with board
 ID and see if a 'C3' is in whatever case statements are there?

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